From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
Fabian Pfitzner <f.pfitzner@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/3] ARM: i.MX8MP: add imx8mp-frdm board
Date: Fri, 23 Jan 2026 11:11:48 +0100 [thread overview]
Message-ID: <aXNJZPJxO_JoLOdh@pengutronix.de> (raw)
In-Reply-To: <d482031d-a2c1-42d8-aaff-ecce2dacce81@pengutronix.de>
On Fri, Jan 23, 2026 at 10:27:18AM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 1/23/26 10:16, Sascha Hauer wrote:
> >> @Ahmad @Sascha
> >>
> >> Do we have a proper driver for the bbu? In that case we could drop the
> >> whole board.c :-)
> >
> > No we don't have that yet. Would be nice to have, but requires some
> > thinking. I think this would require yet another barebox specific device
> > tree binding which is not a nice thing to have.
>
> Another possibility would be to register it in SoC code as it's mostly
> the same across boards anyway. In that case, boards would only need
> an opt-in/opt-out and optionally a way to register different/additional
> names for the update handlers..
That sounds good. It would even allow us to register the current
bootsource as default handler.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-01-23 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 15:02 [PATCH 0/3] add imx8mp-frdm board support Fabian Pfitzner
2026-01-19 15:02 ` [PATCH 1/3] ARM: i.MX8MP: add imx8mp-frdm board Fabian Pfitzner
2026-01-19 15:24 ` Marco Felsch
2026-01-23 9:16 ` Sascha Hauer
2026-01-23 9:27 ` Ahmad Fatoum
2026-01-23 10:11 ` Sascha Hauer [this message]
2026-01-19 15:02 ` [PATCH 2/3] dts: backport NXP i.MX8MP FRDM board dts Fabian Pfitzner
2026-01-19 15:26 ` Marco Felsch
2026-01-19 15:02 ` [PATCH 3/3] dts: imx8mp-frdm: import downstream changes Fabian Pfitzner
2026-01-19 15:38 ` Marco Felsch
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=aXNJZPJxO_JoLOdh@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pfitzner@pengutronix.de \
--cc=m.felsch@pengutronix.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.