From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 8/9] configs: ti_omap3_common: Enable workaround for ARM errata 454179, 430973, 621766
Date: Wed, 25 Feb 2015 22:23:35 +0100 [thread overview]
Message-ID: <1424899415.2534.3.camel@aldrin> (raw)
In-Reply-To: <CAGo_u6rEaSqhzeQP2dXYXJsr2mZ9B_YbL8iUhrLVuW6rBuSOKA@mail.gmail.com>
Le mercredi 25 f?vrier 2015 ? 08:32 -0600, menon.nishanth at gmail.com a
?crit :
> On Wed, Feb 25, 2015 at 6:27 AM, Paul Kocialkowski <contact@paulk.fr> wrote:
> > Le mercredi 25 f?vrier 2015 ? 13:31 +0200, Igor Grinberg a ?crit :
> >> On 02/25/15 13:19, Paul Kocialkowski wrote:
> >> > Le mardi 24 f?vrier 2015 ? 16:57 -0600, Nishanth Menon a ?crit :
> >> >> Enable the OMAP3 specific errata code for 454179, 430973, 621766
> >> >> and while at it, remove legacy non-revision checked errata logic.
> >> >>
> >> >> Signed-off-by: Nishanth Menon <nm@ti.com>
> >> >> ---
> >> >> arch/arm/cpu/armv7/omap3/board.c | 16 ----------------
> >> >> include/configs/ti_omap3_common.h | 6 ++++++
> >> >> 2 files changed, 6 insertions(+), 16 deletions(-)
> >> >>
> >> >> diff --git a/arch/arm/cpu/armv7/omap3/board.c b/arch/arm/cpu/armv7/omap3/board.c
> >> >> index 7ce30949a6c6..cc3a43341335 100644
> >> >> --- a/arch/arm/cpu/armv7/omap3/board.c
> >> >> +++ b/arch/arm/cpu/armv7/omap3/board.c
> >> >> @@ -35,7 +35,6 @@ DECLARE_GLOBAL_DATA_PTR;
> >> >>
> >> >> /* Declarations */
> >> >> extern omap3_sysinfo sysinfo;
> >> >> -static void omap3_setup_aux_cr(void);
> >> >> #ifndef CONFIG_SYS_L2CACHE_OFF
> >> >> static void omap3_invalidate_l2_cache_secure(void);
> >> >> #endif
> >> >> @@ -246,9 +245,6 @@ void s_init(void)
> >> >>
> >> >> try_unlock_memory();
> >> >>
> >> >> - /* Errata workarounds */
> >> >> - omap3_setup_aux_cr();
> >> >> -
> >> >> #ifndef CONFIG_SYS_L2CACHE_OFF
> >> >> /* Invalidate L2-cache from secure mode */
> >> >> omap3_invalidate_l2_cache_secure();
> >> >> @@ -428,18 +424,6 @@ void omap3_update_aux_cr_secure(u32 set_bits, u32 clear_bits)
> >> >> }
> >> >> }
> >> >>
> >> >> -static void omap3_setup_aux_cr(void)
> >> >> -{
> >> >> - /* Workaround for Cortex-A8 errata: #454179 #430973
> >> >> - * Set "IBE" bit
> >> >> - * Set "Disable Branch Size Mispredicts" bit
> >> >> - * Workaround for erratum #621766
> >> >> - * Enable L1NEON bit
> >> >> - * ACR |= (IBE | DBSM | L1NEON) => ACR |= 0xE0
> >> >> - */
> >> >> - omap3_update_aux_cr_secure(0xE0, 0);
> >> >> -}
> >> >> -
> >> >> #ifndef CONFIG_SYS_L2CACHE_OFF
> >> >> static void omap3_update_aux_cr(u32 set_bits, u32 clear_bits)
> >> >> {
> >> >> diff --git a/include/configs/ti_omap3_common.h b/include/configs/ti_omap3_common.h
> >> >> index f909f6b94a18..db15c12ddf53 100644
> >> >> --- a/include/configs/ti_omap3_common.h
> >> >> +++ b/include/configs/ti_omap3_common.h
> >> >
> >> > Only a couple of OMAP3 boards in U-Boot include ti_omap3_common.h. You
> >> > can find a complete list of all the configs that need those options
> >> > enabled from my first patch on that topic:
> >> > http://lists.denx.de/pipermail/u-boot/2015-February/205809.html
> >> >
> >> > I guess it's better to enable those on all the currently-supported omap3
> >> > platforms: that's the way it was so far and it won't hurt in cases it's
> >> > not needed thanks to the revision detection.
> >>
> >> Or...
> >> I think this patch might be a good enough argument to request people
> >> switch to include ti_omap3_common.h instead of duplicating it in
> >> private configs...
> >>
> >> Don't you think?
> >
> > The way I see it, ti_omap3_common.h is common for OMAP3 boards made by
> > TI. A few things there are not generic to omap3 in general (e.g. not
> > every board uses the U-Boot SPL, or UART3 for console).
> >
> > However, I agree it would be beneficial to have an omap3_common.h config
> > with the options that are expected to be shared accross every possible
> > omap3 device (and with a few clever ifdef so that the minimum has to be
> > set in the including board configs).
> >
> > I could try to come up with such a config if you wish, but I'm afraid
> > I'm not the most qualified person to do this (I only have a single omap3
> > device).
> I am planning on a V3 based on trying to converge exynos and TI
> platforms into a common code base. I will stick with ti_*_common.h
> headers for now, we will keep all the other headers updated for the
> moment. I do stand with the opinion that we should all be using the
> same ti_omap3_common header for all platforms using the same SoC...
> but that could be done as follow on patches.
>
> That said, Paul, if you could contribute patches to the effect of
> integrating all these platforms to ti_*_common.h, that'd be great.
I will try to come up with a common configuration for omap3 (and
possibly omap4 and omap5 too). Do you mind if I drop the ti_ prefix? I
don't feel it's relevant to mention the chip manufacturer there,
especially when it's not used anywhere else in the tree (except for the
boards that are actually procuced by TI such as the evms, etc).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150225/42863f0e/attachment.sig>
next prev parent reply other threads:[~2015-02-25 21:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 22:57 [U-Boot] [PATCH V2 0/9] ARM: OMAP3-DRA7: CP15 erratum workarounds and improvements Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 1/9] ARM: OMAP: Change set_pl310_ctrl_reg to be generic Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 2/9] ARM: OMAP3: Rename omap3.h to omap.h to be generic as all SoCs Nishanth Menon
2015-02-25 11:02 ` Paul Kocialkowski
2015-02-25 17:53 ` Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 3/9] ARM: OMAP3: Get rid of omap3_gp_romcode_call and replace with omap_smc1 Nishanth Menon
2015-02-25 11:06 ` Paul Kocialkowski
2015-02-24 22:57 ` [U-Boot] [PATCH V2 4/9] ARM: Provide a mechanism to invoke SoC specific errata WA for CP15 Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 5/9] ARM: DRA7 / OMAP5: Add workaround for ARM errata 798870 Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 6/9] configs: ti_omap5_common: Enable " Nishanth Menon
2015-02-24 22:57 ` [U-Boot] [PATCH V2 7/9] ARM: OMAP3: Introduce OMAP3 Cortex-A8 revision specific errata Nishanth Menon
2015-02-25 11:15 ` Paul Kocialkowski
2015-02-25 19:49 ` Nishanth Menon
2015-03-03 7:30 ` Siarhei Siamashka
2015-02-24 22:57 ` [U-Boot] [PATCH V2 8/9] configs: ti_omap3_common: Enable workaround for ARM errata 454179, 430973, 621766 Nishanth Menon
2015-02-25 11:19 ` Paul Kocialkowski
2015-02-25 11:31 ` Igor Grinberg
2015-02-25 12:27 ` Paul Kocialkowski
2015-02-25 14:32 ` menon.nishanth at gmail.com
2015-02-25 21:23 ` Paul Kocialkowski [this message]
2015-02-26 5:11 ` Nishanth Menon
2015-02-27 19:27 ` Paul Kocialkowski
2015-02-24 22:57 ` [U-Boot] [PATCH V2 9/9] ARM: OMAP5 / DRA7: Setup L2 Aux Control Register with recommended configuration Nishanth Menon
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 22:52 [U-Boot] [PATCH V2 0/9] ARM: OMAP3-DRA7: CP15 erratum workarounds and improvements Nishanth Menon
2015-02-24 22:52 ` [U-Boot] [PATCH V2 8/9] configs: ti_omap3_common: Enable workaround for ARM errata 454179, 430973, 621766 Nishanth Menon
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=1424899415.2534.3.camel@aldrin \
--to=contact@paulk.fr \
--cc=u-boot@lists.denx.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