From: Bjorn Andersson <andersson@kernel.org>
To: robh+dt@kernel.org, quic_molvera@quicinc.com, agross@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@linaro.org
Cc: linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org,
quic_tdas@quicinc.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] clk: qcom: Add clocks for the QDU1000 and QRU1000 SoCs
Date: Wed, 18 Jan 2023 20:42:51 -0600 [thread overview]
Message-ID: <167409616956.3024582.17239635574684353077.b4-ty@kernel.org> (raw)
In-Reply-To: <20230112204446.30236-1-quic_molvera@quicinc.com>
On Thu, 12 Jan 2023 12:44:44 -0800, Melody Olvera wrote:
> This series adds the GCC, RPMh, and PDC clock support required for the
> QDU1000 and QRU1000 SoCs along with the devicetree bindings for them.
>
> 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] dt-bindings: clock: Add QDU1000 and QRU1000 GCC clocks
commit: f636dee9b60dd1cc4d8dcac98cf975991bc12d58
[2/2] clk: qcom: Add QDU1000 and QRU1000 GCC support
commit: 475b330cca2acbf19a00e80a12c66919209b0183
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-01-19 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 20:44 Melody Olvera
2023-01-12 20:44 ` [PATCH v6 1/2] dt-bindings: clock: Add QDU1000 and QRU1000 GCC clocks Melody Olvera
2023-01-13 8:43 ` Krzysztof Kozlowski
2023-01-12 20:44 ` [PATCH v6 2/2] clk: qcom: Add QDU1000 and QRU1000 GCC support Melody Olvera
2023-01-12 21:15 ` Dmitry Baryshkov
2023-01-19 2:44 ` Bjorn Andersson
2023-01-19 2:42 ` 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=167409616956.3024582.17239635574684353077.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-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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®