From: Devi Priya <quic_devipriy@quicinc.com>
To: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_arajkuma@quicinc.com>,
<quic_anusha@quicinc.com>, <quic_poovendh@quicinc.com>
Subject: [PATCH 0/2] Add initial support for RDP418 of IPQ9574 family
Date: Wed, 10 May 2023 16:13:57 +0530 [thread overview]
Message-ID: <20230510104359.16678-1-quic_devipriy@quicinc.com> (raw)
Add the initial device tree support for the Reference Design
Platform(RDP) 418 based on IPQ9574 family of SoC. This patch series adds
support for Console UART, SPI NOR, eMMC and SMPA1 regulator node.
Devi Priya (2):
dt-bindings: arm: qcom: document AL02-C2 board based on IPQ9574 family
arm64: dts: qcom: ipq9574: add support for RDP418 variant
.../devicetree/bindings/arm/qcom.yaml | 2 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/ipq9574-rdp418.dts | 124 ++++++++++++++++++
3 files changed, 127 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/ipq9574-rdp418.dts
base-commit: 52025ebbb518a2d876b8aba191b348ffb1cf368b
--
2.17.1
next reply other threads:[~2023-05-10 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 10:43 Devi Priya [this message]
2023-05-10 10:43 ` [PATCH 1/2] dt-bindings: arm: qcom: document AL02-C2 board based on " Devi Priya
2023-05-10 12:45 ` Krzysztof Kozlowski
2023-05-10 10:43 ` [PATCH 2/2] arm64: dts: qcom: ipq9574: add support for RDP418 variant Devi Priya
2023-05-16 13:57 ` [PATCH 0/2] Add initial support for RDP418 of IPQ9574 family Devi Priya
2023-05-26 19:38 ` Bjorn Andersson
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=20230510104359.16678-1-quic_devipriy@quicinc.com \
--to=quic_devipriy@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_poovendh@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@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®