[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR11MB0048B06F1FEB1EF7187B4AFAA9E3A@MWHPR11MB0048.namprd11.prod.outlook.com>
Date: Fri, 25 Aug 2023 21:04:29 +0000
From: "Patel, Utkarsh H" <utkarsh.h.patel@...el.com>
To: Prashant Malani <pmalani@...omium.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"heikki.krogerus@...ux.intel.com" <heikki.krogerus@...ux.intel.com>,
"bleung@...omium.org" <bleung@...omium.org>
Subject: RE: [PATCH v4 1/2] platform/chrome: cros_ec_typec: Configure Retimer
cable type
Hi Greg,
> > > >
> > > > We are only calling it once depending upon which mode we enter TBT
> > > > Alt or
> > > USB4.
> > >
> > > There should only be 1 "call site" and that should be sufficient to
> > > grab the VDO from the framework for all circumstances. Whether the
> > > other invocation doesn't get called under certain circumstances isn't as
> relevant.
> >
> > Are you suggesting something like this?
> >
> > static int cros_typec_configure_mux(struct cros_typec_data *typec, int
> port_num,)...
> >
> > if (port->mux_flags & USB_PD_MUX_USB4_ENABLED ||
> > port->mux_flags & USB_PD_MUX_TBT_COMPAT_ENABLED)
> > cable_tbt_vdo = cros_typec_get_cable_vdo(port,
> USB_TYPEC_TBT_SID);
>
> My apologies, I misread the patch. I think this looks good.
>
> Acked-by: Prashant Malani <pmalani@...omium.org>
Could you please add this patch to usb-next.
Sincerely,
Utkarsh Patel.
Powered by blists - more mailing lists