From: Tom Rini <trini@konsulko.com>
To: Paul Kocialkowski <paulk@sys-base.io>
Cc: u-boot@lists.denx.de,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Wolfgang Wallner <wolfgang.wallner@br-automation.com>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
Govindaraji Sivanantham <Govindaraji.Sivanantham@in.bosch.com>,
Hiremath Gireesh <Gireesh.Hiremath@in.bosch.com>,
Heiko Schocher <hs@denx.de>, Felix Brack <fb@ltec.ch>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Yegor Yefremov <yegorslists@googlemail.com>
Subject: Re: [PATCH 1/3] omap: Use spl_soc_init instead of spl_board_init
Date: Mon, 29 Jul 2024 14:47:52 -0600 [thread overview]
Message-ID: <20240729204752.GR989285@bill-the-cat> (raw)
In-Reply-To: <20240729204439.429900-1-paulk@sys-base.io>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
On Mon, Jul 29, 2024 at 10:44:37PM +0200, Paul Kocialkowski wrote:
> Both spl_board_init and spl_soc_init are available as ways to run
> specific code in the SPL's board_init_r. Use the former for init
> code that is specific to the SoC and leave spl_board_init available
> for boards to use.
>
> Signed-off-by: Paul Kocialkowski <paulk@sys-base.io>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-07-29 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 20:44 [PATCH 1/3] omap: Use spl_soc_init instead of spl_board_init Paul Kocialkowski
2024-07-29 20:44 ` [PATCH 2/3] am33xx: Use regular spl_board_init instead of am33xx_spl_board_init Paul Kocialkowski
2024-07-29 20:47 ` Tom Rini
2024-07-29 20:44 ` [PATCH 3/3] omap3: sniper: Convert to device-tree control and DM I2C Paul Kocialkowski
2024-07-29 20:47 ` Tom Rini [this message]
2024-08-07 14:20 ` [PATCH 1/3] omap: Use spl_soc_init instead of spl_board_init 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=20240729204752.GR989285@bill-the-cat \
--to=trini@konsulko.com \
--cc=Gireesh.Hiremath@in.bosch.com \
--cc=Govindaraji.Sivanantham@in.bosch.com \
--cc=enric.balletbo@collabora.com \
--cc=fb@ltec.ch \
--cc=hs@denx.de \
--cc=m.niestroj@grinn-global.com \
--cc=paulk@sys-base.io \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sjoerd.simons@collabora.co.uk \
--cc=u-boot@lists.denx.de \
--cc=wolfgang.wallner@br-automation.com \
--cc=yegorslists@googlemail.com \
/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