Devicetree
 help / color / mirror / Atom feed
From: Josua Mayer <josua.m@t-online.de>
To: Andreas Kemnade <andreas@kemnade.info>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 2/2] regulator: Add TPS65185 driver
Date: Sat, 27 Dec 2025 17:33:56 +0100	[thread overview]
Message-ID: <9ab5bb73-6237-4348-a62a-a61af4d4704e@t-online.de> (raw)
In-Reply-To: <20251227-tps65185-submit-v2-2-1882024b8f33@kemnade.info>

Am 27.12.25 um 11:20 schrieb Andreas Kemnade:

> Add a driver for the TPS65185 regulator. Implement handling of the various
> gpio pins. Because the PWRUP (=enable) pin functionality can be achieved
> by just using two bits instead, just ensure that it is set to a stable
> value.
> Implement the pair of symmetric LDOs as a single regulator because they
> share a single voltage set register. As the VCOM regulator sits behind that
> machinery, just define that one as a supply.
> For simplicity, just add the temperature sensor (depending on external NTC)
> directly.
>
> There is a mechanism to measure some kick-back voltage during a defined EPD
> operation, to calibrate the VCOM voltage setting and store that
> non-volatile in the chip to be the power up default setup. That is not
> implemented yet in the driver, but that also means that there is a
> non-factory default value in these registers after power-up.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> ---
>   drivers/regulator/Kconfig    |  11 ++
>   drivers/regulator/Makefile   |   1 +
>   drivers/regulator/tps65185.c | 454 +++++++++++++++++++++++++++++++++++++++++++
>   3 files changed, 466 insertions(+)

Tested on Kobo Aura (N514).

Tested-by: Josua Mayer <josua.mayer@jm0.eu>


      reply	other threads:[~2025-12-27 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27 10:20 [PATCH v2 0/2] regulator: Add TPS65185 Andreas Kemnade
2025-12-27 10:20 ` [PATCH v2 1/2] dt-bindings: regulator: Document TI TPS65185 Andreas Kemnade
2025-12-30  9:08   ` Krzysztof Kozlowski
2025-12-30  9:49     ` Andreas Kemnade
2025-12-30 10:40       ` Krzysztof Kozlowski
2025-12-27 10:20 ` [PATCH v2 2/2] regulator: Add TPS65185 driver Andreas Kemnade
2025-12-27 16:33   ` Josua Mayer [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=9ab5bb73-6237-4348-a62a-a61af4d4704e@t-online.de \
    --to=josua.m@t-online.de \
    --cc=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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