ucsi_ccg: Check DEV_INT bit only when starting CCG4
Subsystems (2)
PATCH v3 1/1 ucsi_ccg: Check DEV_INT bit only when starting CCG4
From: Sing-Han Chen <[email protected]>
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.
--- drivers/usb/typec/ucsi/ucsi_ccg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/typec/ucsi/ucsi_ccg.c +1 -1
@@ -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));
Signature · 1 line
2.25.1
Greg KH
maintainerQuoted 36 lines · Wayne Chang
From: Sing-Han Chen <[email protected]>
after driver sending the
UCSI_STARTcmd, CCGx would clear Bit 0:Device Interrupt in theINTR_REGif CCGX reset successfully.however, there might be a chance that other bits in
INTR_REGare not cleared due to internal data queued in PPM and cause the driver thinks CCGx reset failed.the commit checks bit 0 in
INTR_REGand ignore other bits. ucsi driver would reset PPM later.Fixes 247c554a14aa16ca ("usb: typec: ucsi: add support for Cypress CCGx")Signed-off-by Sing-Han Chen <[email protected]>Signed-off-by Wayne Chang <[email protected]>--- drivers/usb/typec/ucsi/ucsi_ccg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/usb/typec/ucsi/ucsi_ccg.c +1
-1@@ -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));Signature · 1 line
2.25.1
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot