From: Christoph Stoidner <C.Stoidner@phytec.de>
To: PHYTEC Upstream <upstream@lists.phytec.de>,
Wadim Egorov <W.Egorov@phytec.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Yannic Moog <Y.Moog@phytec.de>,
"uboot-imx@nxp.com" <uboot-imx@nxp.com>,
"trini@konsulko.com" <trini@konsulko.com>,
"festevam@gmail.com" <festevam@gmail.com>,
Andrej Picej <andrej.picej@norik.com>,
"sbabic@denx.de" <sbabic@denx.de>,
Primoz Fiser <primoz.fiser@norik.com>,
"m.othacehe@gmail.com" <m.othacehe@gmail.com>
Subject: Re: [PATCH v2 2/3] board: phytec: imx93: Add eeprom-based hardware introspection
Date: Thu, 14 Nov 2024 15:21:27 +0000 [thread overview]
Message-ID: <3d979ca81678c2aede5014351d203be30941725f.camel@phytec.de> (raw)
In-Reply-To: <ede9c065-04d3-47de-9d68-0b2c4659a834@phytec.de>
On Mi, 2024-11-13 at 20:42 +0100, Wadim Egorov wrote:
>
>
> Am 13.11.24 um 17:00 schrieb Christoph Stoidner:
> > The phyCORE-i.MX 93 is available in various variants. Relevant
> > variant
> > options for the spl/u-boot are:
> > - with or without HS400 support for the eMMC
> > - with 1GB ram chip, or 2GB ram chip
> >
> > The phyCORE's eeprom contains all information about the existing
> > variant
> > options. Add evaluation of the eeprom data to the spl/u-boot to
> > enable/disable HS400 and to select the appropriate ram
> > configuration at
> > startup.
> >
> > Signed-off-by: Christoph Stoidner <c.stoidner@phytec.de>
> > ---
> > Cc: Mathieu Othacehe <m.othacehe@gmail.com>
> > Cc: Christoph Stoidner <c.stoidner@phytec.de>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>
> > Cc: Tom Rini <trini@konsulko.com>
> > Cc: Yannic Moog <y.moog@phytec.de>
> > Cc: Primoz Fiser <primoz.fiser@norik.com>
> > Cc: Andrej Picej <andrej.picej@norik.com>
> > Cc: Wadim Egorov <w.egorov@phytec.de>
> > ---
> > Changes in v2:
> > - encapsulate handling of feature flag VOLTAGE into own function
> > - move definition of enum phytec_imx93_ddr_eeprom_code into header
> > file
> >
> > arch/arm/dts/imx93-phyboard-segin-u-boot.dtsi | 19 +++
> > arch/arm/mach-imx/imx9/Kconfig | 2 +
> > arch/arm/mach-imx/imx9/soc.c | 2 +-
> > board/phytec/common/Kconfig | 8 ++
> > board/phytec/common/Makefile | 1 +
> > board/phytec/common/imx93_som_detection.c | 111
> > ++++++++++++++++++
> > board/phytec/common/imx93_som_detection.h | 51 ++++++++
> > board/phytec/phycore_imx93/Kconfig | 28 +++++
> > board/phytec/phycore_imx93/MAINTAINERS | 5 +-
> > board/phytec/phycore_imx93/phycore-imx93.c | 51 ++++++++
> > board/phytec/phycore_imx93/spl.c | 48 ++++++++
> > 11 files changed, 324 insertions(+), 2 deletions(-)
> > create mode 100644 board/phytec/common/imx93_som_detection.c
> > create mode 100644 board/phytec/common/imx93_som_detection.h
> >
> > diff --git a/arch/arm/dts/imx93-phyboard-segin-u-boot.dtsi
> > b/arch/arm/dts/imx93-phyboard-segin-u-boot.dtsi
> > index 6897c91f4d..25c778bb07 100644
> > --- a/arch/arm/dts/imx93-phyboard-segin-u-boot.dtsi
> > +++ b/arch/arm/dts/imx93-phyboard-segin-u-boot.dtsi
> > @@ -305,4 +305,23 @@
> > };
> > };
> > };
> > +
> > + eeprom@50 {
> > + bootph-pre-ram;
> > + bootph-some-ram;
> > + compatible = "atmel,24c32";
> > + reg = <0x50>;
> > + pagesize = <32>;
> > + vcc-supply = <&buck4>;
> > + };
> > +
> > + eepromid@58 {
>
> Please use a generic node name,
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-
> devicetree-basics.html#generic-names-recommendation
>
> With that fixed,
In fact, it is better to remove this eepromid node.
We want to avoid the use of the id-page anyway, because that ID page
is a very chip-specific feature that complicates finding a compatible
replacement eeprom-chip, whenever needed.
So I will just remove the eepromid node in a v3.
>
> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
next prev parent reply other threads:[~2024-11-14 15:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 16:00 [PATCH v2 0/3] Add support for all variants of the phyCORE-i.MX93 SOM Christoph Stoidner
2024-11-13 16:00 ` [PATCH v2 1/3] board: phytec: phycore-imx93: Add 2GB LPDDR4X RAM timings Christoph Stoidner
2024-11-13 16:00 ` [PATCH v2 2/3] board: phytec: imx93: Add eeprom-based hardware introspection Christoph Stoidner
2024-11-13 18:29 ` Fabio Estevam
2024-11-13 19:50 ` Wadim Egorov
2024-11-14 11:31 ` Christoph Stoidner
2024-11-13 19:42 ` Wadim Egorov
2024-11-14 15:21 ` Christoph Stoidner [this message]
2024-11-14 6:30 ` Yannic Moog
2024-11-19 16:45 ` Christoph Stoidner
2024-11-20 8:08 ` Yannic Moog
2024-11-14 8:37 ` Primoz Fiser
2024-11-19 9:35 ` Christoph Stoidner
2024-11-13 16:00 ` [PATCH v2 3/3] board: phytec: imx93: Add phyCORE-i.MX 93 support for all SOM variants Christoph Stoidner
2024-11-13 19:17 ` Wadim Egorov
2024-11-14 6:37 ` Yannic Moog
2024-11-14 11:48 ` Christoph Stoidner
2024-11-14 13:27 ` Yannic Moog
2024-11-14 13:46 ` Wadim Egorov
2024-11-19 9:44 ` Christoph Stoidner
2024-11-14 8:39 ` Primoz Fiser
2024-11-19 9:32 ` Christoph Stoidner
2024-11-13 19:47 ` [Upstream] [PATCH v2 0/3] Add support for all variants of the phyCORE-i.MX93 SOM Wadim Egorov
2024-11-14 12:08 ` Christoph Stoidner
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=3d979ca81678c2aede5014351d203be30941725f.camel@phytec.de \
--to=c.stoidner@phytec.de \
--cc=W.Egorov@phytec.de \
--cc=Y.Moog@phytec.de \
--cc=andrej.picej@norik.com \
--cc=festevam@gmail.com \
--cc=m.othacehe@gmail.com \
--cc=primoz.fiser@norik.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=upstream@lists.phytec.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