| Message ID | 20221204061555.1355453-5-dmitry.baryshkov@linaro.org (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
| Series | dt-bindings: add missing subdevices to qcom-pm8xxx schema | expand |
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
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 led-pattern: description: |
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(+)