From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v2 1/2] Documentation: arm: add cache DT bindings
Date: Mon, 27 Jan 2014 12:58:39 +0000 [thread overview]
Message-ID: <20140127125839.GL15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140121114845.GA2598@e103592.cambridge.arm.com>
On Tue, Jan 21, 2014 at 11:49:01AM +0000, Dave Martin wrote:
> I do have a worry that because the kernel won't normally use this
> information, by default it will get pasted between .dts files, won't get
> tested and will be wrong rather often. It also violates the DT principle
> that probeable information should not be present in the DT -- ePAPR
> obviously envisages systems where cache geometry information is not
> probeable, but that's not the case for architected caches on ARM, except
> in rare cases where the CLIDR is wrong.
That statement is wrong. There are caches on ARM CPUs where there is no
CLIDR register. I suggest reading the earlier DDI0100 revisions.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-27 12:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 17:47 [PATCH RFC v2 0/2] ARM: defining power states DT bindings Lorenzo Pieralisi
2014-01-20 17:47 ` [PATCH RFC v2 1/2] Documentation: arm: add cache " Lorenzo Pieralisi
2014-01-21 11:49 ` Dave Martin
2014-01-21 14:47 ` Lorenzo Pieralisi
2014-01-27 12:58 ` Russell King - ARM Linux [this message]
2014-01-27 18:10 ` Lorenzo Pieralisi
2014-01-20 17:47 ` [PATCH RFC v2 2/2] Documentation: arm: define DT C-states bindings Lorenzo Pieralisi
2014-01-21 11:16 ` Vincent Guittot
2014-01-21 13:31 ` Lorenzo Pieralisi
2014-01-21 14:35 ` Amit Kucheria
2014-01-21 15:23 ` Lorenzo Pieralisi
2014-01-22 11:52 ` Mark Brown
2014-01-22 16:23 ` Lorenzo Pieralisi
2014-01-22 18:17 ` Mark Brown
2014-01-22 11:42 ` Mark Brown
2014-01-22 16:33 ` Lorenzo Pieralisi
2014-01-22 18:11 ` Mark Brown
2014-01-22 19:20 ` Lorenzo Pieralisi
2014-01-24 8:40 ` Vincent Guittot
2014-01-24 17:58 ` Lorenzo Pieralisi
2014-01-28 8:24 ` Vincent Guittot
2014-01-29 12:42 ` Lorenzo Pieralisi
2014-01-25 8:15 ` Antti P Miettinen
2014-01-27 11:41 ` Lorenzo Pieralisi
2014-01-27 12:48 ` Antti P Miettinen
2014-01-27 18:22 ` Lorenzo Pieralisi
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=20140127125839.GL15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).