From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Wayne Chang <waynec@nvidia.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, singhanc@nvidia.com,
stable@vger.kernel.org
Subject: Re: [PATCH v5 1/1] ucsi_ccg: Check DEV_INT bit only when starting CCG4
Date: Wed, 12 Jan 2022 13:05:37 +0200 [thread overview]
Message-ID: <Yd62AVTwH2pGgk4y@kuha.fi.intel.com> (raw)
In-Reply-To: <20220112094143.628610-1-waynec@nvidia.com>
On Wed, Jan 12, 2022 at 05:41:43PM +0800, Wayne Chang wrote:
> From: Sing-Han Chen <singhanc@nvidia.com>
>
> CCGx clears Bit 0:Device Interrupt in the INTR_REG
> if CCGx is reset successfully. However, there might
> be a chance that other bits in INTR_REG are not
> cleared due to internal data queued in PPM. This case
> misleads the driver that CCGx reset failed.
>
> The commit checks bit 0 in INTR_REG and ignores other
> bits. The ucsi driver would reset PPM later.
>
> Fixes: 247c554a14aa ("usb: typec: ucsi: add support for Cypress CCGx")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sing-Han Chen <singhanc@nvidia.com>
> Signed-off-by: Wayne Chang <waynec@nvidia.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> V4 -> V5: Added Cc tag and revised the commit messages
> V3 -> V4: Updated the Fixes tag
> V2 -> V3: Added the Fixes tag
> V1 -> V2: Fixed the name of Sign-off-by
> drivers/usb/typec/ucsi/ucsi_ccg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c b/drivers/usb/typec/ucsi/ucsi_ccg.c
> index bff96d64dddf..6db7c8ddd51c 100644
> --- a/drivers/usb/typec/ucsi/ucsi_ccg.c
> +++ b/drivers/usb/typec/ucsi/ucsi_ccg.c
> @@ -325,7 +325,7 @@ static int ucsi_ccg_init(struct ucsi_ccg *uc)
> if (status < 0)
> return status;
>
> - if (!data)
> + if (!(data & DEV_INT))
> return 0;
>
> status = ccg_write(uc, CCGX_RAB_INTR_REG, &data, sizeof(data));
> --
> 2.25.1
thanks,
--
heikki
prev parent reply other threads:[~2022-01-12 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 9:41 Wayne Chang
2022-01-12 11:05 ` Heikki Krogerus [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=Yd62AVTwH2pGgk4y@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=singhanc@nvidia.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®