From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Fenglin Wu <quic_fenglinw@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Pavel Machek <pavel@ucw.cz>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
collinsd@codeaurora.org, subbaram@codeaurora.org
Subject: Re: [PATCH v2 2/2] dt-bindings: add bindings for QCOM flash LED
Date: Fri, 30 Sep 2022 14:33:08 -0500 [thread overview]
Message-ID: <20220930193308.GA741352-robh@kernel.org> (raw)
In-Reply-To: <5445adda-80e6-41d0-9786-c26d253631c9@linaro.org>
On Thu, Sep 29, 2022 at 02:40:05PM +0200, Krzysztof Kozlowski wrote:
> On 29/09/2022 14:15, Fenglin Wu wrote:
> > Add binding document for flash LED module inside Qualcomm Technologies,
> > Inc. PMICs.
> >
> > Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com>
>
> Thank you for your patch. There is something to discuss/improve.
>
> > + reg:
> > + description: address offset of the flash LED controller
> > + maxItems: 1
> > +
> > +patternProperties:
> > + "^led[0-3]$":
>
> In such case: ^led-[0-9]$"
>
> > + type: object
> > + $ref: common.yaml#
> > + unevaluatedProperties: false
> > + description: |
> > + Represents the physical LED components which are connected to the
> > + flash LED channels' output.
> > +
> > + properties:
> > + led-sources:
This is for when the power source and LED connection are programmable.
IOW, when 'reg' is not enough to describe the configuration. If you only
have LED channels 1-4 with a fixed connection to LED pins/output 1-4,
then use 'reg'.
> > + description: |
> > + The HW indices of the flash LED channels that connect to the
> > + physical LED
> > + allOf:
> > + - minItems: 1
> > + maxItems: 2
> > + items:
> > + enum: [1, 2, 3, 4]
> > +
> > + led-max-microamp:
> > + description: |
> > + The maximum current value when LED is not operating in flash mode (i.e. torch mode)
> > + Valid values when an LED is connected to one flash LED channel:
> > + 5000 - 500000, step by 5000
> > + Valid values when an LED is connected to two flash LED channels:
> > + 10000 - 1000000, step by 10000
> > + minimum: 5000
> > + maximum: 1000000
anyOf:
- minimum: 5000
maximum: 500000
multipleOf: 5000
- minimum: 10000
maximum: 1000000
multipleOf: 10000
Drop any description that's captured by the constraints.
> > +
> > + flash-max-microamp:
> > + description: |
> > + The maximum current value when LED is operating in flash mode.
> > + Valid values when an LED is connected to one flash LED channel:
> > + 12500 - 1500000, step by 12500
> > + Valid values when an LED is connected to two flash LED channels:
> > + 25000 - 2000000, step by 12500
> > + minimum: 12500
> > + maximum: 2000000
> > +
> > + flash-max-timeout-us:
> > + description: |
> > + The maximum timeout value when LED is operating in flash mode.
> > + Valid values: 10000 - 1280000, step by 10000
> > + minimum: 10000
> > + maximum: 1280000
Similar comment for these 2.
> > +
> > + required:
> > + - led-sources
> > + - led-max-microamp
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/leds/common.h>
> > + spmi_bus {
>
> No underscores in node names, so just "bus"
SPMI is something else though...
next prev parent reply other threads:[~2022-09-30 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220929121544.1064279-1-quic_fenglinw@quicinc.com>
2022-09-29 12:15 ` [PATCH v2 2/2] dt-bindings: add bindings for QCOM flash LED Fenglin Wu
2022-09-29 12:40 ` Krzysztof Kozlowski
2022-09-30 1:10 ` Fenglin Wu
2022-09-30 19:33 ` Rob Herring [this message]
2022-10-03 12:49 ` Krzysztof Kozlowski
2022-10-10 9:47 ` Fenglin Wu
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=20220930193308.GA741352-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.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-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=quic_fenglinw@quicinc.com \
--cc=subbaram@codeaurora.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).