linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tushar.behera@linaro.org (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: cache-l2x0: Parse properties from DT for PL310 cache controller
Date: Tue, 7 Jan 2014 17:40:56 +0530	[thread overview]
Message-ID: <CAHbNUh2Y5JPwAWojJE8Chd6fi5Hbk9c2+11FVBhOA-3Rgr5WpA@mail.gmail.com> (raw)
In-Reply-To: <3479510.EFrgCqQWpu@wuerfel>

On 7 January 2014 17:27, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 07 January 2014 17:11:28 Tushar Behera wrote:
>> Parsed auxiliary control properties for PL310 cache controller.
>>
>> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
>> ---
>> These properties are set for Exynos4 platform. If we can pass these properties
>> through device tree for Exynos4, then we can remove the hard-coded L2_AUX_VAL.
>
>
> The explanation would be good to have in the actual changeset

Ok, I will add these explanation to comment section.

> comment above the '---' line. Are all of them actually needed?
> You shouldn't havet o set the ones that are already turned on
> by the boot loader.

These are the extra options that we used to pass in the kernel. For
normal operation, I couldn't perceive any difference without these
properties. The only reason for adding these properties was to be in
sync with existing auxiliary control value.

>>
>> diff --git a/Documentation/devicetree/bindings/arm/l2cc.txt b/Documentation/devicetree/bindings/arm/l2cc.txt
>> index b513cb8..213546d 100644
>> --- a/Documentation/devicetree/bindings/arm/l2cc.txt
>> +++ b/Documentation/devicetree/bindings/arm/l2cc.txt
>> @@ -44,6 +44,16 @@ Optional properties:
>>  - cache-id-part: cache id part number to be used if it is not present
>>    on hardware
>>  - wt-override: If present then L2 is forced to Write through mode
>> +- arm,early-write: If present then BRSEP mode (early write response) is enabled.
>> +- arm,data-prefetch: If present then data prefetching is enabled.
>> +- arm,instruction-prefetch: If present then instruction prefetching is enabled.
>> +- arm,ns-interrupt-access: If present then interrupt mask and interrupt clear
>> +  registers can be read or modified in both secure or non-secure accesses.
>> +- arm,ns-lockdown: If present then non-secure accesses can write to lockdown
>> +  register.
>> +- arm,share-override: If present then shared attribute is ignored internally.
>> +- arm,full-line-of-zero: If present then 'full line of write zero' behaviour is
>> +  enabled.
>
> Is it intentional that you have the "arm," prefix for the new ones, while
> it's not there for the existing ones? Should we drop it for consistency?
>
>         Arnd

No specific reasons for this. I was following "arm,data-latency"
format. We can drop the "arm," prefix.

Thanks for the review.

-- 
Tushar Behera

  reply	other threads:[~2014-01-07 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 11:41 [PATCH] ARM: cache-l2x0: Parse properties from DT for PL310 cache controller Tushar Behera
2014-01-07 11:57 ` Arnd Bergmann
2014-01-07 12:10   ` Tushar Behera [this message]
2014-01-07 12:41 ` Sudeep Holla
2014-01-07 12:54   ` Arnd Bergmann
2014-01-07 15:55     ` Sudeep Holla
2014-01-07 16:12       ` Arnd Bergmann
2014-01-07 16:43         ` Sudeep Holla

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=CAHbNUh2Y5JPwAWojJE8Chd6fi5Hbk9c2+11FVBhOA-3Rgr5WpA@mail.gmail.com \
    --to=tushar.behera@linaro.org \
    --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).