From: Basavaraj Natikar <bnatikar@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,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v5] thunderbolt: Add quirk to disable CLx
Date: Wed, 15 Feb 2023 11:29:00 +0530 [thread overview]
Message-ID: <a4601106-e41e-1991-9f63-b595243dc8bb@amd.com> (raw)
In-Reply-To: <Y+xyh44lGEzwuOj/@black.fi.intel.com>
On 2/15/2023 11:19 AM, Mika Westerberg wrote:
> On Tue, Feb 14, 2023 at 02:01:52PM -0600, Sanjay R Mehta wrote:
>> void tb_check_quirks(struct tb_switch *sw)
>> {
>> + struct tb_switch *root_sw = sw->tb->root_switch;
>> int i;
>>
>> for (i = 0; i < ARRAY_SIZE(tb_quirks); i++) {
>> const struct tb_quirk *q = &tb_quirks[i];
>>
>> - if (q->hw_vendor_id && q->hw_vendor_id != sw->config.vendor_id)
>> + if (q->hw_vendor_id && (q->hw_vendor_id != sw->config.vendor_id &&
>> + q->hw_vendor_id != root_sw->config.vendor_id))
> Again, why you need to change this?
>
> If you have the AMD host router device ID in the list the quirk applies
> and that makes the driver skip enabling CL states for that link. It
> should not matter if we enable CL states in the deeper parts of the
> topology (even if we actually do not at the moment) because that's
> completely different link, right.
Thank you Mike for point it out then [PATCH v4] <https://lore.kernel.org/all/1676402030-4653-1-git-send-email-Sanju.Mehta@amd.com/#r> patch changes solves the purpose.
[PATCH v4] thunderbolt: Add quirk to disable CLx <https://lore.kernel.org/all/1676402030-4653-1-git-send-email-Sanju.Mehta@amd.com/#r>
https://lore.kernel.org/all/1676402030-4653-1-git-send-email-Sanju.Mehta@amd.com/
Please review the changes
next prev parent reply other threads:[~2023-02-15 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 20:01 [PATCH v5] thunderbolt: Add quirk to disable CLx Sanjay R Mehta
2023-02-15 5:49 ` Mika Westerberg
2023-02-15 5:59 ` Basavaraj Natikar [this message]
2023-02-15 6:16 ` Mika Westerberg
2023-02-15 6:23 ` Basavaraj Natikar
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=a4601106-e41e-1991-9f63-b595243dc8bb@amd.com \
--to=bnatikar@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Sanju.Mehta@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