From: Kenneth Crudup <kenny@panix.com>
To: Hsin-Te Yuan <yuanhsinte@chromium.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Kenneth C <kenny@panix.com>
Subject: Re: [PATCH v4] usb: typec: ucsi: Get connector status after enable notifications
Date: Wed, 26 Nov 2025 10:25:45 -0800 [thread overview]
Message-ID: <75b9b15b-4473-4564-bf63-4511bef8ce6d@panix.com> (raw)
In-Reply-To: <20251125-ucsi-v4-1-8c94568ddaa5@chromium.org>
On 11/25/25 01:31, Hsin-Te Yuan wrote:
> Originally, the notification for connector change will be enabled after
> the first read of the connector status. Therefore, if the event happens
> during this window, it will be missing and make the status unsynced.
>
> Get the connector status only after enabling the notification for
> connector change to ensure the status is synced.
>
> Signed-off-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
> ---
> Changes in v4:
> - Handle a single connector in ucsi_init_port() and call it in a loop
> - Link to v3: https://lore.kernel.org/r/20251121-ucsi-v3-1-b1047ca371b8@chromium.org
Tested-By: Kenneth R. Crudup <kenny@panix.com>
> ---
> base-commit: 6a23ae0a96a600d1d12557add110e0bb6e32730c
> change-id: 20251117-ucsi-c2dfe8c006d7
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
prev parent reply other threads:[~2025-11-26 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 9:31 [PATCH v4] usb: typec: ucsi: Get connector status after enable notifications Hsin-Te Yuan
2025-11-25 11:46 ` Greg Kroah-Hartman
2025-11-26 9:02 ` Hsin-Te Yuan
2025-11-26 18:25 ` Kenneth Crudup [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=75b9b15b-4473-4564-bf63-4511bef8ce6d@panix.com \
--to=kenny@panix.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yuanhsinte@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