From: Vinod Koul <vkoul@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: qcom: sc8180x-pmics: add missing gpio-ranges
Date: Thu, 20 Jul 2023 20:54:08 +0530 [thread overview]
Message-ID: <ZLlRmKnp3IYaQySJ@matsya> (raw)
In-Reply-To: <20230720083500.73554-2-krzysztof.kozlowski@linaro.org>
On 20-07-23, 10:34, Krzysztof Kozlowski wrote:
> The GPIO children of PMICs should use gpio-ranges:
>
> sc8180x-primus.dtb: pmic@0: gpio@c000: 'gpio-ranges' is a required property
Reviewed-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2023-07-20 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 8:34 [PATCH 1/4] arm64: dts: qcom: sc8180x-pmics: add missing qcom,spmi-gpio fallbacks Krzysztof Kozlowski
2023-07-20 8:34 ` [PATCH 2/4] arm64: dts: qcom: sc8180x-pmics: add missing gpio-ranges Krzysztof Kozlowski
2023-07-20 8:37 ` Konrad Dybcio
2023-07-20 15:24 ` Vinod Koul [this message]
2023-07-20 8:34 ` [PATCH 3/4] arm64: dts: qcom: sc8180x-pmics: align SPMI PMIC Power-on node name with dtschema Krzysztof Kozlowski
2023-07-20 8:38 ` Konrad Dybcio
2023-07-20 15:24 ` Vinod Koul
2023-07-20 8:35 ` [PATCH 4/4] arm64: dts: qcom: sc8180x-pmics: align LPG " Krzysztof Kozlowski
2023-07-20 8:38 ` Konrad Dybcio
2023-07-20 15:24 ` Vinod Koul
2023-07-20 8:36 ` [PATCH 1/4] arm64: dts: qcom: sc8180x-pmics: add missing qcom,spmi-gpio fallbacks Konrad Dybcio
2023-07-20 15:23 ` Vinod Koul
2023-07-22 5:17 ` (subset) " 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=ZLlRmKnp3IYaQySJ@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=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).