From: Maud Spierings <maudspierings@gocontroll.com>
To: Conor Dooley <conor@kernel.org>
Cc: Lee Jones <lee@kernel.org>, Daniel Thompson <danielt@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>,
Pavel Machek <pavel@kernel.org>, Rob Herring <robh@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>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
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 v5 1/4] dt-bindings: backlight: Add max25014 support
Date: Mon, 10 Nov 2025 08:55:01 +0100 [thread overview]
Message-ID: <88f9ef73-7eb7-4186-a436-9d8bbad52e9d@gocontroll.com> (raw)
In-Reply-To: <20251107-qualified-varsity-78953d06d7c6@spud>
On 11/7/25 19:16, Conor Dooley wrote:
> On Fri, Nov 07, 2025 at 01:49:58PM +0100, Maud Spierings via B4 Relay wrote:
>> From: Maud Spierings <maudspierings@gocontroll.com>
>>
>> The Maxim MAX25014 is a 4-channel automotive grade backlight driver IC
>> with integrated boost controller.
>>
>> Signed-off-by: Maud Spierings <maudspierings@gocontroll.com>
>>
>> ---
>>
>> In the current implementation the control registers for channel 1,
>> control all channels. So only one led subnode with led-sources is
>> supported right now. If at some point the driver functionality is
>> expanded the bindings can be easily extended with it.
>
> I'm sorry if I asked this before and forgot or w/e, but how backwards
> compatible is this? If they control all channels and it gets changed to
> only control channel one, how will a changed kernel understand the
> difference between a new devicetree that only wants to control channel 1
> and an old devicetree that is trying to use channel 1 to control all
> channels?
>
The idea is that an implementation like that will add multiple led@
subnodes without the led-sources property.
So devicetrees controlled by one channel will still have only one led
with multiple sources in the devicetree.
Kind regards,
Maud
>
>> ---
>> .../bindings/leds/backlight/maxim,max25014.yaml | 107 +++++++++++++++++++++
>> MAINTAINERS | 5 +
>> 2 files changed, 112 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 000000000000..e83723224b07
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/leds/backlight/maxim,max25014.yaml
>> @@ -0,0 +1,107 @@
>> +# 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>
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - maxim,max25014
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 0
>> +
>> + 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
>> + default: 11
>> + description:
>> + Value of the ISET field in the ISET register. This controls the current
>> + scale of the outputs, a higher number means more current.
>> +
>> + led@0:
>> + type: object
>> + description: Properties for a string of connected LEDs.
>> + $ref: common.yaml#
>> +
>> + properties:
>> + reg:
>> + const: 0
>> +
>> + led-sources:
>> + allOf:
>> + - minItems: 1
>> + maxItems: 4
>> + items:
>> + minimum: 0
>> + maximum: 3
>> + default: [0, 1, 2, 3]
>> +
>> + default-brightness:
>> + minimum: 0
>> + maximum: 100
>> + default: 50
>> +
>> + required:
>> + - reg
>> +
>> + additionalProperties: false
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/gpio/gpio.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + backlight@6f {
>> + compatible = "maxim,max25014";
>> + reg = <0x6f>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + enable-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
>> + interrupt-parent = <&gpio1>;
>> + interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
>> + power-supply = <®_backlight>;
>> + pwms = <&pwm1>;
>> + maxim,iset = <7>;
>> +
>> + led@0 {
>> + reg = <0>;
>> + led-sources = <0 1 2 3>;
>> + default-brightness = <50>;
>> + };
>> + };
>> + };
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 58c7e3f678d8..606ce086f758 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -15261,6 +15261,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.51.2
>>
>>
next prev parent reply other threads:[~2025-11-10 7:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 12:49 [PATCH v5 0/4] backlight: add new max25014 backlight driver Maud Spierings via B4 Relay
2025-11-07 12:49 ` [PATCH v5 1/4] dt-bindings: backlight: Add max25014 support Maud Spierings via B4 Relay
2025-11-07 15:35 ` [PATCH v5 1/4] dt-bindings: backlight: Add max25014 supporty Frank Li
2025-11-07 17:14 ` Conor Dooley
2025-11-10 7:59 ` Maud Spierings
2025-11-07 18:16 ` [PATCH v5 1/4] dt-bindings: backlight: Add max25014 support Conor Dooley
2025-11-10 7:55 ` Maud Spierings [this message]
2025-11-07 12:49 ` [PATCH v5 2/4] backlight: add max25014atg backlight Maud Spierings via B4 Relay
2025-11-07 15:51 ` [PATCH v5 2/4] backlight: add max25014atg backlighty Frank Li
2025-11-07 16:22 ` Daniel Thompson
2025-11-07 20:42 ` Frank Li
2025-11-10 8:25 ` Maud Spierings
2025-11-07 16:14 ` [PATCH v5 2/4] backlight: add max25014atg backlight Daniel Thompson
2025-11-10 8:40 ` Maud Spierings
2025-11-10 10:01 ` Daniel Thompson
2025-11-10 10:03 ` Maud Spierings
2025-11-10 10:19 ` Daniel Thompson
2025-11-07 12:50 ` [PATCH v5 3/4] arm64: dts: freescale: moduline-display-av101hdt-a10: add backlight Maud Spierings via B4 Relay
2025-11-07 12:50 ` [PATCH v5 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=88f9ef73-7eb7-4186-a436-9d8bbad52e9d@gocontroll.com \
--to=maudspierings@gocontroll.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@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=lgirdwood@gmail.com \
--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
all inboxes | Powered by JetHome®