Re: [PATCH] platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags

On Thu, 5 Nov 2020 18:03:05 -0800, Prashant Malani wrote: > On occasion, the Chrome Embedded Controller (EC) can send a mux > configuration which doesn't map to a particular data mode. For instance, > dedicated Type C chargers, when connected, may cause only > USB_PD_MUX_POLARITY_INVERTED to be

Re: [PATCH] platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags

Friendly ping. If there are not other reservations, can we pick this patch? It doesn't depend on any other patch series. Thanks, On Thu, Nov 19, 2020 at 11:32 PM Heikki Krogerus wrote: > > On Thu, Nov 05, 2020 at 06:03:05PM -0800, Prashant Malani wrote: > > On occasion, the Chrome Embedded

Re: [PATCH] platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags

On Thu, Nov 05, 2020 at 06:03:05PM -0800, Prashant Malani wrote: > On occasion, the Chrome Embedded Controller (EC) can send a mux > configuration which doesn't map to a particular data mode. For instance, > dedicated Type C chargers, when connected, may cause only > USB_PD_MUX_POLARITY_INVERTED

Re: [PATCH] platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags

Including Heikki, who I forgot to add in the original patch email. On Thu, Nov 05, 2020 at 06:03:05PM -0800, Prashant Malani wrote: > On occasion, the Chrome Embedded Controller (EC) can send a mux > configuration which doesn't map to a particular data mode. For instance, > dedicated Type C

[PATCH] platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags

On occasion, the Chrome Embedded Controller (EC) can send a mux configuration which doesn't map to a particular data mode. For instance, dedicated Type C chargers, when connected, may cause only USB_PD_MUX_POLARITY_INVERTED to be set. This is a valid flag combination and should not lead to a