From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: Retry if notification enable timesout
Date: Mon, 7 Sep 2026 13:05:55 +0200 [thread overview]
Message-ID: <ap6akwNAlqmJPMOz@black.igk.intel.com> (raw)
In-Reply-To: <b98ed1c6-37fb-4235-8ebd-df350728f797@app.fastmail.com>
On Thu, Sep 03, 2026 at 02:18:08PM -0400, Mark Pearson wrote:
> On Wed, Aug 5, 2026, at 8:03 AM, Heikki Krogerus wrote:
> > On Wed, Jul 29, 2026 at 02:21:50PM -0400, Mark Pearson wrote:
> >> Found on Thinkpad E14 G8.
> >> When UCSI notifications are enabled the FW does not ack the enablement
> >> itself. Future commands will be acked correctly.
> >>
> >> If this happens try enablement again and confirm acks are working
> >> correctly.
> >>
> >> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
> >
> > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> >
>
> Thanks Heikki.
>
> Just curious - what is the process/timelines for this subsystem for patch
> being accepted and making it into Linus's tree?
> We're tracking this for being able to get it into the distro's, but I want to
> make sure maintainers are happy with it first. I couldn't see it in usb-next
> etc, so wanted to make sure it hadn't fallen off the radar.
I'm sure Greg pick soon.
Thanks,
> Mark
>
> >> ---
> >> drivers/usb/typec/ucsi/ucsi.c | 6 ++++++
> >> 1 file changed, 6 insertions(+)
> >>
> >> diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
> >> index 49f1c53721bb..ea25c44c2850 100644
> >> --- a/drivers/usb/typec/ucsi/ucsi.c
> >> +++ b/drivers/usb/typec/ucsi/ucsi.c
> >> @@ -2082,6 +2082,12 @@ static int ucsi_init(struct ucsi *ucsi)
> >> ntfy = UCSI_ENABLE_NTFY_CMD_COMPLETE | UCSI_ENABLE_NTFY_ERROR;
> >> command = UCSI_SET_NOTIFICATION_ENABLE | ntfy;
> >> ret = ucsi_send_command(ucsi, command, NULL, 0);
> >> + /*
> >> + * Some FW may not ack the notification enable the first time.
> >> + * If this happens, repeat to confirm it is actually working
> >> + */
> >> + if (ret == -ETIMEDOUT)
> >> + ret = ucsi_send_command(ucsi, command, NULL, 0);
> >> if (ret < 0)
> >> goto err_reset;
> >>
> >> --
> >> 2.43.0
> >
> > --
> > heikki
--
heikki
prev parent reply other threads:[~2026-09-07 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 18:21 [PATCH] usb: typec: ucsi: Retry if notification enable timesout Mark Pearson
2026-08-05 12:03 ` Heikki Krogerus
2026-09-03 18:18 ` Mark Pearson
2026-09-07 11:05 ` Heikki Krogerus [this message]
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=ap6akwNAlqmJPMOz@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.