public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 02/13] arm: imx: Remove unused CONFIG_xxx_TAG support
Date: Thu, 4 Feb 2021 08:26:52 -0500	[thread overview]
Message-ID: <20210204132652.GY10169@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5CR_iaWHzfbz2uaEywMgq2zdxjTP1BRw5Soc-a-UbBSUA@mail.gmail.com>

On Thu, Feb 04, 2021 at 06:56:47AM -0300, Fabio Estevam wrote:
> Hi Tom,
> 
> [Adding Bryan]
> 
> On Thu, Feb 4, 2021 at 12:49 AM Tom Rini <trini@konsulko.com> wrote:
> 
> > CONFIG_SERIAL_TAG is only used to configure the ATAG serial record.  It
> > does nothing else.  On i.MX8* this is already being discarded.  On i.MX7
> > we see things like:
> >             warp7          : all -144 rodata +32 text -176
> >                u-boot: add: 0/-2, grow: 0/-2 bytes: 0/-160 (-160)
> >                  function                                   old     new   delta
> >                  params                                       4       -      -4
> >                  get_board_serial                            20       -     -20
> >                  board_late_init                             96      56     -40
> >                  boot_prep_linux                            156      60     -96
> 
> But then it will remove the support of reading serial number via fuses
> which was added by:
> 
> commit 852cc548b3fdf6d5b46e2a96f876d14608ccdcf4
> Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Date:   Mon Mar 26 15:27:34 2018 +0100
> 
>     warp7: Set u-boot serial# based on OTP value
> 
>     u-boot has a standard "serial#" environment variable that is suitable
>     for storing the iSerial number we will supply via the USB device
>     descriptor. serial# is automatically picked up by the disk subsystem in
>     u-boot - thus providing a handy unique identifier in /dev/disk/by-id as
>     detailed below.
> 
>     Storing the hardware serial identifier in serial# means we can change the
>     serial# if we want before USB enumeration - thus making iSerial automatic
>     via OTP but overridable if necessary.
> 
>     This patch reads the defined OTP fuse and sets environment variable
>     "serial#" to the value read.
> 
>     With this patch in place the USB mass storage device will appear in
>     /dev/disk/by-id with a unique name based on the OTP value. For example
> 
>     /dev/disk/by-id/usb-Linux_UMS_disk_0_WaRP7-0xf42400d3000001d4-0:0
> 
>     Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>     Cc: Fabio Estevam <fabio.estevam@nxp.com>
>     Cc: Rui Miguel Silva <rui.silva@linaro.org>
>     Cc: Ryan Harkin <ryan.harkin@linaro.org>
>     Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>

I did miss that one.  I'm not sure if that's abusing a symbol or clever
use of the symbol.  I will have to v2 this one then.

> > Currently, yes.  Historically ever?  Or even if so, you're OK just removing all
> > of that code as well?  Thanks.
> 
> mx5 and mx6 used to boot board files in the past (NXP kernel 2.6.35
> for mx5 or 3.0.x for mx6).
> 
> Such kernels are not even maintained by the NXP, so we should not
> worry about booting non-DT with i.MX.

So you're OK with removing ATAGs support from i.MX5/6 from mainline?
But there's the unresolved question of the best way to populate
"serial#".  Yes?  Thanks.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210204/2371e635/attachment.sig>

  reply	other threads:[~2021-02-04 13:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  2:24 [PATCH 01/13] arm: nanopi2: Remove unused code Tom Rini
2021-02-04  2:24 ` [PATCH 02/13] arm: imx: Remove unused CONFIG_xxx_TAG support Tom Rini
2021-02-04  3:02   ` Fabio Estevam
2021-02-04  3:49     ` Tom Rini
2021-02-04  9:56       ` Fabio Estevam
2021-02-04 13:26         ` Tom Rini [this message]
2021-02-04 16:08           ` Tom Rini
2021-02-04 16:44             ` Tom Rini
2021-02-04 19:20               ` Fabio Estevam
2021-02-04 16:10           ` Fabio Estevam
2021-02-04 16:33             ` Tom Rini
2021-02-04  2:24 ` [PATCH 03/13] arm: layerscape: Disable ATAG support on some platforms Tom Rini
2021-02-04  2:24 ` [PATCH 04/13] bcmstb: Disable ATAGs support Tom Rini
2021-02-04  2:24 ` [PATCH 05/13] arm: puma_rk3399: " Tom Rini
2021-02-04  2:24 ` [PATCH 06/13] arm: goni: Disable CONFIG_REVISION_TAG Tom Rini
2021-02-14 22:33   ` Jaehoon Chung
2021-02-04  2:24 ` [PATCH 07/13] arm: aspeed: Disable ATAGs support Tom Rini
2021-02-09  6:55   ` ChiaWei Wang
2021-02-04  2:24 ` [PATCH 08/13] arm: mediatek: " Tom Rini
2021-02-04  2:24 ` [PATCH 09/13] arm: mvebu: Disable ATAGs support on some platforms Tom Rini
2021-02-04  8:44   ` Stefan Roese
2021-02-04  2:24 ` [PATCH 10/13] arm: rcar2/3: Disable ATAGs support Tom Rini
2021-02-04  2:24 ` [PATCH 11/13] arm: s32v234: " Tom Rini
2021-02-04  2:24 ` [PATCH 12/13] arm: socfpga: arria5_secu1: " Tom Rini
2021-02-04  7:56   ` Holger Brunck
2021-02-04  2:24 ` [PATCH 13/13] arm: stm32: " Tom Rini
2021-02-08 16:34   ` Patrick DELAUNAY
2021-02-10 17:51     ` Tom Rini
2021-02-08 17:25 ` [PATCH 01/13] arm: nanopi2: Remove unused code Stefan Bosch
2021-04-10 17:14 ` Stefan Bosch
2021-04-10 17:15   ` 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=20210204132652.GY10169@bill-the-cat \
    --to=trini@konsulko.com \
    --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