Devicetree
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: azkali.limited@gmail.com, Neil Armstrong <neil.armstrong@linaro.org>
Cc: Philippe Simons <simons.philippe@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] regulator: add support for SGMicro SGM3804
Date: Mon, 11 May 2026 09:51:23 +0900	[thread overview]
Message-ID: <agEoC0kdKoOVrjne@sirena.co.uk> (raw)
In-Reply-To: <20260510-sgm3804-v1-0-e5e8799e0aa0@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

On Sun, May 10, 2026 at 11:45:25PM +0700, Alexandre Hamamdjian via B4 Relay wrote:
> This series adds support for the SGMicro SGM3804, an I2C-controlled
> positive/negative output charge-pump regulator. The chip is used to
> generate the AVDD/AVEE rails for display panels and is present on the
> Ayaneo Pocket DS handheld, where it powers the panel and is required
> before any panel driver can light up the display.

There is a separate series from Neil Armstrong (Cced) already in review
for the same part.  Please sort out what to do about this between
yourselves.

> 
> The Ayaneo Pocket DS device tree, posted as a separate series, depends
> on the binding introduced here to describe its panel power supply, so
> this series is a prerequisite for that work and for any subsequent
> panel-related patches targeting the same board.
> 
> Signed-off-by: Alexandre Hamamdjian <azkali.limited@gmail.com>
> ---
> Alexandre Hamamdjian (2):
>       dt-bindings: regulator: add SGMicro SGM3804
>       regulator: sgm3804: add SGMicro SGM3804 charge-pump regulator driver
> 
>  .../bindings/regulator/sgmicro,sgm3804.yaml        |  60 ++++++++
>  MAINTAINERS                                        |   7 +
>  drivers/regulator/Kconfig                          |  11 ++
>  drivers/regulator/Makefile                         |   1 +
>  drivers/regulator/sgm3804-regulator.c              | 164 +++++++++++++++++++++
>  5 files changed, 243 insertions(+)
> ---
> base-commit: e98d21c170b01ddef366f023bbfcf6b31509fa83
> change-id: 20260510-sgm3804-c37a0ae6d7f3
> 
> Best regards,
> --  
> Alexandre Hamamdjian <azkali.limited@gmail.com>
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2026-05-11  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 16:45 [PATCH 0/2] regulator: add support for SGMicro SGM3804 Alexandre Hamamdjian via B4 Relay
2026-05-10 16:45 ` [PATCH 1/2] dt-bindings: regulator: add " Alexandre Hamamdjian via B4 Relay
2026-05-10 17:45   ` Rob Herring (Arm)
2026-05-11  1:22   ` Mark Brown
2026-05-10 16:45 ` [PATCH 2/2] regulator: sgm3804: add SGMicro SGM3804 charge-pump regulator driver Alexandre Hamamdjian via B4 Relay
2026-05-11  0:51 ` Mark Brown [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=agEoC0kdKoOVrjne@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=azkali.limited@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=simons.philippe@gmail.com \
    /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