linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wayne Chang <waynec@nvidia.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Sing-Han Chen <singhanc@nvidia.com>
Subject: Re: [PATCH v4 1/1] ucsi_ccg: Check DEV_INT bit only when starting CCG4
Date: Wed, 12 Jan 2022 08:41:50 +0000	[thread overview]
Message-ID: <0ba8f2bf-9b8b-04a6-e016-821200456100@nvidia.com> (raw)
In-Reply-To: <Yd6IVb5hsc2jpXqn@kuha.fi.intel.com>

Hi Heikki

Thanks for the review.

On 1/12/22 3:50 PM, Heikki Krogerus wrote:
> 
> 
> Hi,
> 
> On Wed, Jan 12, 2022 at 01:49:50PM +0800, Wayne Chang wrote:
>> From: Sing-Han Chen <singhanc@nvidia.com>
>>
>> after driver sending the UCSI_START cmd, CCGx would
>> clear Bit 0:Device Interrupt in the INTR_REG if CCGX
>> reset successfully.
>>
>> however, there might be a chance that other bits in
>> INTR_REG are not cleared due to internal data queued
>> in PPM and cause the driver thinks CCGx reset failed.
>>
>> the commit checks bit 0 in INTR_REG and ignore other
>> bits. ucsi driver would reset PPM later.
>>
>> Fixes: 247c554a14aa ("usb: typec: ucsi: add support for Cypress CCGx")
> 
> So... no need to take this to the stable kernel releases?
> 
Should I put cc tag here?
>> Signed-off-by: Sing-Han Chen <singhanc@nvidia.com>
>> Signed-off-by: Wayne Chang <waynec@nvidia.com>
>> ---
> 
> What has changed since v3 (and v2) - there is no patch changelog here?
> 
> In case this is new to you, you list those changes under that '---'
> line so they don't become part of the permanent changelog:
> 
> https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format
> 
The changes are resent for updating the commit messages.
Added the Fixes tag which Greg asked for.
Thanks for information. I went through the documents.
Should I put the following messages in the patch after "---" or should I use resend in subject 
for the commit messages updated?
v3 -> v4 commit messages updated
v2 -> v3 commit messages updated
v1 -> v2 commit messages updated
>>   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));
> 
> thanks,
> 
> --
> heikki
> 

thanks,
Wayne.

  reply	other threads:[~2022-01-12  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  5:49 [PATCH v4 1/1] ucsi_ccg: Check DEV_INT bit only when starting CCG4 Wayne Chang
2022-01-12  7:07 ` Greg KH
2022-01-12  7:50 ` Heikki Krogerus
2022-01-12  8:41   ` Wayne Chang [this message]
2022-01-12  9:09     ` Heikki Krogerus
2022-01-12  9:36       ` 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=0ba8f2bf-9b8b-04a6-e016-821200456100@nvidia.com \
    --to=waynec@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=singhanc@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;
as well as URLs for NNTP newsgroup(s).