On 31/10/2023 07:59, Yuxi (Yuxi) Wang wrote: > 1. Stray blank line in your commit. 2. Send patches with proper threading (which is by default by all tools!). Lack of threading makes it difficult to apply entire set or use b4 diff. > Document mps mp3326 LED driver devicetree bindings. > > Signed-off-by: Yuxi Wang <Yuxi.Wang@xxxxxxxxxxxxxxxxxxx> > --- > .../devicetree/bindings/leds/leds-mp3326.yaml | 184 ++++++++++++++++++ > 1 file changed, 184 insertions(+) > create mode 100644 Documentation/devicetree/bindings/leds/leds-mp3326.yaml > > diff --git a/Documentation/devicetree/bindings/leds/leds-mp3326.yaml b/Documentation/devicetree/bindings/leds/leds-mp3326.yaml > new file mode 100644 > index 000000000000..df03c21ae53a > --- /dev/null > +++ b/Documentation/devicetree/bindings/leds/leds-mp3326.yaml Filename like compatible. > @@ -0,0 +1,184 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/leds-mp3326.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: LED driver for MP3326 from Monolithic Power Systems "driver" as Linux driver? If so, drop. MP3326 could be a WLED driver, so "driver" as hardware term, but it does not make sense in "driver for MPS3326" > + > +maintainers: > + - Yuxi Wang <Yuxi.Wang@xxxxxxxxxxxxxxxxxxx> > + > +description: | > + Monolithic Power Systems MP3326 LED Drivers > + > + For more product information please see the link below: > + https://www.monolithicpower.com/en/products/mp3326.html > + > +properties: > + compatible: > + - const: mps,mp3326 It does not look like you tested the bindings, at least after quick look. Please run `make dt_binding_check` (see Documentation/devicetree/bindings/writing-schema.rst for instructions). Maybe you need to update your dtschema and yamllint. I'll stop reviewing. No point to review untested code. Best regards, Krzysztof
