From: Tom Rini <trini@konsulko.com>
To: Andrew Davis <afd@ti.com>
Cc: Simon Glass <sjg@chromium.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] configs: keystone2: Unwind KERNEL_MTD_PARTS definition
Date: Tue, 25 Jul 2023 13:54:45 -0400 [thread overview]
Message-ID: <20230725175445.GA3630934@bill-the-cat> (raw)
In-Reply-To: <431a4601-beda-21c4-13e8-81ef9be453de@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Tue, Jul 25, 2023 at 12:47:10PM -0500, Andrew Davis wrote:
> On 7/25/23 12:18 PM, Tom Rini wrote:
> > On Tue, Jul 25, 2023 at 11:40:58AM -0500, Andrew Davis wrote:
> >
> > > This is more complex than it needs to be and makes converting these
> > > boards over to plain text env files more difficult. Simplify this
> > > environment variable scheme.
> > >
> > > Signed-off-by: Andrew Davis <afd@ti.com>
> > > ---
> > > include/configs/k2e_evm.h | 5 +----
> > > include/configs/k2g_evm.h | 4 +---
> > > include/configs/k2hk_evm.h | 5 +----
> > > include/configs/k2l_evm.h | 5 +----
> > > include/configs/ti_armv7_keystone2.h | 6 +-----
> > > include/environment/ti/spi.h | 14 --------------
> > > 6 files changed, 5 insertions(+), 34 deletions(-)
> > > delete mode 100644 include/environment/ti/spi.h
> >
> > So this unwinding isn't quite enough as the defconfigs also set
> > CONFIG_MTDPARTS_DEFAULT and that's the best way.
>
> The one in CONFIG_MTDPARTS_DEFAULT is different from the one defined in k2*_evm.h,
> so switching would change the env. This patch was attempting to make no changes.
>
> Maybe a better question is do we need these anymore? They don't seem to do anything
> anymore and these partitions are board specific, so couldn't be set universally in
> defconfig anyway. Plus They are instead already defined (correctly too) in the DTS
> files for each board. Should we just drop mtdparts=?
So, CONFIG_MTDPARTS_DEFAULT (and related) largely just results in
setting mtdparts= in the default environment. So yes, if they're correct
in the DTS files the best thing to do is remove the CONFIG options and
remove the environment settings and then there won't be confusion about
which one is the source of truth.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-07-25 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 16:40 [PATCH 1/2] configs: keystone2: Unwind KERNEL_MTD_PARTS definition Andrew Davis
2023-07-25 16:40 ` [PATCH 2/2] configs: keystone2: Change to using env files Andrew Davis
2023-07-25 17:18 ` [PATCH 1/2] configs: keystone2: Unwind KERNEL_MTD_PARTS definition Tom Rini
2023-07-25 17:47 ` Andrew Davis
2023-07-25 17:54 ` Tom Rini [this message]
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=20230725175445.GA3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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