[SRU] [Unstable/OEM-5.14] [PATCH 0/7] Improve USB Type-C support

[Kai-Heng Feng]

On Wed, Dec 15, 2021 at 4:27 PM Timo Aaltonen <tjaalton at ubuntu.com> wrote:
>
> On 15.12.2021 5.17, Kai-Heng Feng wrote:
> > On Tue, Dec 14, 2021 at 11:06 PM Timo Aaltonen <tjaalton at ubuntu.com> wrote:
> >>
> >> On 16.11.2021 3.38, Kai-Heng Feng wrote:
> >>> BugLink: https://bugs.launchpad.net/bugs/1950974
> >>>
> >>> [Impact]
> >>> Error message "ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-110)"
> >>> can be found on many systems.
> >>>
> >>> [Fix]
> >>> The main issue is that the PD firmware is unreliable, so use more
> >>> deterministic methods to make it reliable
> >>>
> >>> [Test]
> >>> The error message is gone. Also tried to plug/unplug USB Type-C power
> >>> cord, and the status are always reported correctly.
> >>>
> >>> [Where problems could occur]
> >>> This is quite a huge refactor, so regression can be expected. Only
> >>> target to unstable and latest OEM kernel to reduce risk we are taking.
> >>>
> >>> Heikki Krogerus (7):
> >>>     usb: typec: ucsi: Always cancel the command if PPM reports BUSY
> >>>       condition
> >>>     usb: typec: ucsi: Don't stop alt mode registration on busy condition
> >>>     usb: typec: ucsi: Add polling mechanism for partner tasks like alt
> >>>       mode checking
> >>>     usb: typec: ucsi: acpi: Reduce the command completion timeout
> >>>     usb: typec: ucsi: Check the partner alt modes always if there is PD
> >>>       contract
> >>>     usb: typec: ucsi: Read the PDOs in separate work
> >>>     usb: typec: ucsi: Better fix for missing unplug events issue
> >>>
> >>>    drivers/usb/typec/ucsi/ucsi.c      | 337 ++++++++++++++---------------
> >>>    drivers/usb/typec/ucsi/ucsi.h      |   3 +-
> >>>    drivers/usb/typec/ucsi/ucsi_acpi.c |   2 +-
> >>>    3 files changed, 167 insertions(+), 175 deletions(-)
> >>>
> >>
> >> What's the plan to get this in jammy/5.15? Remember that the upgrade
> >> path for oem-5.14 is hwe-5.15..
> >
> > Isn't Jammy going to base on Unstable tree (5.15)?
>
> Jammy already has 5.15, unstable is tracking 5.16/5.17 at this point.

I think Jammy tree wasn't existed when I sent this, and Unstable was
5.15 at that time.

So do I resend this to Jammy too?

Kai-Heng

>
>
> --
> t