From: Melody Olvera <quic_molvera@quicinc.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Robert Marko <robimarko@gmail.com>,
Das Srinagesh <quic_gurus@quicinc.com>
Cc: "open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatible
Date: Fri, 16 Dec 2022 15:22:17 -0800 [thread overview]
Message-ID: <031d6121-c4b0-8db4-f816-fcff1e57f656@quicinc.com> (raw)
In-Reply-To: <20221216231312.22574-1-quic_molvera@quicinc.com>
On 12/16/2022 3:13 PM, Melody Olvera wrote:
> Add compatible for scm driver for QDU1000 and QRU1000 platforms. These
> drivers only require the compatible field, so update the bindings
> accordingly for these platforms.
>
> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> ---
> This patch is separated out from [1] and includes
> changes addressing comments from that patch set.
>
> Changes from v4:
> * rebased on top of [2]
> * removed redundant allOf
>
> Changes from v3:
> * removed unnecessary reset-cells
>
> Changes from v2:
> * Dropped qru compat strings
> * Marked no clocks on qdu/qru scm device
> * Revised rpmhpd constants
> * Updated socinfo driver to new format
>
> [1] https://lore.kernel.org/all/20221026190549.4005703-2-quic_molvera@quicinc.com/
Apologies; meant to note that [2] is https://lore.kernel.org/lkml/20221122092345.44369-2-krzysztof.kozlowski@linaro.org/
> ---
> Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> index 8e6e9ebb343d..9312a0953ea8 100644
> --- a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> +++ b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> @@ -38,6 +38,7 @@ properties:
> - qcom,scm-msm8994
> - qcom,scm-msm8996
> - qcom,scm-msm8998
> + - qcom,scm-qdu1000
> - qcom,scm-sc7180
> - qcom,scm-sc7280
> - qcom,scm-sc8280xp
>
> base-commit: ca39c4daa6f7f770b1329ffb46f1e4a6bcc3f291
> prerequisite-patch-id: d5d17b3d720b358b8478cb1ad87e21a70992f228
> prerequisite-patch-id: 6c92672973fdc1524516942fa21c340e68e7c4fb
next prev parent reply other threads:[~2022-12-16 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 23:13 [PATCH v5] dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatible Melody Olvera
2022-12-16 23:22 ` Melody Olvera [this message]
2022-12-17 10:35 ` Krzysztof Kozlowski
2023-01-11 5:09 ` 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=031d6121-c4b0-8db4-f816-fcff1e57f656@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@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_gurus@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
/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).