From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Odelu Kukatla <okukatla@codeaurora.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: interconnect: split SC8280XP to own schema
Date: Mon, 26 Dec 2022 13:08:09 -0600 [thread overview]
Message-ID: <167208168673.62952.8370130996583092568.robh@kernel.org> (raw)
In-Reply-To: <20221223132040.80858-2-krzysztof.kozlowski@linaro.org>
On Fri, 23 Dec 2022 14:20:39 +0100, Krzysztof Kozlowski wrote:
> SC8280XP comes with interconnects without IO address space, so split it
> from common file for easier maintenancen and to fix warnings like:
>
> sc8280xp-lenovo-thinkpad-x13s.dtb: interconnect-mc-virt: 'reg' is a required property
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/interconnect/qcom,rpmh.yaml | 12 -----
> .../interconnect/qcom,sc8280xp-rpmh.yaml | 49 +++++++++++++++++++
> 2 files changed, 49 insertions(+), 12 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sc8280xp-rpmh.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-12-26 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 13:20 [PATCH 1/3] dt-bindings: interconnect: split SC7280 to own schema Krzysztof Kozlowski
2022-12-23 13:20 ` [PATCH 2/3] dt-bindings: interconnect: split SC8280XP " Krzysztof Kozlowski
2022-12-26 19:08 ` Rob Herring [this message]
2022-12-23 13:20 ` [PATCH 3/3] dt-bindings: interconnect: split SM8450 " Krzysztof Kozlowski
2022-12-26 19:07 ` [PATCH 1/3] dt-bindings: interconnect: split SC7280 " Rob Herring
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=167208168673.62952.8370130996583092568.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=okukatla@codeaurora.org \
--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