From: Dylan Van Assche <me@dylanvanassche.be>
To: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, amartinz@shiftphones.com,
Dylan Van Assche <me@dylanvanassche.be>
Subject: [PATCH v2 1/3] dt-bindings: leds: qcom,spmi-flash-led: add PMI8998
Date: Thu, 18 May 2023 08:13:26 +0200 [thread overview]
Message-ID: <20230518061328.146847-2-me@dylanvanassche.be> (raw)
In-Reply-To: <20230518061328.146847-1-me@dylanvanassche.be>
Document compatible for PMI8998 Torch and Flash LED controller.
Signed-off-by: Dylan Van Assche <me@dylanvanassche.be>
---
Documentation/devicetree/bindings/leds/qcom,spmi-flash-led.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/leds/qcom,spmi-flash-led.yaml b/Documentation/devicetree/bindings/leds/qcom,spmi-flash-led.yaml
index ffacf703d9f9..4b42b6950c88 100644
--- a/Documentation/devicetree/bindings/leds/qcom,spmi-flash-led.yaml
+++ b/Documentation/devicetree/bindings/leds/qcom,spmi-flash-led.yaml
@@ -26,6 +26,7 @@ properties:
- qcom,pm8150c-flash-led
- qcom,pm8150l-flash-led
- qcom,pm8350c-flash-led
+ - qcom,pmi8998-flash-led
- const: qcom,spmi-flash-led
reg:
--
2.40.1
next prev parent reply other threads:[~2023-05-18 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 6:13 [PATCH v2 0/3] arm64: dts: qcom: pmi8998: add and enable flash LED controller Dylan Van Assche
2023-05-18 6:13 ` Dylan Van Assche [this message]
2023-05-18 7:19 ` [PATCH v2 1/3] dt-bindings: leds: qcom,spmi-flash-led: add PMI8998 Krzysztof Kozlowski
2023-05-18 6:13 ` [PATCH v2 2/3] arm64: dts: qcom: pmi8998: add flash LED controller Dylan Van Assche
2023-05-18 7:19 ` Krzysztof Kozlowski
2023-05-18 6:13 ` [PATCH v2 3/3] arm64: dts: qcom: sdm845-shift-axolotl: enable flash LEDs Dylan Van Assche
2023-05-18 10:44 ` Konrad Dybcio
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=20230518061328.146847-2-me@dylanvanassche.be \
--to=me@dylanvanassche.be \
--cc=agross@kernel.org \
--cc=amartinz@shiftphones.com \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).