From: csd@broadcom.com (Christian Daudt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: bcm281xx: Add L2 support for Rev A2 chips
Date: Fri, 3 May 2013 10:13:42 -0700 [thread overview]
Message-ID: <5183F046.9020802@broadcom.com> (raw)
In-Reply-To: <20130503085100.GA6188@mudshark.cambridge.arm.com>
On 13-05-03 01:51 AM, Will Deacon wrote:
> Hi Christian,
>
> On Fri, May 03, 2013 at 01:57:33AM +0100, Christian Daudt wrote:
>> Rev A2 SoCs have an unorthodox memory re-mapping and this needs
>> to be reflected in the cache operations.
>> This patch adds new outer cache functions for the l2x0 driver
>> to support this SoC revision. It also adds a new compatible
>> value for the cache to enable this functionality.
>>
>> Updates from V1:
>> - remove section 1 altogether and note that in comments
>> - simplify section selection caused by section 1 removal
>> - BUG_ON just in case section 1 shows up
> Looking much better now :)
>
>> diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c
>> index c465fac..d70e0ab 100644
>> --- a/arch/arm/mm/cache-l2x0.c
>> +++ b/arch/arm/mm/cache-l2x0.c
>> @@ -523,6 +523,147 @@ static void aurora_flush_range(unsigned long start, unsigned long end)
>> }
>> }
>>
>> +/*
>> + * For certain Broadcom SoCs, depending on the address range, different offsets
>> + * need to be added to the address before passing it to L2 for
>> + * invalidation/clean/flush
>> + *
>> + * Section Address Range Offset EMI
>> + * 1 0x00000000 - 0x3FFFFFFF 0x80000000 VC
>> + * 2 0x40000000 - 0xBFFFFFFF 0x40000000 SYS
>> + * 3 0xC0000000 - 0xFFFFFFFF 0x80000000 VC
> I don't think you answered last time (or I missed it) but where is the RAM
> in the physical memory map for boards with this L2 controller? Do you
> actually have 3GB at 0x40000000?
There can be up to 1G for VC and 1G for SYS. Usually that translates to
0x80000000-0xFFFFFFFF
thanks,
csd
WARNING: multiple messages have this Message-ID (diff)
From: "Christian Daudt" <csd@broadcom.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Russell King <linux@arm.linux.org.uk>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Stephen Warren <swarren@wwwdotorg.org>,
"arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"csd_b@daudt.org" <csd_b@daudt.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
Josh Cartwright <josh.cartwright@ni.com>,
Yehuda Yitschak <yehuday@marvell.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] ARM: bcm281xx: Add L2 support for Rev A2 chips
Date: Fri, 3 May 2013 10:13:42 -0700 [thread overview]
Message-ID: <5183F046.9020802@broadcom.com> (raw)
In-Reply-To: <20130503085100.GA6188@mudshark.cambridge.arm.com>
On 13-05-03 01:51 AM, Will Deacon wrote:
> Hi Christian,
>
> On Fri, May 03, 2013 at 01:57:33AM +0100, Christian Daudt wrote:
>> Rev A2 SoCs have an unorthodox memory re-mapping and this needs
>> to be reflected in the cache operations.
>> This patch adds new outer cache functions for the l2x0 driver
>> to support this SoC revision. It also adds a new compatible
>> value for the cache to enable this functionality.
>>
>> Updates from V1:
>> - remove section 1 altogether and note that in comments
>> - simplify section selection caused by section 1 removal
>> - BUG_ON just in case section 1 shows up
> Looking much better now :)
>
>> diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c
>> index c465fac..d70e0ab 100644
>> --- a/arch/arm/mm/cache-l2x0.c
>> +++ b/arch/arm/mm/cache-l2x0.c
>> @@ -523,6 +523,147 @@ static void aurora_flush_range(unsigned long start, unsigned long end)
>> }
>> }
>>
>> +/*
>> + * For certain Broadcom SoCs, depending on the address range, different offsets
>> + * need to be added to the address before passing it to L2 for
>> + * invalidation/clean/flush
>> + *
>> + * Section Address Range Offset EMI
>> + * 1 0x00000000 - 0x3FFFFFFF 0x80000000 VC
>> + * 2 0x40000000 - 0xBFFFFFFF 0x40000000 SYS
>> + * 3 0xC0000000 - 0xFFFFFFFF 0x80000000 VC
> I don't think you answered last time (or I missed it) but where is the RAM
> in the physical memory map for boards with this L2 controller? Do you
> actually have 3GB@0x40000000?
There can be up to 1G for VC and 1G for SYS. Usually that translates to
0x80000000-0xFFFFFFFF
thanks,
csd
next prev parent reply other threads:[~2013-05-03 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 0:57 [PATCH V2] ARM: bcm281xx: Add L2 support for Rev A2 chips Christian Daudt
2013-05-03 0:57 ` Christian Daudt
2013-05-03 8:51 ` Will Deacon
2013-05-03 8:51 ` Will Deacon
2013-05-03 17:13 ` Christian Daudt [this message]
2013-05-03 17:13 ` Christian Daudt
2013-05-03 17:30 ` Will Deacon
2013-05-03 17:30 ` Will Deacon
2013-05-09 20:44 ` Olof Johansson
2013-05-09 20:44 ` Olof Johansson
2013-05-10 17:43 ` Russell King - ARM Linux
2013-05-10 17:43 ` Russell King - ARM Linux
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=5183F046.9020802@broadcom.com \
--to=csd@broadcom.com \
--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.