From: Roman Vivchar <rva333@protonmail.com>
To: Rillian Grant <rillian.grant@gmail.com>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ruslan Koreev <koreev.r@gmail.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] leds: flash: Add support for the TI LM3643 dual LED flash driver
Date: Wed, 11 Nov 2026 19:29:31 +0000 [thread overview]
Message-ID: <2f081600-58a2-47b3-808f-b578bb07d41f@protonmail.com> (raw)
Hi Rillian,
On 10/11/26 22:09, Rillian Grant wrote:
> The LM3643 is an I2C dual LED flash driver. Its two high-side current
> sources share a synchronous boost converter and each supports torch and
> flash modes with programmable current and flash timeout alongside fault
> reporting.
>
> It also supports connecting both sources together to supply one LED with
> current up to the boost converter's 1.5A maximum. In that case the current
> will be split between each source symmetrically and the sources will be
> enabled and disabled at the same time.
>
> As strobing is toggled chip-wide the driver returns -EBUSY when a sibling
> LED is active.
>
> Flash timeouts do not have a constant step. The driver advertises the most
> granular step and rounds down to the nearest supported value.
>
> Register behavior was taken from the datasheet (SNVS967A).
>
> Co-developed-by: Ruslan Koreev <koreev.r@gmail.com>
> Signed-off-by: Ruslan Koreev <koreev.r@gmail.com>
> Signed-off-by: Rillian Grant <rillian.grant@gmail.com>
I have tested this series on a Realme C3 phone, which uses Orient Chip
OCP81373 IC (register-compatible clone of the LM3643, except the device
ID is 0x3A instead of 0x00). I had to modify the driver to support
multiple chips, since there's at least one more clone IC (Awinic
AW3643). After applying modifications, flash and torch modes were
confirmed to work correctly. Once this series is merged, I will send a
small series to add support for the OCP81373.
Tested-by: Roman Vivchar <rva333@protonmail.com>
Best regards,
Roman
next reply other threads:[~2026-11-11 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 19:29 Roman Vivchar [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-11 19:09 [PATCH v3 0/4] leds: flash: " Rillian Grant
2026-10-11 19:09 ` [PATCH v3 2/4] leds: flash: Add support for the TI " Rillian Grant
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=2f081600-58a2-47b3-808f-b578bb07d41f@protonmail.com \
--to=rva333@protonmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=koreev.r@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rillian.grant@gmail.com \
--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®