From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Zhang Jiaxi <Z1529105815@outlook.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 2/2] arm64: dts: qcom: Add a minimal Xiaomi Warsaw description
Date: Mon, 26 Oct 2026 13:39:19 +0100 [thread overview]
Message-ID: <2c20fe9f-c117-47de-aeca-2641abcb4b66@oss.qualcomm.com> (raw)
In-Reply-To: <SY5PR01MB10600F961AC57A32262D99ECCA1662@SY5PR01MB10600.ausprd01.prod.outlook.com>
On 10/21/26 2:52 PM, Zhang Jiaxi wrote:
> Hi Konrad,
>
> Thank you for reviewing v2. I have posted RFC v3:
> https://lore.kernel.org/all/20261021-b4-warsaw-minimal-usb2-v3-0-9f4213ab83ef@outlook.com/
>
> It updates the model name, node ordering, common PMIC include and GPIO
> reservation comments. The cover describes the revised DT's bounded
> native core/USB test and the Codex/LLM assistance used.
>
> USB remains restricted to High-Speed peripheral mode in this RFC. The OEM
> configuration retains OTG/UCSI role switching, so this is not a claim of
> peripheral-only hardware. I would appreciate your guidance on whether
> that explicit initial restriction is acceptable, or USB should remain
> disabled until the dual-role board integration is included.
It's fine
Konrad
prev parent reply other threads:[~2026-10-26 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:51 [PATCH RFC v2 0/2] arm64: dts: qcom: introduce minimal Xiaomi Warsaw support Zhang Jiaxi
2026-10-16 15:53 ` [PATCH RFC v2 1/2] dt-bindings: arm: qcom: Add Xiaomi Warsaw Zhang Jiaxi
2026-10-16 15:53 ` [PATCH RFC v2 2/2] arm64: dts: qcom: Add a minimal Xiaomi Warsaw description Zhang Jiaxi
2026-10-21 10:32 ` Konrad Dybcio
2026-10-21 12:52 ` Zhang Jiaxi
2026-10-26 12:39 ` Konrad Dybcio [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=2c20fe9f-c117-47de-aeca-2641abcb4b66@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Z1529105815@outlook.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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
all inboxes | Powered by JetHome®