From: Daniel Thompson <daniel@riscstar.com>
To: maudspierings@gocontroll.com
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>,
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,
MaudSpieringsmaudspierings@gocontroll.com
Subject: Re: [PATCH v2 2/4] backlight: add max25014atg backlight
Date: Fri, 22 Aug 2025 08:20:50 +0100 [thread overview]
Message-ID: <aKgaUtcNoOsga6l7@aspen.lan> (raw)
In-Reply-To: <20250819-max25014-v2-2-5fd7aeb141ea@gocontroll.com>
On Tue, Aug 19, 2025 at 12:59:00PM +0200, 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 intgrated boost controller.
>
> Signed-off-by: Maud Spierings maudspierings@gocontroll.com
Looking good but still a few small comments (below).
> diff --git a/drivers/video/backlight/max25014.c b/drivers/video/backlight/max25014.c
> new file mode 100644
> index 0000000000000000000000000000000000000000..fe5e0615cf6d151868b56ebb9544b175b09dfcee
> --- /dev/null
> +++ b/drivers/video/backlight/max25014.c
> @@ -0,0 +1,395 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Backlight driver for Maxim MAX25014
> + *
> + * Copyright (C) 2025 GOcontroll B.V.
> + * Author: Maud Spierings <maudspierings@gocontroll.com>
> + */
> +
> +#include <linux/backlight.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/i2c.h>
> +#include <linux/regmap.h>
> +#include <linux/slab.h>
> +
> +#define MAX25014_ISET_DEFAULT_100 11
> +#define MAX_BRIGHTNESS (100)
> +#define MIN_BRIGHTNESS (0)
> +#define TON_MAX (130720) /* @153Hz */
> +#define TON_STEP (1307) /* @153Hz */
> +#define TON_MIN (0)
> +
> +#define MAX25014_DEV_ID (0x00)
> +#define MAX25014_REV_ID (0x01)
> +#define MAX25014_ISET (0x02)
> +#define MAX25014_IMODE (0x03)
> +#define MAX25014_TON1H (0x04)
> +#define MAX25014_TON1L (0x05)
> +#define MAX25014_TON2H (0x06)
> +#define MAX25014_TON2L (0x07)
> +#define MAX25014_TON3H (0x08)
> +#define MAX25014_TON3L (0x09)
> +#define MAX25014_TON4H (0x0A)
> +#define MAX25014_TON4L (0x0B)
> +#define MAX25014_TON_1_4_LSB (0x0C)
> +#define MAX25014_SETTING (0x12)
> +#define MAX25014_DISABLE (0x13)
> +#define MAX25014_BSTMON (0x14)
> +#define MAX25014_IOUT1 (0x15)
> +#define MAX25014_IOUT2 (0x16)
> +#define MAX25014_IOUT3 (0x17)
> +#define MAX25014_IOUT4 (0x18)
> +#define MAX25014_OPEN (0x1B)
> +#define MAX25014_SHORT_GND (0x1C)
> +#define MAX25014_SHORT_LED (0x1D)
> +#define MAX25014_MASK (0x1E)
> +#define MAX25014_DIAG (0x1F)
There is no need to put raw numbers in brackets.
> +
> +#define MAX25014_IMODE_HDIM BIT(2)
> +#define MAX25014_ISET_ENABLE BIT(5)
> +#define MAX25014_ISET_PSEN BIT(4)
> +#define MAX25014_DIAG_HW_RST BIT(2)
> +#define MAX25014_SETTING_FPWM GENMASK(6, 4)
> +
> +struct max25014 {
> + struct i2c_client *client;
> + struct backlight_device *bl;
> + struct regmap *regmap;
> + struct max25014_platform_data *pdata;
This appears to be unused.
> + struct gpio_desc *enable;
> + struct regulator *vin; /* regulator for boost converter Vin rail */
> + uint32_t initial_brightness;
It is important to keep the initial_brightness for the lifetime of the
driver?
> + uint32_t iset;
> + uint8_t strings_mask;
> +};
> +
Daniel.
next prev parent reply other threads:[~2025-08-22 7:20 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
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 [this message]
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=aKgaUtcNoOsga6l7@aspen.lan \
--to=daniel@riscstar.com \
--cc=MaudSpieringsmaudspierings@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=maudspierings@gocontroll.com \
--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;
as well as URLs for NNTP newsgroup(s).