From: Sander Vanheule <sander@svanheule.net>
To: "Escala, Edelweise" <Edelweise.Escala@analog.com>,
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>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 2/2] leds: ltc3220: Add Support for LTC3220 18 channel LED Driver
Date: Thu, 14 May 2026 21:03:52 +0200 [thread overview]
Message-ID: <a8b222b3304ef00fba1342a831a5c40fb13ba467.camel@svanheule.net> (raw)
In-Reply-To: <DS0PR03MB722878551FEED39276921D1DED062@DS0PR03MB7228.namprd03.prod.outlook.com>
On Wed, 2026-05-13 at 11:25 +0000, Escala, Edelweise wrote:
> > Up to you if you want to clear the device configuration (maybe this causes
> > LED flickering?), but with REGCACHE_FLAT_S, you should be able to maintain
> > the boot state of the device.
>
> For the reset behavior, I'm keeping the current approach (clearing all
> registers on probe) since I haven't observed any flickering, and it ensures a
> known clean state. Let me know if you have concerns with this approach.
It's just that I've found myself forcing register writes to fix a REGCACHE_FLAT
cache at start-up. But if clearing everything is your preference, then I have no
issues with that.
Best,
Sander
prev parent reply other threads:[~2026-05-14 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 4:09 [PATCH v7 0/2] Add Support for LTC3220 18 Channel " Edelweise Escala
2026-05-08 4:09 ` [PATCH v7 1/2] dt-bindings: leds: Add LTC3220 18 channel " Edelweise Escala
2026-05-08 13:57 ` Rob Herring
2026-05-13 11:10 ` Escala, Edelweise
2026-05-08 4:09 ` [PATCH v7 2/2] leds: ltc3220: Add Support for " Edelweise Escala
2026-05-10 9:07 ` Sander Vanheule
2026-05-13 11:25 ` Escala, Edelweise
2026-05-14 19:03 ` Sander Vanheule [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=a8b222b3304ef00fba1342a831a5c40fb13ba467.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=Edelweise.Escala@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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®