All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Jagan Teki <jagan@amarulasolutions.com>, u-boot@lists.denx.de
Cc: Sunil Mohan Adapa <sunil@medhas.org>,
	Arnaud Ferraris <arnaud.ferraris@collabora.com>,
	Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: [PATCH 0/2] sunxi: A64: enable AXP driver support
Date: Wed,  7 May 2025 01:53:23 +0100	[thread overview]
Message-ID: <20250507005325.15612-1-andre.przywara@arm.com> (raw)

Hi,

this series enables the build of the AXP driver in U-Boot proper for all
boards using the Allwinner A64 SoC. So far some static PMIC rail setup
was done by TF-A, but this was rather static (enabling too many) and
increases the code size of the rather limited BL31 build.

Do this for the A64 only first, since this uses RSB consistently, while
the H6 boards are undergoing a transition to use I2C.

Please have a look and test!

Cheers,
Andre

Andre Przywara (2):
  sunxi: A64: enable DRIVEVBUS support for respective boards
  sunxi: A64: enable AXP drivers

 arch/arm/Kconfig                     | 1 +
 arch/arm/mach-sunxi/Kconfig          | 3 +++
 configs/a64-olinuxino-emmc_defconfig | 1 +
 configs/a64-olinuxino_defconfig      | 1 +
 configs/amarula_a64_relic_defconfig  | 1 +
 configs/bananapi_m64_defconfig       | 1 +
 configs/orangepi_win_defconfig       | 1 +
 configs/pinetab_defconfig            | 1 +
 8 files changed, 10 insertions(+)

-- 
2.46.3


             reply	other threads:[~2025-05-07  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  0:53 Andre Przywara [this message]
2025-05-07  0:53 ` [PATCH 1/2] sunxi: A64: enable DRIVEVBUS support for respective boards Andre Przywara
2025-05-07  0:53 ` [PATCH 2/2] sunxi: A64: enable AXP drivers Andre Przywara
2025-08-11 15:53 ` [PATCH 0/2] sunxi: A64: enable AXP driver support Jernej Škrabec
2025-08-28  8:39 ` Peter Robinson

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=20250507005325.15612-1-andre.przywara@arm.com \
    --to=andre.przywara@arm.com \
    --cc=arnaud.ferraris@collabora.com \
    --cc=jagan@amarulasolutions.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=sunil@medhas.org \
    --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 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.