From: "Neil Armstrong" <neil.armstrong@linaro.org>
To: trini@konsulko.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de
Subject: [GIT PULL] Please pull u-boot-amlogic-20230131
Date: Wed, 22 Mar 2023 11:46:42 +0100 [thread overview]
Message-ID: <1f1304e3-9f03-0420-c9d0-d36338f413d0@linaro.org> (raw)
Hi Tom,
A single change to enable the odroid-go-ultra PMIC regulator at boot.
The CI job is at https://source.denx.de/u-boot/custodians/u-boot-amlogic/pipelines/15691
Thanks,
Neil
The following changes since commit 88e08fc5f6e508eac46cd1dfb0379b11ae032c0a:
Prepare v2023.04-rc4 (2023-03-13 20:52:48 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-amlogic.git tags/u-boot-amlogic-20230322
for you to fetch changes up to de58694f0d5431627d7389f50a6b2034a682ba24:
ARM: meson: odroid-go-ultra: setup PMIC regulators are board init (2023-03-14 09:03:16 +0100)
----------------------------------------------------------------
- odroid-go-ultra: setup PMIC regulators at board init
----------------------------------------------------------------
Neil Armstrong (1):
ARM: meson: odroid-go-ultra: setup PMIC regulators are board init
.../arm/dts/meson-g12b-odroid-go-ultra-u-boot.dtsi | 8 ++++++++
board/amlogic/odroid-go-ultra/MAINTAINERS | 7 +++++++
board/amlogic/odroid-go-ultra/Makefile | 5 +++++
board/amlogic/odroid-go-ultra/odroid-go-ultra.c | 22 ++++++++++++++++++++++
configs/odroid-go-ultra_defconfig | 4 ++--
5 files changed, 44 insertions(+), 2 deletions(-)
create mode 100644 board/amlogic/odroid-go-ultra/MAINTAINERS
create mode 100644 board/amlogic/odroid-go-ultra/Makefile
create mode 100644 board/amlogic/odroid-go-ultra/odroid-go-ultra.c
next reply other threads:[~2023-03-22 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 10:46 Neil Armstrong [this message]
2023-03-22 13:27 ` [GIT PULL] Please pull u-boot-amlogic-20230131 Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2023-01-31 8:48 Neil Armstrong
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=1f1304e3-9f03-0420-c9d0-d36338f413d0@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).