From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Prashant Malani <pmalani@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Rajmohan Mani <rajmohan.mani@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH v2] platform/chrome: cros_ec_typec: USB4 support
Date: Wed, 22 Jul 2020 17:27:32 +0200 [thread overview]
Message-ID: <d09324a9-0a3e-3dd5-5521-dcd2d04a9d3f@collabora.com> (raw)
In-Reply-To: <CACeCKadwsH2yhqegZubgJnLy+p0CM3H1DzXiA-72Gagy2aYB-A@mail.gmail.com>
Hi Prashant,
On 21/7/20 21:55, Prashant Malani wrote:
> Hey Enric, Benson,
>
> Just wondering if you've had a chance to review this patch.
>
It's on my radar but I'm waiting for the dependencies to be merged.
> Best regards,
>
> -Prashant
>
> On Fri, Jul 10, 2020 at 12:40 PM Prashant Malani <pmalani@chromium.org> wrote:
>>
>> From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>>
>> With USB4 mode the mux driver needs the Enter_USB Data
>> Object (EUDO) that was used when the USB mode was entered.
>> Though the object is not available in the driver, it is
>> possible to construct it from the information we have.
>>
>> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>> Signed-off-by: Prashant Malani <pmalani@chromium.org>
For my own reference:
Acked-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>> ---
>>
>> This patch depends on latest usb-next from Greg KH, this commit in
>> particular:
>> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=ad8db94d6813dc659bd4de0531a8a1150559eafb
>>
>> Changes in v2:
>> - Removed EUDO bits for cable current and tunneling support.
>>
>> drivers/platform/chrome/cros_ec_typec.c | 33 ++++++++++++++++++++++++-
>> 1 file changed, 32 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/platform/chrome/cros_ec_typec.c b/drivers/platform/chrome/cros_ec_typec.c
>> index 0c041b79cbba..a9700275a851 100644
>> --- a/drivers/platform/chrome/cros_ec_typec.c
>> +++ b/drivers/platform/chrome/cros_ec_typec.c
>> @@ -13,6 +13,7 @@
>> #include <linux/platform_data/cros_ec_proto.h>
>> #include <linux/platform_data/cros_usbpd_notify.h>
>> #include <linux/platform_device.h>
>> +#include <linux/usb/pd.h>
>> #include <linux/usb/typec.h>
>> #include <linux/usb/typec_altmode.h>
>> #include <linux/usb/typec_dp.h>
>> @@ -494,6 +495,34 @@ static int cros_typec_enable_dp(struct cros_typec_data *typec,
>> return typec_mux_set(port->mux, &port->state);
>> }
>>
>> +static int cros_typec_enable_usb4(struct cros_typec_data *typec,
>> + int port_num,
>> + struct ec_response_usb_pd_control_v2 *pd_ctrl)
>> +{
>> + struct cros_typec_port *port = typec->ports[port_num];
>> + struct enter_usb_data data;
>> +
>> + data.eudo = EUDO_USB_MODE_USB4 << EUDO_USB_MODE_SHIFT;
>> +
>> + /* Cable Speed */
>> + data.eudo |= pd_ctrl->cable_speed << EUDO_CABLE_SPEED_SHIFT;
>> +
>> + /* Cable Type */
>> + if (pd_ctrl->control_flags & USB_PD_CTRL_OPTICAL_CABLE)
>> + data.eudo |= EUDO_CABLE_TYPE_OPTICAL << EUDO_CABLE_TYPE_SHIFT;
>> + else if (pd_ctrl->control_flags & USB_PD_CTRL_ACTIVE_CABLE)
>> + data.eudo |= EUDO_CABLE_TYPE_RE_TIMER << EUDO_CABLE_TYPE_SHIFT;
>> +
>> + data.active_link_training = !!(pd_ctrl->control_flags &
>> + USB_PD_CTRL_ACTIVE_LINK_UNIDIR);
>> +
>> + port->state.alt = NULL;
>> + port->state.data = &data;
>> + port->state.mode = TYPEC_MODE_USB4;
>> +
>> + return typec_mux_set(port->mux, &port->state);
>> +}
>> +
>> static int cros_typec_configure_mux(struct cros_typec_data *typec, int port_num,
>> uint8_t mux_flags,
>> struct ec_response_usb_pd_control_v2 *pd_ctrl)
>> @@ -514,7 +543,9 @@ static int cros_typec_configure_mux(struct cros_typec_data *typec, int port_num,
>> if (ret)
>> return ret;
>>
>> - if (mux_flags & USB_PD_MUX_TBT_COMPAT_ENABLED) {
>> + if (mux_flags & USB_PD_MUX_USB4_ENABLED) {
>> + ret = cros_typec_enable_usb4(typec, port_num, pd_ctrl);
>> + } else if (mux_flags & USB_PD_MUX_TBT_COMPAT_ENABLED) {
>> ret = cros_typec_enable_tbt(typec, port_num, pd_ctrl);
>> } else if (mux_flags & USB_PD_MUX_DP_ENABLED) {
>> ret = cros_typec_enable_dp(typec, port_num, pd_ctrl);
>> --
>> 2.27.0.383.g050319c2ae-goog
>>
next prev parent reply other threads:[~2020-07-22 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 19:40 Prashant Malani
2020-07-21 19:55 ` Prashant Malani
2020-07-22 15:27 ` Enric Balletbo i Serra [this message]
2020-07-24 0:47 ` Prashant Malani
2020-09-01 9:08 ` Enric Balletbo i Serra
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=d09324a9-0a3e-3dd5-5521-dcd2d04a9d3f@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rajmohan.mani@intel.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®