From: Sanjay R Mehta <sanmehta@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Sanjay R Mehta <Sanju.Mehta@amd.com>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, Basavaraj.Natikar@amd.com,
Nehal-bakulchandra.Shah@amd.com, Shyam-sundar.S-k@amd.com,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Added some bug fixes for USB4
Date: Mon, 9 Aug 2021 17:58:17 +0530 [thread overview]
Message-ID: <0a2a4b97-1c9e-b570-f848-9fafce348aeb@amd.com> (raw)
In-Reply-To: <YREaPR3xyxOkm3iL@lahna>
On 8/9/2021 5:36 PM, Mika Westerberg wrote:
> [CAUTION: External Email]
>
> Hi,
>
> On Fri, Aug 06, 2021 at 11:59:04AM -0500, Sanjay R Mehta wrote:
>> From: Sanjay R Mehta <sanju.mehta@amd.com>
>>
>> This series adds some general USB4 bug fixes as per USB4 Spec.
>>
>> v2:
>> - Added quirk to handle any vendor specific quirks.
>> v1:
>> - removed PCI-IDs as AMD USB4 controller exposes USB4 class ID.
>> - removed clearing of interrupt using interrupt status clear register.
>> - skip port Adapter(0) initialisation for both host router & device router.
>>
>> Sanjay R Mehta (4):
>> thunderbolt: Add quirk to support vendor specific implementation
>> thunderbolt: Handle ring interrupt by reading intr status
>> thunderbolt: Skip port init for control adapter(0)
>> thunderbolt: Fix port linking by checking all adapters
>
> I did some minor tweaks and removed the "Fixes" lines since these are
> actually not fixes per se more like improvements :) Then applied all to
> thunderbolt.git/next. Please check that they still work on AMD hardware
> and make sense in general.
>
Thanks a lot Mika :). This should work for AMD.
> Thanks!
>
prev parent reply other threads:[~2021-08-09 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 16:59 [PATCH v3 0/4] Added some bug fixes for USB4 Sanjay R Mehta
2021-08-06 16:59 ` [PATCH v3 1/4] thunderbolt: Add quirk to support vendor specific implementation Sanjay R Mehta
2021-08-06 16:59 ` [PATCH v3 2/4] thunderbolt: Handle ring interrupt by reading intr status Sanjay R Mehta
2021-08-06 16:59 ` [PATCH v3 3/4] thunderbolt: Skip port init for control adapter(0) Sanjay R Mehta
2021-08-06 16:59 ` [PATCH v3 4/4] thunderbolt: Fix port linking by checking all adapters Sanjay R Mehta
2021-08-09 12:06 ` [PATCH v3 0/4] Added some bug fixes for USB4 Mika Westerberg
2021-08-09 12:28 ` Sanjay R Mehta [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=0a2a4b97-1c9e-b570-f848-9fafce348aeb@amd.com \
--to=sanmehta@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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).