From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Zhang Jiaxi <Z1529105815@outlook.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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: [RFC PATCH 2/2] arm64: dts: qcom: Add a minimal Xiaomi Warsaw description
Date: Tue, 13 Oct 2026 10:13:54 +0200 [thread overview]
Message-ID: <cc9c2f25-aaaa-4113-83d8-4965822e4fce@oss.qualcomm.com> (raw)
In-Reply-To: <SY5PR01MB10600FCBB6CF8F9233D1214BBA1932@SY5PR01MB10600.ausprd01.prod.outlook.com>
On 10/9/26 12:34 AM, Zhang Jiaxi wrote:
> From: Jiaxi Zhang <z1529105815@outlook.com>
>
> Add the board identity, reference clocks, PM8550/PMK8550 devices and
> keys used by the v165 board. Retain its inherited debug UART alias,
> stdout selection and QUP wrapper enable. Keep peripheral bring-up
> and the Android bootloader memory contract in separate drafts.
>
> Describe the board from the SoC and PMIC includes, rather than
> inheriting all peripherals of the SM8750 MTP board. Reference clocks
> and key pin configuration are retained from the MTP description
> included by the existing Warsaw BSP.
>
> Signed-off-by: Jiaxi Zhang <z1529105815@outlook.com>
>
> ---
> This revised minimal board has not been boot-tested.
Please test it.
Konrad
prev parent reply other threads:[~2026-10-13 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:34 Zhang Jiaxi
2026-10-13 8:13 ` 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=cc9c2f25-aaaa-4113-83d8-4965822e4fce@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=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
all inboxes | Powered by JetHome®