From: Melody Olvera <quic_molvera@quicinc.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] dt-bindings: clock: Introduce pdc bindings for QDU1000 and QRU1000
Date: Mon, 3 Oct 2022 14:47:04 -0500 [thread overview]
Message-ID: <55d28ebc-e061-7b5e-99f9-f34f2b0e9af8@quicinc.com> (raw)
In-Reply-To: <114fb5a01a422c15997a9a4daebce584@kernel.org>
On 10/1/2022 4:22 AM, Marc Zyngier wrote:
> On 2022-10-01 04:04, Melody Olvera wrote:
>> Add compatible fields for QDU1000 and QRU1000 pdcs.
>>
>> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
>> ---
>> .../devicetree/bindings/interrupt-controller/qcom,pdc.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
>> b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
>> index b6f56cf5fbe3..5c7b790db7e0 100644
>> --- a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
>> +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
>> @@ -33,6 +33,8 @@ properties:
>> - qcom,sm8150-pdc
>> - qcom,sm8250-pdc
>> - qcom,sm8350-pdc
>> + - qcom,qdu1000-pdc
>> + - qcom,qru1000-pdc
>> - const: qcom,pdc
>>
>> reg:
>
> Please fix the title of the commit, as this has little to do with clocks.
Will do.
>
> M.
Thanks,
Melody
prev parent reply other threads:[~2022-10-03 19:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:03 [PATCH 0/5] clk: qcom: Add clocks for the QDU1000 and QRU1000 SoCs Melody Olvera
2022-10-01 3:03 ` [PATCH 1/5] dt-bindings: clock: Add QDU1000 and QRU1000 GCC clock bindings Melody Olvera
2022-10-01 9:24 ` Krzysztof Kozlowski
2022-10-03 18:47 ` Melody Olvera
2022-10-03 21:32 ` Dmitry Baryshkov
2022-10-11 22:11 ` Melody Olvera
2022-10-04 6:55 ` Krzysztof Kozlowski
2022-10-03 13:24 ` Rob Herring
2022-10-03 13:24 ` Rob Herring
2022-10-01 3:04 ` [PATCH 2/5] dt-bindings: clock: Add RPMHCC bindings for QDU1000 and QRU1000 Melody Olvera
2022-10-01 6:59 ` Dmitry Baryshkov
2022-10-03 18:55 ` Melody Olvera
2022-10-01 3:04 ` [PATCH 3/5] clk: qcom: Add QDU1000 and QRU1000 GCC support Melody Olvera
2022-10-01 7:10 ` Dmitry Baryshkov
2022-10-03 19:37 ` Melody Olvera
2022-10-01 3:04 ` [PATCH 4/5] clk: qcom: Add support for QDU1000 and QRU1000 RPMh clocks Melody Olvera
2022-10-01 7:03 ` Dmitry Baryshkov
2022-10-03 19:40 ` Melody Olvera
2022-10-01 3:04 ` [PATCH 5/5] dt-bindings: clock: Introduce pdc bindings for QDU1000 and QRU1000 Melody Olvera
2022-10-01 6:58 ` Dmitry Baryshkov
2022-10-03 19:46 ` Melody Olvera
2022-10-01 9:22 ` Marc Zyngier
2022-10-03 19:47 ` Melody Olvera [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=55d28ebc-e061-7b5e-99f9-f34f2b0e9af8@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.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=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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).