From: Abhishek Sahu <abhsahu@nvidia.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lukas@wunner.de>
Subject: Re: [PATCH v2 0/2] PCI: device link quirk for NVIDIA GPU
Date: Mon, 17 Jun 2019 17:04:43 +0530 [thread overview]
Message-ID: <ec2226e8-ccce-488f-20eb-0dd22dc9bed1@nvidia.com> (raw)
In-Reply-To: <20190613205720.GK13533@google.com>
On 6/14/2019 2:27 AM, Bjorn Helgaas wrote:
> On Thu, Jun 06, 2019 at 02:52:23PM +0530, Abhishek Sahu wrote:
>> * v2:
>>
>> 1. Make the pci device link helper function generic which can be
>> used for other multi-function PCI devices also.
>> 2. Minor changes in comments and commit logs.
>>
>> * v1:
>>
>> NVIDIA Turing GPU [1] has hardware support for USB Type-C and
>> VirtualLink [2]. The Turing GPU is a multi-function PCI device
>> which has the following four functions:
>>
>> - VGA display controller (Function 0)
>> - Audio controller (Function 1)
>> - USB xHCI Host controller (Function 2)
>> - USB Type-C USCI controller (Function 3)
>>
>> Currently NVIDIA and Nouveau GPU drivers only manage function 0.
>> Rest of the functions are managed by other drivers. These functions
>> internally in the hardware are tightly coupled. When function 0 goes
>> in runtime suspended state, then it will do power gating for most of
>> the hardware blocks. Some of these hardware blocks are used by
>> the other PCI functions, which leads to functional failure. In the
>> mainline kernel, the device link is present between
>> function 0 and function 1. This patch series deals with creating
>> a similar kind of device link between function 0 and
>> functions 2 and 3.
>>
>> [1] https://www.nvidia.com/content/dam/en-zz/Solutions/design-visualization/technologies/turing-architecture/NVIDIA-Turing-Architecture-Whitepaper.pdf
>> [2] https://en.wikipedia.org/wiki/VirtualLink
>>
>> Abhishek Sahu (2):
>> PCI: Code reorganization for creating device link
>> PCI: Create device link for NVIDIA GPU
>
> Applied to pci/misc for v5.3, thanks!
Thanks Bjorn for your review and support!
The runtime PM changes in USB Type-C USCI driver is also
applied for v5.3
https://marc.info/?l=linux-usb&m=155994544705901&w=2
It will help in achieving run-time PM for Turing GPUs
in v5.3.
Regards,
Abhishek
prev parent reply other threads:[~2019-06-17 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 9:22 [PATCH v2 0/2] PCI: device link quirk for NVIDIA GPU Abhishek Sahu
2019-06-06 9:22 ` [PATCH v2 1/2] PCI: Code reorganization for creating device link Abhishek Sahu
2019-06-06 9:22 ` [PATCH v2 2/2] PCI: Create device link for NVIDIA GPU Abhishek Sahu
2019-06-13 20:57 ` [PATCH v2 0/2] PCI: device link quirk " Bjorn Helgaas
2019-06-17 11:34 ` Abhishek Sahu [this message]
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=ec2226e8-ccce-488f-20eb-0dd22dc9bed1@nvidia.com \
--to=abhsahu@nvidia.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).