From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: shmobile: armadillo800eva: enable all errata for cache on defconfig
Date: Tue, 05 Mar 2013 05:57:00 +0000 [thread overview]
Message-ID: <20130305055659.GC9711@verge.net.au> (raw)
In-Reply-To: <1346808893-14124-2-git-send-email-horms@verge.net.au>
On Sun, Mar 03, 2013 at 04:42:08PM -0800, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > > > Some errata for cache had not enabled on current
> > > > > > Armadillo800eva defconfig.
> > > > > > This patch enables these.
> > > > > > Special thanks to Ishiyama-san
> > > > >
> > > > > It seems to me that it would be better to handle these in Kconfig
> > > > > to enable them on an SoC or board basis.
> > > > >
> > > > > The reason is that I would like to move away from per-board defconfigs
> > > > > and towards a more consolidated defconfig. And in that case it will
> > > > > be more difficult to know which ERRATA are needed for each board and SoC.
> > > > >
> > > > > Obviously this thinking is open to review and it implies that
> > > > > several board defconfigs should be updated.
> > >
> > > We used defconfig selection for CPU/board settings before.
> > > But Kconfig selection for ERRATA make sense.
> > >
> > > Do you want to me to send v2 patch which use Kconfig ?
> > > Or do you do that ?
> >
> > I'd like you to send v2 if possible.
>
> OK, but I noticed that it will be complex if we select these ERRATA on Kconfig,
> Because, these ERRATAs dependency.
Thanks, I see this is indeed getting messy.
The reason that I asked is that I would like to consolidate the defconfigs.
Ideally one for shmobile. But more realistically one per SoC. And I thought
that avoiding adding ERRATAs to defconfigs would make that slightly easier
in the long run. But I don't think it justifies dealing with the mess
you describe below. So I will apply the patch as is.
> Ex)
> config PL310_ERRATA_588369
> bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
> depends on CACHE_L2X0
>
> It depends on CACHE_L2X0, but this CACHE_L2X0 selection is depend on user,
> this means that there is no guarantee that CACHE_L2X0 is selected.
> Then, the Kconfig will be...
>
> select PL310_ERRATA_588369 if CACHE_L2X0
>
> And more complex ERRARA dependency is...
>
> config ARM_ERRATA_742230
> bool "ARM errata: DMB operation may be faulty"
> depends on CPU_V7 && SMP
> depends on !ARCH_MULTIPLATFORM
>
> Of course I can use above style on Kconfig,
> but my worry is we will have unknown trouble
> if someone updated these ERRATA implementation and dependency
> in the future...
>
> This is example, but I tested below.
> This means we can select unnecessary settings on Kconfig ...
>
> ----------------
> config ARM_ERRATA_326103
> bool "ARM errata: FSR write bit incorrect on a SWP to read-only memory"
> => depends on CPU_V6
> ...
>
> config ARCH_R8A7740
> bool "R-Mobile A1 (R8A77400)"
> select ARCH_WANT_OPTIONAL_GPIOLIB
> => select CPU_V7
> => select ARM_ERRATA_326103
> ...
>
> > grep ERRATA .config
> CONFIG_ARM_ERRATA_326103=y
> ----------------------
>
> Best regards
> ---
> Kuninori Morimoto
>
next prev parent reply other threads:[~2013-03-05 5:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 23:18 [GIT PULL] Renesas ARM-based SoC fix for v3.6 Rafael J. Wysocki
2012-08-27 23:33 ` Olof Johansson
2012-08-30 5:38 ` Simon Horman
2012-08-30 5:38 ` [PATCH] ARM: shmobile: marzen: fixup smsc911x id for regulator Simon Horman
2012-09-02 15:23 ` [GIT PULL] Renesas ARM-based SoC fix for v3.6 Olof Johansson
2012-09-05 1:34 ` [GIT PULL] Renesas ARM-based SoC fix for v3.6 #2 Simon Horman
2012-09-05 1:34 ` [PATCH 1/3] ARM: shmobile: armadillo800eva: fixup: sound card detection order Simon Horman
2013-02-22 4:45 ` [PATCH 1/3] ARM: shmobile: armadillo800eva: enable all errata for cache on defconfig Kuninori Morimoto
2013-02-22 22:58 ` Simon Horman
2013-03-01 6:53 ` Simon Horman
2013-03-01 10:01 ` Kuninori Morimoto
2013-03-01 13:02 ` Simon Horman
2013-03-04 0:42 ` Kuninori Morimoto
2013-03-05 5:57 ` Simon Horman [this message]
2013-03-06 4:46 ` Simon Horman
2015-01-19 9:54 ` [PATCH 1/3] ARM: shmobile: armadillo800eva: Properly specify HDMI audio link format Lars-Peter Clausen
2015-01-19 9:54 ` [PATCH 2/3] ASoC: sh: fsi: Fix clock inversion Lars-Peter Clausen
2015-01-19 12:23 ` Sergei Shtylyov
2015-01-19 9:54 ` [PATCH 3/3] ASoC: simple-card: Remove support for setting differing DAI formats Lars-Peter Clausen
2015-01-20 0:11 ` Kuninori Morimoto
2012-09-05 1:34 ` [PATCH 2/3] ARM: shmobile: mackerel: fixup usb module order Simon Horman
2012-09-05 1:34 ` [PATCH 3/3] ARM: shmobile: armadillo800eva: enable rw rootfs mount Simon Horman
2013-02-22 4:46 ` [PATCH 3/3] ARM: shmobile: armadillo800eva: enable NEON on defconfig Kuninori Morimoto
2013-02-22 23:09 ` Simon Horman
2013-02-25 0:17 ` Kuninori Morimoto
2013-02-25 0:21 ` Kiyoshi Ishiyama
2013-03-01 9:41 ` Simon Horman
2012-09-05 4:44 ` [GIT PULL] Renesas ARM-based SoC fix for v3.6 #2 Olof Johansson
2012-09-05 4:53 ` Simon Horman
2012-09-18 4:46 ` [GIT PULL] Renesas ARM-based SoC fix for v3.6 #3 Simon Horman
2012-09-18 4:46 ` [PATCH] ARM: shmobile: kzm9g: bugfix: correct mmcif interrupt settings Simon Horman
2012-09-18 14:41 ` [GIT PULL] Renesas ARM-based SoC fix for v3.6 #3 Olof Johansson
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=20130305055659.GC9711@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).