linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yang <xu.yang_2@nxp.com>
To: Guenter Roeck <linux@roeck-us.net>,
	"heikki.krogerus@linux.intel.com"
	<heikki.krogerus@linux.intel.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>, Jun Li <jun.li@nxp.com>
Subject: RE: [EXT] Re: [PATCH] usb: typec: tcpm: fix create duplicate source/sink-capabilities file
Date: Mon, 9 Jan 2023 00:35:20 +0000	[thread overview]
Message-ID: <DB7PR04MB4505A0A29918EC71FDF5C8BC8CFE9@DB7PR04MB4505.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <PA4PR04MB959190B619279B290630D8018CE69@PA4PR04MB9591.eurprd04.prod.outlook.com>

Hi,

> -----Original Message-----
> From: Xu Yang
> Sent: Friday, December 16, 2022 2:41 PM
> To: Guenter Roeck <linux@roeck-us.net>; heikki.krogerus@linux.intel.com
> Cc: gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; dl-linux-imx <linux-imx@nxp.com>; Jun Li <jun.li@nxp.com>
> Subject: RE: [EXT] Re: [PATCH] usb: typec: tcpm: fix create duplicate source/sink-capabilities file
> 
> Hi Guenter,
> 
> > -----Original Message-----
> > From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
> > Sent: Friday, December 16, 2022 1:13 PM
> > To: Xu Yang <xu.yang_2@nxp.com>; heikki.krogerus@linux.intel.com
> > Cc: gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; dl-linux-imx <linux-imx@nxp.com>; Jun Li <jun.li@nxp.com>
> > Subject: [EXT] Re: [PATCH] usb: typec: tcpm: fix create duplicate source/sink-capabilities file
> >
> > Caution: EXT Email
> >
> > On 12/15/22 19:31, Xu Yang wrote:
> > > After soft reset has completed, an Explicit Contract negotiation occurs.
> > > The sink device will receive source capabilitys again. This will cause
> > > a duplicate source-capabilities file be created.
> > >
> > > And the kernel will dump:
> > > sysfs: cannot create duplicate filename '/devices/virtual/usb_power_delivery/pd1/source-capabilities'
> > >
> > > This will unregister existing capabilities before register new one.
> > >
> > > Fixes: 8203d26905ee ("usb: typec: tcpm: Register USB Power Delivery Capabilities")
> > > cc: <stable@vger.kernel.org>
> > > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > > ---
> > >   drivers/usb/typec/tcpm/tcpm.c | 6 ++++++
> > >   1 file changed, 6 insertions(+)
> > >
> > > diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
> > > index 904c7b4ce2f0..02d8a704db95 100644
> > > --- a/drivers/usb/typec/tcpm/tcpm.c
> > > +++ b/drivers/usb/typec/tcpm/tcpm.c
> > > @@ -2371,6 +2371,9 @@ static int tcpm_register_source_caps(struct tcpm_port *port)
> > >       if (IS_ERR(port->partner_pd))
> > >               return PTR_ERR(port->partner_pd);
> > >
> > > +     /* remove existing capabilities since got new one */
> > > +     usb_power_delivery_unregister_capabilities(port->partner_source_caps);
> > > +
> > >       memcpy(caps.pdo, port->source_caps, sizeof(u32) * port->nr_source_caps);
> > >       caps.role = TYPEC_SOURCE;
> > >
> > > @@ -2394,6 +2397,9 @@ static int tcpm_register_sink_caps(struct tcpm_port *port)
> > >       if (IS_ERR(port->partner_pd))
> > >               return PTR_ERR(port->partner_pd);
> > >
> > > +     /* remove existing capabilities since got new one */
> > > +     usb_power_delivery_unregister_capabilities(port->partner_sink_caps);
> > > +
> > >       memcpy(caps.pdo, port->sink_caps, sizeof(u32) * port->nr_sink_caps);
> > >       caps.role = TYPEC_SINK;
> > >
> >
> > Shouldn't usb_power_delivery_unregister_capabilities() be called from
> > the SOFT_RESET state handler ?
> 
> Although this issue is triggered by soft reset event, there is also
> other possibilities which may produce this behavior. Such as received
> 2rd source capability or use Get_Source_Cap message. It's a dynamic
> process even after source/sink is ready. So I think it's better to handle
> it in tcpm_register_source/sink_caps(). Not sure if this is reasonable.
> 
> Thanks,
> Xu Yang

Do you have any other comments or suggestions with this patch?

Thanks,
Xu Yang

> 
> >
> > Guenter


  reply	other threads:[~2023-01-09  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  3:31 [PATCH] usb: typec: tcpm: fix create duplicate source/sink-capabilities file Xu Yang
2022-12-16  5:13 ` Guenter Roeck
2022-12-16  6:40   ` [EXT] " Xu Yang
2023-01-09  0:35     ` Xu Yang [this message]
2023-01-10 15:01       ` Guenter Roeck
2023-01-11 13:39         ` Xu Yang

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=DB7PR04MB4505A0A29918EC71FDF5C8BC8CFE9@DB7PR04MB4505.eurprd04.prod.outlook.com \
    --to=xu.yang_2@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jun.li@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).