From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Soeren Moch <smoch@web.de>, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] board: tbs2910: Convert to DM_SERIAL
Date: Mon, 14 Mar 2022 14:28:29 -0400 [thread overview]
Message-ID: <20220314182829.GK9986@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ2pNFDqkS1tC0jgQ=vfpUebT=g+z87fZXeSVWKhHid6RQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Mon, Mar 14, 2022 at 12:24:36PM -0600, Simon Glass wrote:
> Hi Soeren,
>
> On Mon, 14 Mar 2022 at 02:26, Soeren Moch <smoch@web.de> wrote:
> >
> > ... to get rid of the build warning.
> > Unfortunately we still need the board specific serial pin init code.
> > Otherwise the first boot messages over the serial console are lost.
> >
> > Signed-off-by: Soeren Moch <smoch@web.de>
> > ---
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: Tom Rini <trini@konsulko.com>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: u-boot@lists.denx.de
> >
> > The whole purpose of DM is somewhat defeated when we still need board
> > specific initializations. Any ideas how we can get all boot messages
> > without board specific inits? 'u-boot,dm-pre-reloc;' in the uart device
> > tree node did not help.
>
> You can put that in your serial driver, perhaps? Or in the initial SoC
> init code?
>
> Another recent way (in -next) is to use events to monitor the
> EVT_DM_PRE_PROBE event for the serial driver.
It's just the same thing every single imx platform is doing.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-14 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 8:26 [PATCH 1/2] board: tbs2910: Enable Link Time Optimizations in defconfig Soeren Moch
2022-03-14 8:26 ` [PATCH 2/2] board: tbs2910: Convert to DM_SERIAL Soeren Moch
2022-03-14 18:24 ` Simon Glass
2022-03-14 18:28 ` Tom Rini [this message]
2022-03-14 19:22 ` Soeren Moch
2022-03-14 19:34 ` Tom Rini
2022-03-14 19:37 ` Simon Glass
2022-03-14 21:51 ` Sören Moch
2022-03-14 22:20 ` Simon Glass
2022-03-14 22:38 ` Tom Rini
2022-03-14 22:46 ` Simon Glass
2022-03-14 23:16 ` Fabio Estevam
2022-03-15 20:56 ` Soeren Moch
2022-03-19 11:34 ` Soeren Moch
2022-03-14 18:14 ` [PATCH 1/2] board: tbs2910: Enable Link Time Optimizations in defconfig Tom Rini
2022-03-14 18:24 ` Simon Glass
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=20220314182829.GK9986@bill-the-cat \
--to=trini@konsulko.com \
--cc=festevam@gmail.com \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=smoch@web.de \
--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