From: csd@broadcom•com (Christian Daudt)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: bcm281xx: Add L2 cache enable code
Date: Tue, 5 Mar 2013 14:56:12 -0800 [thread overview]
Message-ID: <5136780C.7030801@broadcom.com> (raw)
In-Reply-To: <51363770.5060201@wwwdotorg.org>
On 13-03-05 10:20 AM, Stephen Warren wrote:
> On 03/04/2013 07:47 PM, Christian Daudt wrote:
>> - Adds a module to provide calls into secure monitor mode
>> - Uses this module to make secure monitor calls to enable L2 cache.
>> diff --git a/Documentation/devicetree/bindings/misc/smc.txt b/Documentation/devicetree/bindings/misc/smc.txt
>> +Example:
>> + smc at 0x3404c000 {
>> + compatible = "bcm,kona-smc";
> Both here in this example, and ...
>
>> diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arch/arm/boot/dts/bcm11351.dtsi
>> + smc at 0x3404c000 {
>> + compatible = "bcm,kona-smc";
> Here in the actual .dts file, you should include the specific ID of the
> SoC too, so that if there are Soc-specific bugs, the compatible property
> that's required to determine this is present from the start. In other words,
>
> compatible = "bcm,bcm11351-smc", "bcm,kona-smc";
>
> (which SoC ID you use in the example is arbitrary, but it may as well
> match the .dts file you're editing in the patch).
>
ok. done.
thanks,
csd
prev parent reply other threads:[~2013-03-05 22:56 UTC|newest]
Thread overview: 11+ 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 9:01 ` Arnd Bergmann
2013-03-05 22:54 ` Christian Daudt
2013-03-06 6:31 ` Arnd Bergmann
[not found] ` <5136F816.2070909@broadcom.com>
2013-03-06 11:28 ` Arnd Bergmann
2013-03-06 15:05 ` Christian Daudt
2013-04-10 17:33 ` [GIT PULL] ARM: bcm281xx firmware tags Christian Daudt
2013-04-11 6: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 22:56 ` Christian Daudt [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=5136780C.7030801@broadcom.com \
--to=csd@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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