From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Elson Serrao <elson.serrao@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] dt-bindings: connector: Add role‑switch provider phandle
Date: Wed, 11 Mar 2026 15:23:26 +0200 [thread overview]
Message-ID: <abFszhkrN_X1ax8U@kuha> (raw)
In-Reply-To: <c57cc1cd-c7cd-41d5-adef-c2e69de72f46@oss.qualcomm.com>
Mon, Mar 09, 2026 at 01:41:20PM -0700, Elson Serrao kirjoitti:
>
>
> On 2/24/2026 10:56 AM, Elson Serrao wrote:
> > +Heikki Krogerus <heikki.krogerus@linux.intel.com>
> >
> > Adding Heikki since this relates to usb-role-switch provider modeling.
> >
> > Thanks,
> > Elson
> >
> > On 2/23/2026 11:10 AM, Elson Serrao wrote:
> >> Hi all,
> >>
> >> This RFC proposes a generic Devicetree mechanism for a USB connector to
> >> reference the USB role‑switch provider when there is an intermediate,
> >> block between the connector and the controller in the OF graph.
> >>
> >> Problem
> >> =======
> >> OF‑graph links are strictly point‑to‑point via remote-endpoint, so a
> >> consumer can only discover its immediate neighbor in the graph. When an
> >> intermediate node sits between the USB connector and the controller, the
> >> connector cannot identify the controller (the role‑switch provider) from
> >> the graph alone.
> >>
>
> [...]
>
> Gentle ping on this RFC.
>
> When you have a moment, I’d appreciate guidance on whether the proposed
> modeling direction looks acceptable.
>
> For context only, the following DTS patch illustrates this modeling:
> https://lore.kernel.org/all/20260309203337.803986-11-elson.serrao@oss.qualcomm.com/
FWIW you proposal is okay by me.
thanks,
--
heikki
prev parent reply other threads:[~2026-03-11 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:10 [RFC PATCH 0/1] dt-bindings: connector: Add role‑switch provider phandle Elson Serrao
2026-02-23 19:10 ` [RFC PATCH 1/1] " Elson Serrao
2026-02-24 18:56 ` [RFC PATCH 0/1] " Elson Serrao
2026-03-09 20:41 ` Elson Serrao
2026-03-11 13:23 ` 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=abFszhkrN_X1ax8U@kuha \
--to=heikki.krogerus@linux.intel.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=elson.serrao@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_wcheng@quicinc.com \
--cc=robh@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