From: Bjorn Andersson <andersson@kernel.org>
To: quic_molvera@quicinc.com, krzysztof.kozlowski+dt@linaro.org,
Andy Gross <agross@kernel.org>,
konrad.dybcio@linaro.org, robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Add base device tree files for QDU1000/QRU1000
Date: Mon, 30 Jan 2023 17:46:11 -0600 [thread overview]
Message-ID: <167512236604.4092892.10258510885495297697.b4-ty@kernel.org> (raw)
In-Reply-To: <20230112210722.6234-1-quic_molvera@quicinc.com>
On Thu, 12 Jan 2023 13:07:20 -0800, Melody Olvera wrote:
> This series adds the base device tree files and DTS support for the
> Qualcomm QDU1000 and QRU1000 IDP SoCs, including the clocks, tlmm, smmu,
> regulators, mmc, interconnects, cpufreq, and qup.
>
> This patchset requires the dt-bindings changes from [1-3].
>
> The Qualcomm Technologies, Inc. Distributed Unit 1000 and Radio Unit
> 1000 are new SoCs meant for enabling Open RAN solutions. See more at
> https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets/documents/qualcomm_5g_ran_platforms_product_brief.pdf
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: Add base QDU1000/QRU1000 DTSIs
commit: b441a026ae1a5d269ec0ee768681b55294a72621
[2/2] arm64: dts: qcom: Add base QDU1000/QRU1000 IDP DTs
commit: e5768f7a804acdae33d5e02325dd4b67c3883593
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-01-30 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:07 [PATCH v6 0/2] Add base device tree files for QDU1000/QRU1000 Melody Olvera
2023-01-12 21:07 ` [PATCH v6 1/2] arm64: dts: qcom: Add base QDU1000/QRU1000 DTSIs Melody Olvera
2023-01-20 21:22 ` Konrad Dybcio
2023-01-12 21:07 ` [PATCH v6 2/2] arm64: dts: qcom: Add base QDU1000/QRU1000 IDP DTs Melody Olvera
2023-01-20 21:13 ` [PATCH v6 0/2] Add base device tree files for QDU1000/QRU1000 Melody Olvera
2023-01-30 23:46 ` Bjorn Andersson [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=167512236604.4092892.10258510885495297697.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@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_molvera@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;
as well as URLs for NNTP newsgroup(s).