From: Wadim Egorov <w.egorov@phytec.de>
To: Yannic Moog <Y.Moog@phytec.de>,
Christoph Stoidner <C.Stoidner@phytec.de>
Cc: "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>,
PHYTEC Upstream <upstream@lists.phytec.de>,
Primoz Fiser <primoz.fiser@norik.com>,
"m.othacehe@gmail.com" <m.othacehe@gmail.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH v2 3/3] board: phytec: imx93: Add phyCORE-i.MX 93 support for all SOM variants
Date: Thu, 14 Nov 2024 14:46:52 +0100 [thread overview]
Message-ID: <fa2b44ee-a717-4b98-ab08-c77c17255f77@phytec.de> (raw)
In-Reply-To: <c44edecde5ba3d006baaa0c58a45f1f6c5476260.camel@phytec.de>
>>>> --- a/board/phytec/phycore_imx93/MAINTAINERS
>>>> +++ b/board/phytec/phycore_imx93/MAINTAINERS
>>>> @@ -9,5 +9,5 @@ F: arch/arm/dts/imx93-phyboard-segin-u-
>>>> boot.dtsi
>>>> F: board/phytec/phycore_imx93/
>>>> F: board/phytec/common/imx93_som_detection.c
>>>> F: board/phytec/common/imx93_som_detection.h
>>>> -F: configs/imx93-phyboard-segin_defconfig
>>>> +F: configs/imx93-phycore_defconfig
>>>
>>> How will you handle this when/if you have another board?
>>
>> That imx93-phycore_defconfig has no more dependency to the carrier
>> board.
>
> Not true,
> CONFIG_DEFAULT_DEVICE_TREE="imx93-phyboard-segin"
> It has a dependency to a board. That is why I am asking.
This approach has served us well for a while.
Most of our u-boot "boards" are designed from a SoM perspective. Also,
customers typically use the initial carrier board as a reference, often
following its interface configurations. So in most cases we are good to go.
I'm not sure why you want to bring this up again.
next prev parent reply other threads:[~2024-11-14 13:47 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
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 [this message]
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=fa2b44ee-a717-4b98-ab08-c77c17255f77@phytec.de \
--to=w.egorov@phytec.de \
--cc=C.Stoidner@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