From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Sanjay R Mehta <sanmehta@amd.com>
Cc: Sanjay R Mehta <Sanju.Mehta@amd.com>,
andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, Basavaraj.Natikar@amd.com,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: Disable CLx state for AMD Yellow Carp and Pink Sardine
Date: Fri, 10 Feb 2023 16:56:41 +0200 [thread overview]
Message-ID: <Y+ZbKdYWvp6z5reQ@black.fi.intel.com> (raw)
In-Reply-To: <077f39f2-9fac-c743-1c97-eecf4512b1dc@amd.com>
On Fri, Feb 10, 2023 at 08:16:48PM +0530, Sanjay R Mehta wrote:
>
>
> On 2/10/2023 7:47 PM, Mika Westerberg wrote:
> > On Fri, Feb 10, 2023 at 07:32:13PM +0530, Sanjay R Mehta wrote:
> >>
> >>
> >> On 2/10/2023 7:25 PM, Mika Westerberg wrote:
> >>> Hi,
> >>>
> >>> On Fri, Feb 10, 2023 at 07:32:23AM -0600, Sanjay R Mehta wrote:
> >>>> From: Sanjay R Mehta <sanju.mehta@amd.com>
> >>>>
> >>>> AMD Yellow Carp and Pink Sardine don't support CLx state,
> >>>> hence disabling it.
> >>>
> >>> The lane adapters are supposed to announce whether CL-states are
> >>> supported or not. Is that not the case with the AMD hardware?
> >>
> >> Yes Mika. it doesn't work for AMD hardware.
> >
> > :-(
> >
> > Okay can you then add a quirk for this to quirks.c?
>
> Did you meant like below, is this fine?
I mean add the affected routers to quirks.c that then sets:
sw->quirks |= QUIRK_NO_CLX;
and check this in tb_switch_clx_is_supported(), if set return false or
something like that.
I know we have bunch of Intel specific quirks littered around the
driver but let's not add more. We should move these too into quirks.c at
some point.
prev parent reply other threads:[~2023-02-10 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 13:32 [PATCH] thunderbolt: Disable CLx state for AMD Yellow Carp and Pink Sardine Sanjay R Mehta
2023-02-10 13:55 ` Mika Westerberg
2023-02-10 14:02 ` Sanjay R Mehta
2023-02-10 14:17 ` Mika Westerberg
2023-02-10 14:46 ` Sanjay R Mehta
2023-02-10 14:56 ` Mika Westerberg [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=Y+ZbKdYWvp6z5reQ@black.fi.intel.com \
--to=mika.westerberg@linux.intel.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=sanmehta@amd.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