From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: bcm281xx: Add L2 cache enable code
Date: Wed, 6 Mar 2013 06:31:03 +0000 [thread overview]
Message-ID: <201303060631.03782.arnd@arndb.de> (raw)
In-Reply-To: <513677BB.9010309@broadcom.com>
On Tuesday 05 March 2013, Christian Daudt wrote:
> On 13-03-05 01:01 AM, Arnd Bergmann wrote:
> > On Tuesday 05 March 2013, Christian Daudt wrote:
> > For other firmware interfaces like this, we tend to list the specific commands
> > that the firmware understands. If you think there might be different versions
> > to consider, you might want to model this like
> >
> > Documentation/devicetree/bindings/arm/psci.txt
> This interface is stable and in shipping products at this time, and so
> the api will remain constant.
But what about future products? Wouldn't they be able to extend the
current interface in a compatible way?
> >> +static void __init init_irq(void)
> >> +{
> >> + irqchip_init();
> >> + bcm_kona_smc_init();
> >> +
> >> +#ifdef CONFIG_CACHE_L2X0
> >> + kona_l2_cache_init();
> >> +#endif /* CONFIG_CACHE_L2X0 */
> >> +}
> > Why are you calling bcm_kona_smc_init() and kona_l2_cache_init() from init_irq()?
> >
> > It seems completely unrelated to interrupt handling.
> >
> It was originally in init_machine section but I was told that that was
> too late and init_irq would be better, and I saw that highbank also has
> it in init_irq. I agree that it is unrelated to irq - is there a better
> place to put this in ?
IMHO the later the better. Do you know what issues were caused by having it
in init_machine?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Christian Daudt <csd-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
"arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
abhimanyu.kapur-1ViLX0X+lBJBDgjK7y7TUQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: bcm281xx: Add L2 cache enable code
Date: Wed, 6 Mar 2013 06:31:03 +0000 [thread overview]
Message-ID: <201303060631.03782.arnd@arndb.de> (raw)
In-Reply-To: <513677BB.9010309-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
On Tuesday 05 March 2013, Christian Daudt wrote:
> On 13-03-05 01:01 AM, Arnd Bergmann wrote:
> > On Tuesday 05 March 2013, Christian Daudt wrote:
> > For other firmware interfaces like this, we tend to list the specific commands
> > that the firmware understands. If you think there might be different versions
> > to consider, you might want to model this like
> >
> > Documentation/devicetree/bindings/arm/psci.txt
> This interface is stable and in shipping products at this time, and so
> the api will remain constant.
But what about future products? Wouldn't they be able to extend the
current interface in a compatible way?
> >> +static void __init init_irq(void)
> >> +{
> >> + irqchip_init();
> >> + bcm_kona_smc_init();
> >> +
> >> +#ifdef CONFIG_CACHE_L2X0
> >> + kona_l2_cache_init();
> >> +#endif /* CONFIG_CACHE_L2X0 */
> >> +}
> > Why are you calling bcm_kona_smc_init() and kona_l2_cache_init() from init_irq()?
> >
> > It seems completely unrelated to interrupt handling.
> >
> It was originally in init_machine section but I was told that that was
> too late and init_irq would be better, and I saw that highbank also has
> it in init_irq. I agree that it is unrelated to irq - is there a better
> place to put this in ?
IMHO the later the better. Do you know what issues were caused by having it
in init_machine?
Arnd
next prev parent reply other threads:[~2013-03-06 6:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 2:47 [PATCH] ARM: bcm281xx: Add L2 cache enable code Christian Daudt
2013-03-05 2:47 ` Christian Daudt
2013-03-05 9:01 ` Arnd Bergmann
2013-03-05 9:01 ` Arnd Bergmann
2013-03-05 22:54 ` Christian Daudt
2013-03-05 22:54 ` Christian Daudt
2013-03-06 6:31 ` Arnd Bergmann [this message]
2013-03-06 6:31 ` Arnd Bergmann
[not found] ` <5136F816.2070909@broadcom.com>
2013-03-06 11:28 ` Arnd Bergmann
2013-03-06 11:28 ` Arnd Bergmann
2013-03-06 15:05 ` Christian Daudt
2013-03-06 15:05 ` Christian Daudt
2013-04-10 17:33 ` [GIT PULL] ARM: bcm281xx firmware tags Christian Daudt
2013-04-10 17:33 ` Christian Daudt
2013-04-11 6:52 ` Olof Johansson
2013-04-11 6:52 ` Olof Johansson
2013-04-11 8:52 ` Olof Johansson
2013-04-11 8:52 ` Olof Johansson
2013-03-05 18:20 ` [PATCH] ARM: bcm281xx: Add L2 cache enable code Stephen Warren
2013-03-05 18:20 ` Stephen Warren
2013-03-05 22:56 ` Christian Daudt
2013-03-05 22:56 ` Christian Daudt
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=201303060631.03782.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.