From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Jun Li <jun.li@nxp.com>
Cc: "linux@roeck-us.net" <linux@roeck-us.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 2/2] usb: typec: tcpm: set correct data role for non-DRD
Date: Thu, 9 Jan 2020 13:52:24 +0200 [thread overview]
Message-ID: <20200109115224.GC29437@kuha.fi.intel.com> (raw)
In-Reply-To: <1577442957-6921-1-git-send-email-jun.li@nxp.com>
Hi Jun,
Where's the 1/2 of this series?
On Fri, Dec 27, 2019 at 10:39:17AM +0000, Jun Li wrote:
> From: Li Jun <jun.li@nxp.com>
>
> Since the typec port data role is separated from power role,
> so check the port data capability when setting data role.
>
> Signed-off-by: Li Jun <jun.li@nxp.com>
> ---
> drivers/usb/typec/tcpm/tcpm.c | 24 +++++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
> index 56fc356..1f0d82e 100644
> --- a/drivers/usb/typec/tcpm/tcpm.c
> +++ b/drivers/usb/typec/tcpm/tcpm.c
> @@ -780,7 +780,7 @@ static int tcpm_set_roles(struct tcpm_port *port, bool attached,
> enum typec_role role, enum typec_data_role data)
> {
> enum typec_orientation orientation;
> - enum usb_role usb_role;
> + enum usb_role usb_role = USB_ROLE_NONE;
> int ret;
>
> if (port->polarity == TYPEC_POLARITY_CC1)
> @@ -788,10 +788,20 @@ static int tcpm_set_roles(struct tcpm_port *port, bool attached,
> else
> orientation = TYPEC_ORIENTATION_REVERSE;
>
> - if (data == TYPEC_HOST)
> - usb_role = USB_ROLE_HOST;
> - else
> - usb_role = USB_ROLE_DEVICE;
> + if (port->typec_caps.data == TYPEC_PORT_DRD) {
> + if (data == TYPEC_HOST)
> + usb_role = USB_ROLE_HOST;
> + else
> + usb_role = USB_ROLE_DEVICE;
> + } else if (port->typec_caps.data == TYPEC_PORT_DFP) {
> + if (data == TYPEC_HOST)
> + usb_role = USB_ROLE_HOST;
> + data = TYPEC_HOST;
So if data != host, tcpc is told that data == host, but the mux is set
to USB_ROLE_NONE. So why tcpc needs to think the role is host in that
case?
Shouldn't this function actually return error if the port is DFP only,
and TYPEC_DEVICE is requested?
> + } else {
> + if (data == TYPEC_DEVICE)
> + usb_role = USB_ROLE_DEVICE;
> + data = TYPEC_DEVICE;
> + }
>
> ret = tcpm_mux_set(port, TYPEC_STATE_USB, usb_role, orientation);
> if (ret < 0)
> @@ -1817,7 +1827,7 @@ static void tcpm_pd_ctrl_request(struct tcpm_port *port,
> tcpm_set_state(port, SOFT_RESET, 0);
> break;
> case PD_CTRL_DR_SWAP:
> - if (port->port_type != TYPEC_PORT_DRP) {
> + if (port->typec_caps.data != TYPEC_PORT_DRD) {
> tcpm_queue_message(port, PD_MSG_CTRL_REJECT);
> break;
> }
> @@ -3969,7 +3979,7 @@ static int tcpm_dr_set(struct typec_port *p, enum typec_data_role data)
> mutex_lock(&port->swap_lock);
> mutex_lock(&port->lock);
>
> - if (port->port_type != TYPEC_PORT_DRP) {
> + if (port->typec_caps.data != TYPEC_PORT_DRD) {
> ret = -EINVAL;
> goto port_unlock;
> }
> --
> 2.7.4
thanks,
--
heikki
next prev parent reply other threads:[~2020-01-09 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 10:39 [PATCH 2/2] usb: typec: tcpm: set correct data role for non-DRD Jun Li
2020-01-09 11:52 ` Heikki Krogerus [this message]
2020-01-10 10:41 ` Jun Li
2020-01-20 13:51 ` Heikki Krogerus
2020-01-21 4:01 ` Jun Li
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=20200109115224.GC29437@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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).