From: Maud Spierings <maudspierings@gocontroll.com>
To: Rob Herring <robh@kernel.org>
Cc: Lee Jones <lee@kernel.org>, Daniel Thompson <danielt@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>,
Pavel Machek <pavel@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Helge Deller <deller@gmx.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fbdev@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: backlight: Add max25014 bindings
Date: Wed, 20 Aug 2025 07:19:46 +0200 [thread overview]
Message-ID: <a1115bc7-225f-438c-8ae9-c616f42747d7@gocontroll.com> (raw)
In-Reply-To: <20250819195008.GA1218175-robh@kernel.org>
On 8/19/25 21:50, Rob Herring wrote:
> On Tue, Aug 19, 2025 at 12:58:59PM +0200, Maud Spierings wrote:
>> The Maxim MAX25014 is a 4-channel automotive grade backlight driver IC
>> with intgrated boost controller.
>>
>> Signed-off-by: Maud Spierings <maudspierings@gocontroll.com>
>> ---
>> .../bindings/leds/backlight/maxim,max25014.yaml | 79 ++++++++++++++++++++++
>> MAINTAINERS | 5 ++
>> 2 files changed, 84 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/leds/backlight/maxim,max25014.yaml b/Documentation/devicetree/bindings/leds/backlight/maxim,max25014.yaml
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..30b591152fa31d5e43243cac44c72028b05b5f8a
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/leds/backlight/maxim,max25014.yaml
>> @@ -0,0 +1,79 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/leds/backlight/maxim,max25014.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Maxim max25014 backlight controller
>> +
>> +maintainers:
>> + - Maud Spierings <maudspierings@gocontroll.com>
>> +
>> +allOf:
>> + - $ref: common.yaml#
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - maxim,max25014
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + enable-gpios:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + power-supply:
>> + description: Regulator which controls the boost converter input rail.
>> +
>> + pwms:
>> + maxItems: 1
>> +
>> + maxim,iset:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>
> maximum: 15
done
>> + default: 11
>> + description:
>> + Value of the ISET register field (0-15).
>
> Perhaps a little on what this controls?
done, for now, it controls the current scale of the backlight, higher
number = more current. But I will put it in the description in v3
>> +
>> + maxim,strings:
>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>> + description:
>> + A 4-bit bitfield that describes which led strings to turn on.
>> + minItems: 4
>> + maxItems: 4
>
> items:
> maximum: 1
>
> But why not just an 8-bit value 0x0-0xF?
That is possible too, the logic is inverted in the actual chip, a bit
set means the string is turned off, but that can be solved with a
bitwise not. This just felt like a natural way to read/edit it, an 8-bit
value you have to first translate the bits into a hex value which isn't
very clear about what it is actually doing.
Is it possible to to 0b0111 notation in a devicetree? That would make it
better at least.
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - maxim,strings
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/gpio/gpio.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + backlight: backlight@6f {
>
> Drop unused labels.
oops dropped
>> + reg = <0x6f>;
>> + compatible = "maxim,max25014";
>
> compatible is always first.
Messed that up in the dtsos too, fixed everywhere in v3
>> + default-brightness = <50>;
>> + enable-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
>> + interrupt-parent = <&gpio1>;
>> + interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_backlight>;
>
> Generally we don't put pinctrl properties in examples as they are always
> allowed.
dropped
>> + power-supply = <®_backlight>;
>> + pwms = <&pwm1>;
>> + maxim,iset = <7>;
>> + maxim,strings = <1 1 1 1>;
>> + };
>> + };
>> +
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e81d5f9fbd16cc384356804390d65652bbb9e3f6..11c73d2e37fac22aea852152746236c1472f41b8 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14972,6 +14972,11 @@ F: Documentation/userspace-api/media/drivers/max2175.rst
>> F: drivers/media/i2c/max2175*
>> F: include/uapi/linux/max2175.h
>>
>> +MAX25014 BACKLIGHT DRIVER
>> +M: Maud Spierings <maudspierings@gocontroll.com>
>> +S: Maintained
>> +F: Documentation/devicetree/bindings/leds/backlight/maxim,max25014.yaml
>> +
>> MAX31335 RTC DRIVER
>> M: Antoniu Miclaus <antoniu.miclaus@analog.com>
>> L: linux-rtc@vger.kernel.org
>>
>> --
>> 2.50.1
>>
Thanks for your review!
Kind regards,
Maud
next prev parent reply other threads:[~2025-08-20 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 10:58 [PATCH v2 0/4] backlight: add new max25014 backlight driver Maud Spierings via B4 Relay
2025-08-19 10:58 ` [PATCH v2 1/4] dt-bindings: backlight: Add max25014 bindings Maud Spierings via B4 Relay
2025-08-19 12:28 ` Fabio Estevam
2025-08-19 12:35 ` Maud Spierings
2025-08-19 12:32 ` Rob Herring (Arm)
2025-08-19 19:50 ` Rob Herring
2025-08-20 5:19 ` Maud Spierings [this message]
2025-08-22 7:26 ` Daniel Thompson
2025-08-22 7:35 ` Maud Spierings
2025-08-19 10:59 ` [PATCH v2 2/4] backlight: add max25014atg backlight Maud Spierings via B4 Relay
2025-08-22 7:20 ` Daniel Thompson
2025-08-22 7:31 ` Maud Spierings
2025-08-19 10:59 ` [PATCH v2 3/4] arm64: dts: freescale: moduline-display-av101hdt-a10: add backlight Maud Spierings via B4 Relay
2025-08-19 10:59 ` [PATCH v2 4/4] arm64: dts: freescale: moduline-display-av123z7m-n17: " Maud Spierings via B4 Relay
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=a1115bc7-225f-438c-8ae9-c616f42747d7@gocontroll.com \
--to=maudspierings@gocontroll.com \
--cc=conor+dt@kernel.org \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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