From: Mark Rutland <mark.rutland@arm.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Wenyou Yang <wenyou.yang@atmel.com>
Subject: Re: [PATCH] ARM: at91: sama5: configure L2 cache
Date: Fri, 19 Sep 2014 20:27:24 +0100 [thread overview]
Message-ID: <20140919192724.GH26036@leverpostej> (raw)
In-Reply-To: <20140918212836.GD29620@piout.net>
[...]
> > There have been DT bindings proposed for prefetch control register. I
> > suggest that you search this mailing list for that patch, and check
> > whether it is acceptable for your platform.
> >
>
> I'm really wondering whether we should really put that in the device
> tree... We will soon end up with a property for each bit of each
> registers and the binding will end up being huge. Also, that is
> configuration, not HW description.
If it's configuration, why is putting it in a board file any better?
The optimal values will depend on the workload, which depends on more
than the just the machine. If anything this kind of tuning might be
better handled using kernel command line parameters.
> I actually tried multiple things, without any satisfaction:
> - using DT, with the main issue that we will definitely end up with one
> property per bit of configuration
>
> - adding an .l2c_prefetch_val to the machine start but that is kind of
> ugly.
>
> - adding a new parameter to l2x0_of_init()
>
> So I ended up choosing to do it in the platform code. But if everybody
> is fine with adding more properties to DT, I can go that way.
We can add properties as necessary. The fun part is deciding what is
necessary.
Mark.
prev parent reply other threads:[~2014-09-19 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 20:38 [PATCH] ARM: at91: sama5: configure L2 cache Alexandre Belloni
2014-09-18 21:02 ` Russell King - ARM Linux
2014-09-18 21:28 ` Alexandre Belloni
2014-09-19 19:27 ` Mark Rutland [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=20140919192724.GH26036@leverpostej \
--to=mark.rutland@arm.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=wenyou.yang@atmel.com \
/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