From: Lee Jones <lee@kernel.org>
To: Matthias Fend <matthias.fend@emfend.at>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pavel Machek <pavel@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
bsp-development.geo@leica-geosystems.com,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 0/2] Support for Texas Instruments TPS6131X flash LED driver
Date: Tue, 13 May 2025 11:40:09 +0100 [thread overview]
Message-ID: <20250513104009.GJ2936510@google.com> (raw)
In-Reply-To: <20250509-leds-tps6131x-v4-0-2c9563f5b67c@emfend.at>
On Fri, 09 May 2025, Matthias Fend wrote:
> The TPS61310/TPS61311 is a flash LED driver with I2C interface. Its power
> stage is capable of supplying a maximum total current of roughly 1500mA.
> The TPS6131x provides three constant-current sinks, capable of sinking up
> to 2 × 400mA (LED1 and LED3) and 800mA (LED2) in flash mode. In torch mode
> each sink (LED1, LED2, LED3) supports currents up to 175m
>
> Signed-off-by: Matthias Fend <matthias.fend@emfend.at>
> ---
> Changes in v4:
> - Added/removed/adjusted comments
> - Use defines for register defaults
> - Updated source format
> - Check for error in torch refresh timer
> - Return error from tps6131x_parse_node()
> - Link to v3: https://lore.kernel.org/r/20250423-leds-tps6131x-v3-0-ca67d346a4ea@emfend.at
>
> Changes in v3:
> - Add comment for locking
> - Drop handling based on CONFIG_V4L2_FLASH_LED_CLASS
> - Stop if getting reset GPIO fails
> - Optimize locks
> - Fix type of num_channels (u32 -> int)
> - Convert a remaining return sequence to dev_err_probe
> - Link to v2: https://lore.kernel.org/r/20250318-leds-tps6131x-v2-0-bc09c7a50b2e@emfend.at
>
> Changes in v2:
> - Bindings: Extend device description
> - Bindings: Drop unused address/size cells
> - Bindings: Use fallback compatible
> - Bindings: Corrected minimum current for 50mA steps
> - Bindings: Drop node label
> - Fix name of REGISTER4 INDC shift define
> - Save device instead i2c_client in private data
> - Add comment for mutex
> - Use macro to convert from uA to mA
> - Use defines to describe initial register values
> - Add safety delay during reset sequence
> - Use fixed value enum to set the mode
> - Renamed some local variables
> - Re-sorted local variables
> - Replaced ifdefs for V4L2_FLASH_LED_CLASS
> - Improved some error messages
> - Link to v1: https://lore.kernel.org/r/20250228-leds-tps6131x-v1-0-d1071d90f9ea@emfend.at
>
> ---
> Matthias Fend (2):
> dt-bindings: leds: add Texas Instruments TPS6131x flash LED driver
> leds: tps6131x: add support for Texas Instruments TPS6131X flash LED driver
>
> .../devicetree/bindings/leds/ti,tps61310.yaml | 120 +++
> MAINTAINERS | 7 +
> drivers/leds/flash/Kconfig | 11 +
> drivers/leds/flash/Makefile | 1 +
> drivers/leds/flash/leds-tps6131x.c | 815 +++++++++++++++++++++
> 5 files changed, 954 insertions(+)
I get errors on apply:
WARNING: Message contains suspicious unicode control characters!
Subject: [PATCH v4 2/2] leds: tps6131x: add support for Texas Instruments TPS6131X flash LED driver
Line: + * Register contents after a power on/reset. These values cannot be changed.
-----------------------------------------------------------------^
Char: ZERO WIDTH SPACE (0x200b)
If you are sure about this, rerun with the right flag to allow.
FWIW, I also saw these in your mails:
> The values <200b><200b>are fixed because they are written directly to a register.
> In V1, I used an enum without values <200b><200b>and mapped it to the register value in
> a function. I was asked to omit this mapping and use the enum directly.
Never seen this before. Not sure what's going on.
Please fix and resubmit.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-05-13 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 10:13 Matthias Fend
2025-05-09 10:13 ` [PATCH v4 1/2] dt-bindings: leds: add Texas Instruments TPS6131x " Matthias Fend
2025-05-09 10:13 ` [PATCH v4 2/2] leds: tps6131x: add support for Texas Instruments TPS6131X " Matthias Fend
2025-05-13 10:40 ` Lee Jones [this message]
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=20250513104009.GJ2936510@google.com \
--to=lee@kernel.org \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matthias.fend@emfend.at \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@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®