LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Abhishek Sahu <abhsahu@nvidia.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI: Create device link for NVIDIA GPU
Date: Mon, 3 Jun 2019 12:07:07 +0200 [thread overview]
Message-ID: <20190603100707.yhw4fu54vt3ykvd5@wunner.de> (raw)
In-Reply-To: <d0824334-99f2-d42e-3a5e-3bdc4c1c37c8@nvidia.com>
On Mon, Jun 03, 2019 at 01:30:51PM +0530, Abhishek Sahu wrote:
> On 6/1/2019 2:09 AM, Bjorn Helgaas wrote:
> > > If there *is* spec language that allows dependencies like this, please
> > include the citation in your commit log.
>
> The PCIe specification treats each function separately but GPU case is
> different. So, it won't be part of PCIe spec. in GPU, the different
> kind of devices are internally coupled in HW but still needs to be
> managed by different driver.
GPUs aren't the only devices which have these implicit dependencies.
E.g. Broadcom BCM57765 combines a Gigabit Ethernet chip in function 0
(14e4:16b4) with an SD card reader in function 1 (14e4:16bc) and AFAIK
for the latter to work, the former needs to be in D0. I think we're
incorrectly not enforcing this dependency in the kernel yet. That chip
was built into many MacBooks.
Indeed the inability to specify such inter-function power dependencies
in config space seems to be a gaping hole in the PCI spec. Maybe we
should always assume that function 0 needs to be in D0 for any other
function to work? Not sure if that would be safe.
Thanks,
Lukas
next prev parent reply other threads:[~2019-06-03 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 5:01 [PATCH 0/2] PCI: device link quirk " Abhishek Sahu
2019-05-31 5:01 ` [PATCH 1/2] PCI: Code reorganization for VGA device link Abhishek Sahu
2019-06-03 17:15 ` Bjorn Helgaas
2019-06-04 11:38 ` Abhishek Sahu
2019-05-31 5:01 ` [PATCH 2/2] PCI: Create device link for NVIDIA GPU Abhishek Sahu
2019-05-31 20:39 ` Bjorn Helgaas
2019-06-03 8:00 ` Abhishek Sahu
2019-06-03 10:07 ` Lukas Wunner [this message]
2019-06-03 17:22 ` Bjorn Helgaas
2019-06-04 11:43 ` Abhishek Sahu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603100707.yhw4fu54vt3ykvd5@wunner.de \
--to=lukas@wunner.de \
--cc=abhsahu@nvidia.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--subject='Re: [PATCH 2/2] PCI: Create device link for NVIDIA GPU' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).