From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Prashanth K <prashanth.k@oss.qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: Get the connector fwnode based on reg value
Date: Fri, 18 Sep 2026 11:18:13 +0200 [thread overview]
Message-ID: <aq0B1fbrqk5_ppsv@black.igk.intel.com> (raw)
In-Reply-To: <20260916042808.2879079-1-prashanth.k@oss.qualcomm.com>
On Wed, Sep 16, 2026 at 09:58:08AM +0530, Prashanth K wrote:
> ucsi_find_fwnode() currently maps UCSI connectors to Device tree
> connector nodes based on the order in which connector child nodes
> are described in DT.
>
> This can fail because the ordering of child nodes isn't guaranteed
> in Device-tree. For example, DTB may contain connector@1 before
> connector@0, causing connector numbers to be associated with the wrong
> fwnode. As a result, role switch and Type-C notifications can be
> delivered to the wrong remote endpoints.
>
> Fix this by using the "reg" property of each connector to match
> its corresponding fwnode. While at it, if the reg property isn't
> present, then fall back to the old method.
>
> Fixes: c1b0bc2dabfa ("usb: typec: Add support for UCSI interface")
That commit does not yet include any kind of support for DT.
Thanks,
> Cc: stable@vger.kernel.org
> Signed-off-by: Prashanth K <prashanth.k@oss.qualcomm.com>
> ---
> drivers/usb/typec/ucsi/ucsi.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
> index bef3f9b71d71..c1450639c795 100644
> --- a/drivers/usb/typec/ucsi/ucsi.c
> +++ b/drivers/usb/typec/ucsi/ucsi.c
> @@ -1801,10 +1801,21 @@ static struct fwnode_handle *ucsi_find_fwnode(struct ucsi_connector *con)
> {
> struct fwnode_handle *fwnode;
> int i = 1;
> + int ret;
> + u32 port;
>
> - device_for_each_child_node(con->ucsi->dev, fwnode)
> - if (i++ == con->num)
> - return fwnode;
> + device_for_each_child_node(con->ucsi->dev, fwnode) {
> + ret = fwnode_property_read_u32(fwnode, "reg", &port);
> + if (ret < 0) {
> + if (i == con->num)
> + return fwnode;
> + } else {
> + if (port == con->num - 1)
> + return fwnode;
> + }
> +
> + i++;
> + }
> return NULL;
> }
>
> --
> 2.34.1
--
heikki
prev parent reply other threads:[~2026-09-18 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 4:28 Prashanth K
2026-09-18 9:18 ` 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=aq0B1fbrqk5_ppsv@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=prashanth.k@oss.qualcomm.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®