From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: mvebu: rename ARM_ERRATA_753970
Date: Wed, 05 Nov 2014 10:11:31 +0100 [thread overview]
Message-ID: <1415178691.20372.225.camel@x220> (raw)
In-Reply-To: <20140912133142.GJ12361@n2100.arm.linux.org.uk>
Hi Russell,
On Fri, 2014-09-12 at 14:31 +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 12, 2014 at 01:10:05PM +0200, Paul Bolle wrote:
> > ARM_ERRATA_753970 was renamed to PL310_ERRATA_753970 in v3.2, through
> > commit fa0ce4035d48 ("ARM: 7162/1: errata: tidy up Kconfig options for
> > PL310 errata workarounds"). Two selects were added in v3.15 that still
> > use the previous name. Rename these. Make these select statements depend
> > on CACHE_L2X0, like all other select statements for PL310_ERRATA_753970
> > do, to be safe we don't inadvertently start to allow pointless
> > configurations in the future.
> >
> > Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> > ---
> > v3: add CACHE_L2X0 dependency, as Russell requested.
> >
> > Tested with "git grep" and fiddling with "make ARCH=arm [...]config".
> > Please shout if that's deemed insufficient.
> >
> > Note that I promised this v3 over two months ago. Taking two months to
> > update this patch is not really something to be proud of. On the other
> > hand: no one bothered to prod me for this v3 or send in a proper fix
> > themselves. Add to this that I first reported these selects for an
> > outdated Kconfig symbol in April. So I begin to wonder whether these
> > selects statements are really needed to begin with.
Whatever will be done in the long run: no one else said anything about
my v3. It's now nearly seven months since I first reported this issue.
In the mean time three releases contained the bogus selects. Apparently
neither Marvell Armada 375 boards nor Marvell Armada 380/385 boards
actually need to select PL310_ERRATA_753970.
I think I'll send a trivial cleanup shortly.
> I wonder whether we should deal with this a different way: rather than
> having this stuff as a configuration option, have the work-arounds
> default to being enabled, and have kernel command parameters to disable
> them should that be necessary.
>
> I expect the normal case is that everyone normally runs with these
> errata workarounds enabled (especially with a single zImage kernel), so
> there will be relatively few who need to disable them. Plus, this gives
> flexibility on single zImage to turn the errata workarounds off without
> needing to rebuild.
>
> The other major advantage is less Kconfig options with dependencies
> which seem all to easily to result in select abuse.
I have no idea what CACHE_L2X0, ie the L2x0 outer cache controller,
actually does nor what those PL310 errata are all about. So I can't
comment on the feasibility of your idea. Obviously, dropping Kconfig
symbols, and making configuration a bit easier would be one of the
benefits of that idea. But I wouldn't know whether it outweighs the
costs involved.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2014-11-05 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201404052101.19381.arnd@arndb.de>
2014-04-05 19:02 ` [GIT PULL 1/8] ARM: SoC non-critical bug fixes for 3.15 Arnd Bergmann
2014-04-05 19:03 ` [GIT PULL 2/8] ARM: SoC: cleanups " Arnd Bergmann
2014-04-05 19:04 ` [GIT PULL 3/8] ARM: SoC specific changes Arnd Bergmann
[not found] ` <1396777049.30640.9.camel@x220>
2014-04-06 17:02 ` Kconfig ARM_ERRATA_753970? Gregory CLEMENT
2014-04-06 17:28 ` Paul Bolle
2014-05-26 9:01 ` [PATCH] ARM: mvebu: rename ARM_ERRATA_753970 Paul Bolle
2014-06-20 20:21 ` Jason Cooper
2014-06-20 20:42 ` Paul Bolle
2014-06-20 21:10 ` Jason Cooper
2014-06-23 7:58 ` Paul Bolle
2014-06-20 20:53 ` Russell King - ARM Linux
2014-06-23 9:01 ` [PATCH v2] " Paul Bolle
2014-06-23 9:07 ` Russell King - ARM Linux
2014-06-23 9:34 ` Paul Bolle
2014-09-12 11:10 ` [PATCH v3] " Paul Bolle
2014-09-12 13:31 ` Russell King - ARM Linux
2014-11-05 9:11 ` Paul Bolle [this message]
2014-04-05 19:04 ` [GIT PULL 4/8] ARM: SoC: board changes Arnd Bergmann
2014-04-05 19:05 ` [GIT PULL 5/8] ARM: SoC: device tree changes Arnd Bergmann
2014-04-05 19:06 ` [GIT PULL 6/8] ARM: SoC: driver changes Arnd Bergmann
2014-04-05 19:06 ` [GIT PULL 7/8] ARM: SoC: sh " Arnd Bergmann
2014-04-05 19:07 ` [GIT PULL 8/8] ARM: SoC: late cleanups Arnd Bergmann
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=1415178691.20372.225.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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).