From: Sudeep Holla <sudeep.holla@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Dirk Behme <dirk.behme@gmail.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] arm64: dts: r8a7795: Add L2 cache-controller nodes
Date: Fri, 18 Dec 2015 13:46:56 +0000 [thread overview]
Message-ID: <56740E50.9060607@arm.com> (raw)
In-Reply-To: <CAMuHMdUjjR1UuQDCwsV4U-tSR95W_Go_2u=BBehotCd9vQ9ZJA@mail.gmail.com>
On 18/12/15 13:33, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Fri, Dec 18, 2015 at 12:56 PM, Dirk Behme <dirk.behme@gmail.com> wrote:
>> On 18.12.2015 12:03, Geert Uytterhoeven wrote:
>>> On Sat, Dec 12, 2015 at 8:16 AM, Dirk Behme <dirk.behme@gmail.com> wrote:
>>>> From: Geert Uytterhoeven <geert+renesas@glider.be>
>>>>
>>>> Add device nodes for the L2 caches, and link the CPU node to its L2
>>>> cache node.
>>>>
>>>> The L2 cache for the Cortex-A57 CPU cores is 2 MiB large (organized as
>>>> 128 KiB x 16 ways).
>>>>
>>>> The L2 cache for the Cortex-A53 CPU cores is 512 KiB large (organized as
>>>> 32 KiB x 16 ways).
>>>>
>>>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>>> ---
>>>> Note: Geert: I picked your patch from
>>>>
>>>> http://www.spinics.net/lists/arm-kernel/msg466628.html
>>>>
>>>> incoporated some review comments and rebased it against
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas.git/log/?h=next
>>>> renesas-next-20151211v2-v4.4-rc1
>>>
>>> This is more or less what I have locally, except that I kept the latency
>>> properties
>>
>> Hmm, maybe I missed anything, but the only part reading the latency I can
>> find is
>>
>> arch/arm/mm/cache-l2x0.c
>>
>> [1] which isn't relevant for arm64?
>
> No driver using a property in DT is not a reason not to put the property in DT.
> The r8a7995 datasheet does contain the latency values to use.
>
While I agree with that, I would avoid having these values for 2 reasons:
1. Others might blindly copy and expect these setting to done in Linux
or any non-secure OS using DT which is clearly not possible on ARM64
2. Going by your argument, we usually have much more in datasheets
which are not all in DT, so strictly speaking that's not a reason to
have it here.
Again I am not against it, just an opinion.
--
Regards,
Sudeep
next prev parent reply other threads:[~2015-12-18 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 7:16 [PATCH 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores Dirk Behme
2015-12-12 7:16 ` [PATCH 2/2] arm64: dts: r8a7795: Add L2 cache-controller nodes Dirk Behme
2015-12-18 11:03 ` Geert Uytterhoeven
2015-12-18 11:56 ` Dirk Behme
2015-12-18 13:33 ` Geert Uytterhoeven
2015-12-18 13:46 ` Sudeep Holla [this message]
2015-12-18 11:02 ` [PATCH 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores Geert Uytterhoeven
2015-12-18 11:58 ` Dirk Behme
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=56740E50.9060607@arm.com \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.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).