From: Greg KH <gregkh@linuxfoundation.org>
To: Wayne Chang <waynec@nvidia.com>
Cc: heikki.krogerus@linux.intel.com, Sanket.Goswami@amd.com,
singhanc@nvidia.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: typec: ucsi_ccg: Disable UCSI ALT support on Tegra
Date: Wed, 28 Sep 2022 15:45:40 +0200 [thread overview]
Message-ID: <YzRQBEeLorfC8KAL@kroah.com> (raw)
In-Reply-To: <20220928131615.3286936-1-waynec@nvidia.com>
On Wed, Sep 28, 2022 at 09:16:15PM +0800, Wayne Chang wrote:
> From: Sing-Han Chen <singhanc@nvidia.com>
>
> Firmware built for Tegra doesn't support UCSI ALT
> command and has known issue of reporting wrong
> capability info.
>
> This commit disables UCSI ALT support when reading
> the capability on Tegra.
You have a full 72 columns to use, no need to make it shorter :)
>
> Signed-off-by: Sing-Han Chen <singhanc@nvidia.com>
> Signed-off-by: Wayne Chang <waynec@nvidia.com>
> ---
> drivers/usb/typec/ucsi/ucsi_ccg.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c b/drivers/usb/typec/ucsi/ucsi_ccg.c
> index 5c0bf48be766..fde3da0605f5 100644
> --- a/drivers/usb/typec/ucsi/ucsi_ccg.c
> +++ b/drivers/usb/typec/ucsi/ucsi_ccg.c
> @@ -122,9 +122,14 @@ struct version_format {
> * Firmware version 3.1.10 or earlier, built for NVIDIA has known issue
> * of missing interrupt when a device is connected for runtime resume
> */
> -#define CCG_FW_BUILD_NVIDIA (('n' << 8) | 'v')
> +#define CCG_FW_BUILD_NVIDIA_RTX (('n' << 8) | 'v')
Why change this here? It's not needed, just add the new command
instead.
And what commit id does this fix? Is it needed for stable kernels? If
so, how far back?
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-28 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 13:16 [PATCH 1/1] usb: typec: ucsi_ccg: Disable UCSI ALT support on Tegra Wayne Chang
2022-09-28 13:45 ` Greg KH [this message]
2022-09-28 14:11 ` Wayne Chang
2022-09-28 14:29 ` Greg KH
2022-09-28 14:45 ` Wayne Chang
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=YzRQBEeLorfC8KAL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Sanket.Goswami@amd.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=singhanc@nvidia.com \
--cc=waynec@nvidia.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