From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: devicetree@vger.kernel.org, Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 4/4] dt-bindings: leds: Add 'cm3605' to 'linux,default-trigger'
Date: Mon, 5 Dec 2022 16:07:09 -0600 [thread overview]
Message-ID: <20221205220709.GA2713165-robh@kernel.org> (raw)
In-Reply-To: <20221204061555.1355453-5-dmitry.baryshkov@linaro.org>
On Sun, Dec 04, 2022 at 08:15:55AM +0200, Dmitry Baryshkov wrote:
> Add 'cm3605' to possible values for 'linux,default-trigger'. This allows
> one to specify Capella CM3605 proximity sensor as the LED trigger.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> Documentation/devicetree/bindings/leds/common.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
> index f5c57a580078..4ffb1cdf6845 100644
> --- a/Documentation/devicetree/bindings/leds/common.yaml
> +++ b/Documentation/devicetree/bindings/leds/common.yaml
> @@ -101,6 +101,7 @@ properties:
> # LED is triggered by SD/MMC activity
> - pattern: "^mmc[0-9]+$"
> - pattern: "^cpu[0-9]*$"
> + - const: cm3605
No. This would never scale to the 1000s of devices we have.
Maybe 'trigger-sources' does what you need.
Rob
prev parent reply other threads:[~2022-12-05 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 6:15 [PATCH v2 0/4] dt-bindings: add missing subdevices to qcom-pm8xxx schema Dmitry Baryshkov
2022-12-04 6:15 ` [PATCH v2 1/4] dt-bindings: input: qcom,pm8921-keypad: convert to YAML format Dmitry Baryshkov
2022-12-05 1:45 ` kernel test robot
2022-12-05 22:04 ` Rob Herring
2022-12-06 3:20 ` Dmitry Baryshkov
2022-12-07 17:07 ` Rob Herring
2022-12-07 18:36 ` Dmitry Baryshkov
2022-12-07 19:32 ` Dmitry Torokhov
2022-12-04 6:15 ` [PATCH v2 2/4] dt-bindings: mfd: qcom-pm8xxx: add missing child nodes Dmitry Baryshkov
2022-12-04 14:40 ` Jonathan Cameron
2022-12-04 6:15 ` [PATCH v2 3/4] dt-bindings: iio: adc: qcom,pm8018-adc: allow specifying MPP channels Dmitry Baryshkov
2022-12-04 15:37 ` Jonathan Cameron
2022-12-04 15:43 ` Dmitry Baryshkov
2022-12-04 6:15 ` [PATCH v2 4/4] dt-bindings: leds: Add 'cm3605' to 'linux,default-trigger' Dmitry Baryshkov
2022-12-05 22:07 ` Rob Herring [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=20221205220709.GA2713165-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).