public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <festevam@denx.de>,
	u-boot@lists.denx.de, Peng Fan <peng.fan@nxp.com>,
	Stefano Babic <sbabic@denx.de>
Subject: Re: [PATCH 1/4] ARM: imx: imx8m: Introduce and use UART_BASE_ADDR(n)
Date: Mon, 25 Apr 2022 09:05:49 -0400	[thread overview]
Message-ID: <20220425130549.GD6921@bill-the-cat> (raw)
In-Reply-To: <dab391ba-c7a8-a0ee-83f9-56f76f1be99d@denx.de>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Mon, Apr 25, 2022 at 03:02:29PM +0200, Marek Vasut wrote:
> On 4/25/22 14:46, Fabio Estevam wrote:
> > Hi Marek,
> > 
> > On 24/04/2022 18:44, Marek Vasut wrote:
> > > Introduce helper macro UART_BASE_ADDR(n), which returns Nth UART base
> > > address. Convert all board configurations to this new macro. This is the
> > > first step toward switching CONFIG_MXC_UART_BASE to Kconfig. This is a
> > > clean up, no functional change.
> > 
> > As DM_SERIAL is mandatory now, we should get rid of CONFIG_MXC_UART_BASE.
> > 
> > I would prefer a patch that removes CONFIG_MXC_UART_BASE instead.
> 
> DM is mandatory in SPL too ? I doubt it.

It is strongly encouraged, but not mandatory.  It is not used on I guess
imx27/31/5, but is for all of the imx8 families.  So
CONFIG_MXC_UART_BASE still needs to be moved out of board.h files (and
perhaps out of CONFIG namespace since it's not configurable, it's part
of the SoC) and perhaps the path for imx8* is to drop the references
since it's all DM?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-04-25 13:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 21:44 [PATCH 1/4] ARM: imx: imx8m: Introduce and use UART_BASE_ADDR(n) Marek Vasut
2022-04-24 21:44 ` [PATCH 2/4] ARM: imx: imx27: " Marek Vasut
2022-05-20 13:41   ` sbabic
2022-04-24 21:44 ` [PATCH 3/4] ARM: imx: imx31: " Marek Vasut
2022-05-20 13:40   ` sbabic
2022-04-24 21:44 ` [PATCH 4/4] ARM: imx: imx5: " Marek Vasut
2022-05-20  7:30   ` Stefano Babic
2022-05-20  7:45     ` Marek Vasut
2022-05-20  8:11       ` Stefano Babic
2022-05-20  8:18         ` Stefano Babic
2022-04-25 12:46 ` [PATCH 1/4] ARM: imx: imx8m: " Fabio Estevam
2022-04-25 13:02   ` Marek Vasut
2022-04-25 13:05     ` Tom Rini [this message]
2022-04-25 13:13       ` Marek Vasut
2022-04-25 13:39         ` Tom Rini
2022-04-25 13:15       ` Fabio Estevam
2022-05-20 13:42 ` sbabic

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=20220425130549.GD6921@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=festevam@denx.de \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.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