public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yannic Moog <Y.Moog@phytec.de>
To: "primoz.fiser@norik.com" <primoz.fiser@norik.com>,
	"m.othacehe@gmail.com" <m.othacehe@gmail.com>
Cc: "peng.fan@nxp.com" <peng.fan@nxp.com>,
	"trini@konsulko.com" <trini@konsulko.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
	"sbabic@denx.de" <sbabic@denx.de>,
	"uboot-imx@nxp.com" <uboot-imx@nxp.com>,
	"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: [Upstream] [PATCH] Add Phytec i.MX93 support
Date: Fri, 19 Jan 2024 06:49:22 +0000	[thread overview]
Message-ID: <010a36a7d295152e5f78650904ec2df17ff36618.camel@phytec.de> (raw)
In-Reply-To: <87ttnavr5u.fsf@gmail.com>

Hi Mathieu

On Thu, 2024-01-18 at 12:04 +0100, Mathieu Othacehe wrote:
> 
> Hi,
> 
> Thanks for the review!
> 
> > s/imx93_phycore/phycore_imx93
> > 
> > To fit into existing PHYTEC boards already in tree.
> 
> I deliberately picked that order so that it is aligned with most imx
> boards already supported by u-boot.
> 
> The supported imx93 boards follow that pattern:
> 
> - imx93_var_som
> - imx93_evk
> 
> So it felt natural to have:
> 
> - imx93_phycore
> 
> Plus the kernel device-trees are also following that order:
> 
> - imx93-phycore-xxx
> 
> On the other hand, it is true that the existing phycore boards use the
> phytec_* pattern:
> 
> - phycore_am335x_r2
> - phycore_imx8mm
> - phycore_imx8mp
> - phycore_rk3288/
> 
> So that will be confusing no matter the option that we choose.
> 
> I will come up with a v2 fixing your other remarks, but I think that
> this should be addressed beforehand.

We decided not to alter the names after the fact, but for imx8 product family we noticed the same
problem.
Anyway, to avoid this whole issue, please name the defconfig and the device tree to imx93-phyboard-
segin. This avoids the challenge of naming configs when you have multiple carrier boards supported
for the same SoM. Further, for the board/phytec/ dir, only phytec board code is in there, so you may
stick to the phytec naming convention (i.e. phycore_imx93 as Primoz suggested). This also allows to
reuse the phycore code (see imx8mm-phygate-tauri-l for reference).

Yannic
> 
> Thanks,
> 
> Mathieu
> _______________________________________________
> upstream mailing list
> upstream@lists.phytec.de
> http://lists.phytec.de/cgi-bin/mailman/listinfo/upstream


  reply	other threads:[~2024-01-19  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  7:52 [PATCH] Add Phytec i.MX93 support Mathieu Othacehe
2024-01-17 10:36 ` Fabio Estevam
2024-01-18 10:47 ` Primoz Fiser
2024-01-18 11:04   ` Mathieu Othacehe
2024-01-19  6:49     ` Yannic Moog [this message]
2024-01-19  7:21 ` Yannic Moog
2024-01-24 13:30   ` Mathieu Othacehe
2024-01-24 13:46     ` Yannic Moog

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=010a36a7d295152e5f78650904ec2df17ff36618.camel@phytec.de \
    --to=y.moog@phytec.de \
    --cc=festevam@gmail.com \
    --cc=m.othacehe@gmail.com \
    --cc=peng.fan@nxp.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