All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shengyu Qu <wiagn233@outlook.com>
To: lee@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, wens@csie.org,
	lgirdwood@gmail.com, broonie@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Shengyu Qu <wiagn233@outlook.com>
Subject: [PATCH v1 0/4] Add X-Powers AXP15060 PMIC support
Date: Fri,  7 Apr 2023 21:57:13 +0800	[thread overview]
Message-ID: <TY3P286MB2611A814E580C96DC6F187B798969@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM> (raw)

This patch series adds support for the X-Powers AXP15060 PMIC, which is
a general purpose PMIC seen on different boards with different SOC.
This series were tested on Starfive Visionfive 2 board.

On this board, IRQ line from PMIC isn't connected so PEK function is
completely unable to use, so IRQ existence detection is added to patch 2
to avoid initialization failure.

Besides, its GPIO/LDO control logic is quite different from other chips
and is not easy to add support for it basing on existing axp20x GPIO
driver, so I didn't add support for it in this series. Maybe others
could do this.

Shengyu Qu (4):
  dt-bindings: mfd: x-powers,axp152: Document the AXP15060 variant
  mfd: axp20x: Add support for AXP15060 PMIC
  regulator: axp20x: Add AXP15060 support
  regulator: axp20x: Set DCDC frequency only when property exists

 .../bindings/mfd/x-powers,axp152.yaml         |   3 +-
 drivers/mfd/axp20x-i2c.c                      |   2 +
 drivers/mfd/axp20x.c                          |  90 +++++++
 drivers/regulator/axp20x-regulator.c          | 237 +++++++++++++++++-
 include/linux/mfd/axp20x.h                    |  85 +++++++
 5 files changed, 404 insertions(+), 13 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-04-07 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 13:57 Shengyu Qu [this message]
2023-04-07 14:18 [PATCH v1 0/4] Add X-Powers AXP15060 PMIC support Shengyu Qu

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=TY3P286MB2611A814E580C96DC6F187B798969@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM \
    --to=wiagn233@outlook.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.