From: Peng Fan <peng.fan@oss.nxp.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: [GIT PULL] please pull mmc-next-2026-02-26
Date: Thu, 26 Feb 2026 19:48:40 +0800 [thread overview]
Message-ID: <aaAzGKCyhtvxOX80@nxa18884-linux.ap.freescale.net> (raw)
Hi Tom,
Please pull mmc-next-2026-02-26
----------------------------------------
Add MediaTek MT6359P regulator driver
Add MediaTek MT6357 regulator driver
Add MediaTek PMIC Wrapper driver
Enable pmic and regulator for mt8365 evk
Minor cleanup
----------------------------------------
CI: https://source.denx.de/u-boot/custodians/u-boot-mmc/-/pipelines/29376
Thanks
Peng
The following changes since commit 8fd76675efbe7af785ccc1ba1ac8b9f7e10f6715:
board: Correct usage of fdtfile=CONFIG_DEFAULT_FDT_FILE (2026-02-23 15:30:34 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-mmc.git tags/mmc-next-2026-02-26
for you to fetch changes up to b3d16267b5095746888927478a0973fa810a0826:
mmc: mtk-sd: add mediatek,mt8189-mmc compatible (2026-02-26 11:15:44 +0800)
----------------------------------------------------------------
Bo-Chen Chen (1):
power: regulator: mt6359: add driver for MT6359P
David Lechner (2):
configs: mt8365_evk_defconfig: enable PMIC and regulators
mmc: mtk-sd: add mediatek,mt8189-mmc compatible
Heinrich Schuchardt (1):
power: regulator: Kconfig: add SPL_DM_REGULATOR_FAN53555
Julien Masson (2):
power: regulator: add MediaTek MT6357 driver
power: pmic: mtk-pwrap: add MediaTek PMIC Wrapper driver
Marek Vasut (1):
cmd: mmc: Drop trailing space in Name: before newline
MAINTAINERS | 3 +
cmd/mmc.c | 4 +-
configs/mt8365_evk_defconfig | 6 +
drivers/mmc/mtk-sd.c | 11 +
drivers/power/pmic/Kconfig | 8 +
drivers/power/pmic/Makefile | 1 +
drivers/power/pmic/mtk-pwrap.c | 896 +++++++++++++++++++++++++++++
drivers/power/regulator/Kconfig | 26 +
drivers/power/regulator/Makefile | 2 +
drivers/power/regulator/mt6357_regulator.c | 512 +++++++++++++++++
drivers/power/regulator/mt6359_regulator.c | 711 +++++++++++++++++++++++
include/power/mt6357.h | 159 +++++
include/power/mt6359.h | 225 ++++++++
include/power/mt6359p.h | 230 ++++++++
14 files changed, 2792 insertions(+), 2 deletions(-)
create mode 100644 drivers/power/pmic/mtk-pwrap.c
create mode 100644 drivers/power/regulator/mt6357_regulator.c
create mode 100644 drivers/power/regulator/mt6359_regulator.c
create mode 100644 include/power/mt6357.h
create mode 100644 include/power/mt6359.h
create mode 100644 include/power/mt6359p.h
next reply other threads:[~2026-02-26 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 11:48 Peng Fan [this message]
2026-02-26 18:30 ` [GIT PULL] please pull mmc-next-2026-02-26 Tom Rini
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=aaAzGKCyhtvxOX80@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.nxp.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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