Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/freescale-imx: fix i.MX8MMini configuration
Date: Mon, 30 Mar 2020 09:49:05 +0200	[thread overview]
Message-ID: <20200330074905.GA5954@p1g2> (raw)
In-Reply-To: <20200330082524.58b82f57@windsurf.home>

Hi Thomas,

On Mon, Mar 30, 2020 at 08:25:24AM +0200, Thomas Petazzoni wrote:
> Hello Gary,
> 
> On Thu, 26 Mar 2020 17:49:42 +0100
> Gary Bisson <gary.bisson@boundarydevices.com> wrote:
> 
> > - Just like i.MX8MQ, i.MX8MMini is using Hantro VPU.
> > - Platform name wasn't set for i.MX8Mini
> >   -> now differencing IMX8MQ and IMX8MM for VPU package  
> > 
> > Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> 
> So, I've applied, but I have one comment/concern below.
> 
> > diff --git a/package/freescale-imx/Config.in b/package/freescale-imx/Config.in
> > index f42bb11a3c..0a5be9c75a 100644
> > --- a/package/freescale-imx/Config.in
> > +++ b/package/freescale-imx/Config.in
> > @@ -66,7 +66,8 @@ config BR2_PACKAGE_FREESCALE_IMX_PLATFORM
> >  	default "IMX6UL" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX6UL
> >  	default "IMX7" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX7
> >  	default "IMX8" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8
> > -	default "IMX8" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8M
> > +	default "IMX8MQ" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8M
> > +	default "IMX8MM" if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8MM
> 
> I am not sure about the usefulness of this
> BR2_PACKAGE_FREESCALE_IMX_PLATFORM string, especially for i.MX8
> platforms. Indeed, this string is only used by the imx-lib and imx-vpu
> packages, and it seems that they are not relevant for i.MX8. So what is
> the "reference" to know what is the correct string for i.MX8 platforms
> ? Does it really make sense to have this option in
> package/freescale-imx/Config.in ? Should we have it instead in imx-lib
> and imx-vpu instead ?

Well regarding i.MX8, it will be used in imx-vpu-hantro once updated [1].
But it is true it might the only place where it will be useful for
i.MX8.
For i.MX6, since it used in both imx-lib and imx-vpu, it felt right not
to duplicate this logic. So I guess i.MX8 platform naming went here for
consistency.
Also, since all the i.MX variants are declared in
freescale-imx/Config.in, feels ok to me to have the logic at the same
spot. But I'm open to moving it to different packages.

Regards,
Gary

[1] http://patchwork.ozlabs.org/patch/1262157/

  reply	other threads:[~2020-03-30  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 16:49 [Buildroot] [PATCH 0/2] imx: fix i.MX8MMini support Gary Bisson
2020-03-26 16:49 ` [Buildroot] [PATCH 1/2] package/freescale-imx: fix i.MX8MMini configuration Gary Bisson
2020-03-30  6:25   ` Thomas Petazzoni
2020-03-30  7:49     ` Gary Bisson [this message]
2020-03-26 16:49 ` [Buildroot] [PATCH 2/2] package/freescale-imx/imx-vpu-hantro: bump version to 1.15.0 Gary Bisson
2020-03-27 10:31   ` Laurent Gauthier
2020-03-27 14:27     ` Gary Bisson
2020-03-30  6:25   ` Thomas Petazzoni

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=20200330074905.GA5954@p1g2 \
    --to=gary.bisson@boundarydevices.com \
    --cc=buildroot@busybox.net \
    /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