From: Bjorn Andersson <andersson@kernel.org>
To: krzysztof.kozlowski+dt@linaro.org,
krzysztof.kozlowski@linaro.org, konrad.dybcio@linaro.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, agross@kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/3] arm64: dts: qcom: msm8996-xiaomi-gemini: use preferred enable-gpios for LP5562 LED
Date: Tue, 27 Dec 2022 22:36:45 -0600 [thread overview]
Message-ID: <167220221219.833009.18401531649717521241.b4-ty@kernel.org> (raw)
In-Reply-To: <20221127203240.54955-1-krzysztof.kozlowski@linaro.org>
On Sun, 27 Nov 2022 21:32:38 +0100, Krzysztof Kozlowski wrote:
> The preferred name suffix for properties with single and multiple GPIOs
> is "gpios". Linux GPIO core code supports both. Bindings are going to
> expect the "gpios" one:
>
> qcom/msm8996-xiaomi-gemini.dtb: lp5562@30: 'enable-gpio' does not match any of the regexes: '^led@[0-8]$', '^multi-led@[0-8]$', 'pinctrl-[0-9]+'
>
>
> [...]
Applied, thanks!
[1/3] arm64: dts: qcom: msm8996-xiaomi-gemini: use preferred enable-gpios for LP5562 LED
commit: 4df05b44468cdf5dea7a7aa291eeabd7e639f8ff
[2/3] arm64: dts: qcom: align LED node names with dtschema
(no commit info)
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-12-28 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 20:32 [PATCH v2 1/3] arm64: dts: qcom: msm8996-xiaomi-gemini: use preferred enable-gpios for LP5562 LED Krzysztof Kozlowski
2022-11-27 20:32 ` [PATCH v2 2/3] arm64: dts: qcom: align LED node names with dtschema Krzysztof Kozlowski
2022-11-27 20:32 ` [PATCH v2 3/3] ARM: " Krzysztof Kozlowski
2022-11-28 14:58 ` [PATCH v2 1/3] arm64: dts: qcom: msm8996-xiaomi-gemini: use preferred enable-gpios for LP5562 LED Konrad Dybcio
2022-12-06 18:19 ` (subset) " Bjorn Andersson
2022-12-28 4:36 ` 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=167220221219.833009.18401531649717521241.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=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).