Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akash Kumar <akash.kumar@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: qcom: talos: Add graph port placeholders for USB Type-C muxing
Date: Tue, 17 Nov 2026 13:17:21 +0100	[thread overview]
Message-ID: <f21c77ee-44da-4a1a-a289-d4ea9cbe158f@kernel.org> (raw)
In-Reply-To: <20261116114411.1700153-1-akash.kumar@oss.qualcomm.com>

On 16/11/2026 12:43, Akash Kumar wrote:
> Add empty port/endpoint nodes on the primary USB QMP PHY (usb_qmpphy)
> and the usb_1/usb_2 dwc3 controllers, along with orientation-switch on
> the PHY. These placeholders let board files wire up a USB-C PD
> controller's HS/SS endpoints directly via
> &label { remote-endpoint = <...>; }; instead of redeclaring the
> port/ports structure on the shared nodes.
> 
> Signed-off-by: Akash Kumar <akakum@qti.qualcomm.com>

Why isn't this part of proper patchset using it? Why Talos Lyra has 5
independent patches, all built on top of each other or cross-depending
while nothing is merged?

Best regards,
Krzysztof

      reply	other threads:[~2026-11-17 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 11:43 [PATCH v2 1/2] arm64: dts: qcom: talos: Add graph port placeholders for USB Type-C muxing Akash Kumar
2026-11-17 12:17 ` Krzysztof Kozlowski [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=f21c77ee-44da-4a1a-a289-d4ea9cbe158f@kernel.org \
    --to=krzk@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=akash.kumar@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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