From: Conor Dooley <conor@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: pavel@ucw.cz, lee@kernel.org, thierry.reding@gmail.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, agross@kernel.org, andersson@kernel.org,
luca.weiss@fairphone.com, konrad.dybcio@linaro.org,
u.kleine-koenig@pengutronix.de, quic_subbaram@quicinc.com,
quic_gurus@quicinc.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-pwm@vger.kernel.org,
kernel@quicinc.com,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 2/7] dt-bindings: leds: leds-qcom-lpg: Add support for LPG PPG
Date: Thu, 31 Aug 2023 16:58:26 +0100 [thread overview]
Message-ID: <20230831-dose-eligibly-dee96e1f4dc2@spud> (raw)
In-Reply-To: <20230830180600.1865-5-quic_amelende@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 4159 bytes --]
On Wed, Aug 30, 2023 at 11:05:57AM -0700, Anjelique Melendez wrote:
> Update leds-qcom-lpg binding to support LPG PPG.
>
> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/leds/leds-qcom-lpg.yaml | 89 ++++++++++++++++++-
> 1 file changed, 88 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml b/Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml
> index e6f1999cb22f..067ebe35ca5e 100644
> --- a/Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml
> +++ b/Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml
> @@ -11,7 +11,7 @@ maintainers:
>
> description: >
> The Qualcomm Light Pulse Generator consists of three different hardware blocks;
> - a ramp generator with lookup table, the light pulse generator and a three
> + a ramp generator with lookup table (LUT), the light pulse generator and a three
> channel current sink. These blocks are found in a wide range of Qualcomm PMICs.
>
> properties:
> @@ -63,6 +63,29 @@ properties:
> - description: dtest line to attach
> - description: flags for the attachment
>
> + nvmem:
> + description: >
Why do you have these chomping operators? I can't see any formatting
that'd require them. Unless you're respinning for other reasons, you can
ignore this comment.
Thanks,
Conor.
> + This property is required for PMICs that supports PPG, which is when a
> + PMIC stores LPG per-channel data and pattern LUT in SDAM modules instead
> + of in a LUT peripheral. For PMICs, such as PM8350C, per-channel data
> + and pattern LUT is separated into 2 SDAM modules. In that case, phandles
> + to both SDAM modules need to be specified.
> + minItems: 1
> + maxItems: 2
> +
> + nvmem-names:
> + minItems: 1
> + items:
> + - const: lpg_chan_sdam
> + - const: lut_sdam
> +
> + qcom,pbs:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: >
> + Phandle of the Qualcomm Programmable Boot Sequencer node (PBS).
> + PBS node is used to trigger LPG pattern sequences for PMICs that support
> + single SDAM PPG.
> +
> multi-led:
> type: object
> $ref: leds-class-multicolor.yaml#
> @@ -106,6 +129,39 @@ required:
>
> additionalProperties: false
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,pmi632-lpg
> + then:
> + properties:
> + nvmem:
> + maxItems: 1
> + nvmem-names:
> + maxItems: 1
> + required:
> + - nvmem
> + - nvmem-names
> + - qcom,pbs
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,pm8350c-pwm
> + - qcom,pm8550-pwm
> + then:
> + properties:
> + nvmem:
> + minItems: 2
> + nvmem-names:
> + minItems: 2
> + required:
> + - nvmem
> + - nvmem-names
> +
> examples:
> - |
> #include <dt-bindings/leds/common.h>
> @@ -191,4 +247,35 @@ examples:
> compatible = "qcom,pm8916-pwm";
> #pwm-cells = <2>;
> };
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + led-controller {
> + compatible = "qcom,pmi632-lpg";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + #pwm-cells = <2>;
> + nvmem-names = "lpg_chan_sdam";
> + nvmem = <&pmi632_sdam_7>;
> + qcom,pbs = <&pmi632_pbs_client3>;
> +
> + led@1 {
> + reg = <1>;
> + color = <LED_COLOR_ID_RED>;
> + label = "red";
> + };
> +
> + led@2 {
> + reg = <2>;
> + color = <LED_COLOR_ID_GREEN>;
> + label = "green";
> + };
> +
> + led@3 {
> + reg = <3>;
> + color = <LED_COLOR_ID_BLUE>;
> + label = "blue";
> + };
> + };
> +
> ...
> --
> 2.41.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-31 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 18:05 [PATCH v4 0/7] Add support for LUT PPG Anjelique Melendez
2023-08-30 18:05 ` [PATCH v4 1/7] dt-bindings: soc: qcom: Add qcom,pbs bindings Anjelique Melendez
2023-08-30 18:05 ` [PATCH v4 2/7] dt-bindings: leds: leds-qcom-lpg: Add support for LPG PPG Anjelique Melendez
2023-08-31 15:58 ` Conor Dooley [this message]
2023-08-30 18:05 ` [PATCH v4 3/7] soc: qcom: add QCOM PBS driver Anjelique Melendez
2023-08-30 18:20 ` Konrad Dybcio
2023-08-30 18:05 ` [PATCH v4 4/7] leds: rgb: leds-qcom-lpg: Add support for PPG through single SDAM Anjelique Melendez
2023-08-30 18:34 ` Konrad Dybcio
2023-09-07 19:55 ` Anjelique Melendez
2023-09-07 20:42 ` Konrad Dybcio
2023-09-07 22:01 ` Anjelique Melendez
2023-08-30 18:06 ` [PATCH v4 5/7] leds: rgb: leds-qcom-lpg: Update PMI632 lpg_data to support PPG Anjelique Melendez
2023-08-30 18:34 ` Konrad Dybcio
2023-09-07 19:54 ` Anjelique Melendez
2023-09-07 20:26 ` Konrad Dybcio
2023-09-07 20:31 ` Konrad Dybcio
2023-09-08 0:30 ` Anjelique Melendez
2023-09-08 8:28 ` Konrad Dybcio
2023-09-08 18:58 ` Anjelique Melendez
2023-08-30 18:06 ` [PATCH v4 6/7] leds: rgb: leds-qcom-lpg: Include support for dedicated LUT SDAM PPG Scheme Anjelique Melendez
2023-08-30 18:06 ` [PATCH v4 7/7] leds: rgb: Update PM8350C lpg_data to support two-nvmem " Anjelique Melendez
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=20230831-dose-eligibly-dee96e1f4dc2@spud \
--to=conor@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=pavel@ucw.cz \
--cc=quic_amelende@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).