From: "Mani, Rajmohan" <rajmohan.mani@intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: RE: [PATCH 1/2] platform/chrome: cros_ec_typec: Skip port partner check in configure_mux()
Date: Fri, 5 Feb 2021 22:56:20 +0000 [thread overview]
Message-ID: <DM6PR11MB3963CE613ED4F666EBDA27E6F6B29@DM6PR11MB3963.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACeCKadzdTGi3y_WbihX_p_rfL8wcTFVwbUGPU=de53fA9dVog@mail.gmail.com>
Hi Prashant,
> -----Original Message-----
> From: Prashant Malani <pmalani@chromium.org>
> Sent: Friday, February 05, 2021 12:07 PM
> To: Mani, Rajmohan <rajmohan.mani@intel.com>
> Cc: Benson Leung <bleung@chromium.org>; Enric Balletbo i Serra
> <enric.balletbo@collabora.com>; Guenter Roeck <groeck@chromium.org>;
> Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Heikki Krogerus
> <heikki.krogerus@linux.intel.com>
> Subject: Re: [PATCH 1/2] platform/chrome: cros_ec_typec: Skip port partner
> check in configure_mux()
>
> Hi Raj,
>
> On Fri, Feb 5, 2021 at 11:52 AM Rajmohan Mani
> <rajmohan.mani@intel.com> wrote:
> >
> > For certain needs like updating the USB4 retimer firmware when no
> > device are connected, the Type-C ports require mux configuration, to
> > be able to communicate with the retimer. So removed the above check to
> > allow for mux configuration of Type-C ports, to enable retimer
> > communication.
> >
> > Signed-off-by: Rajmohan Mani <rajmohan.mani@intel.com>
> Reviewed-by: Prashant Malani <pmalani@chromium.org>
>
Thanks for the review of the patch series.
> > ---
> > drivers/platform/chrome/cros_ec_typec.c | 3 ---
> > 1 file changed, 3 deletions(-)
> >
> > diff --git a/drivers/platform/chrome/cros_ec_typec.c
> > b/drivers/platform/chrome/cros_ec_typec.c
> > index e724a5eaef1c..3d8ff3f8a514 100644
> > --- a/drivers/platform/chrome/cros_ec_typec.c
> > +++ b/drivers/platform/chrome/cros_ec_typec.c
> > @@ -536,9 +536,6 @@ static int cros_typec_configure_mux(struct
> cros_typec_data *typec, int port_num,
> > enum typec_orientation orientation;
> > int ret;
> >
> > - if (!port->partner)
> > - return 0;
> > -
> > if (mux_flags & USB_PD_MUX_POLARITY_INVERTED)
> > orientation = TYPEC_ORIENTATION_REVERSE;
> > else
> > --
> > 2.30.0
> >
next prev parent reply other threads:[~2021-02-06 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 19:51 [PATCH 0/2] Add support for Type-C mux events without port partners Rajmohan Mani
2021-02-05 19:51 ` [PATCH 1/2] platform/chrome: cros_ec_typec: Skip port partner check in configure_mux() Rajmohan Mani
2021-02-05 20:07 ` Prashant Malani
2021-02-05 22:56 ` Mani, Rajmohan [this message]
2021-02-05 19:51 ` [PATCH 2/2] platform/chrome: cros_ec_types: Support disconnect events without partners Rajmohan Mani
2021-02-05 20:05 ` Prashant Malani
2021-02-05 20:06 ` Prashant Malani
2021-02-06 0:59 ` [PATCH 0/2] Add support for Type-C mux events without port partners Benson Leung
2021-02-06 1:26 ` Mani, Rajmohan
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=DM6PR11MB3963CE613ED4F666EBDA27E6F6B29@DM6PR11MB3963.namprd11.prod.outlook.com \
--to=rajmohan.mani@intel.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
/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®