From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: l2x0: Add OF based initialization
Date: Tue, 07 Jun 2011 11:54:47 -0500 [thread overview]
Message-ID: <4DEE57D7.1030704@gmail.com> (raw)
In-Reply-To: <BANLkTi=7rHjKV=+hNKzEHvZMeDPwknOWtg@mail.gmail.com>
Olof,
On 06/07/2011 11:20 AM, Olof Johansson wrote:
> On Tue, Jun 7, 2011 at 7:22 AM, Rob Herring<robherring2@gmail.com> wrote:
>
>> +- aux-value : Value to set the Auxillary Control register to. Setting masked
>> + bits is undefined. Default value is 0.
>> +- aux-mask : Mask of bits to preserve in the Auxillary Control register.
>> + Default value is 0xffffffff.
>
> The device tree should describe the hardware, not the way the linux
> kernel drives the hardware. In the case of the AUX register, it's
> mostly a collection of options that are either turned on or off. I
> don't think they should necessarily be described as an opaque 32-bit
> word, but instead as separate attributes.
Unfortunately, the meaning of the bits depends on the model and there
doesn't seem to be any commonality or subset of options as to what each
platform is setting up.
>
> At least the geometry should be specified that way.
That's probably the only part that doesn't get changed. :)
>
> For feature enable bits, it depends on what features should be enabled
> and from the kernel side. I'm not sure that belongs in the device tree
> at all.
I don't think it can be decided what the kernel needs to setup by the
device tree. The main reason it's needed in the kernel at all is
probably because the bootloader didn't setup aux_ctrl or set it up
incorrectly.
Perhaps the magic values should just be left in the platforms and
continue to be passed into the OF init function:
l2x0_of_init(__u32 aux_val, __u32 aux_mask);
Rob
next prev parent reply other threads:[~2011-06-07 16:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 14:22 [PATCH v2 0/3] DT bindings for Cortex A9 peripherals Rob Herring
2011-06-07 14:22 ` [PATCH 1/3] ARM: pmu: add OF probing support Rob Herring
2011-06-08 15:54 ` Mark Rutland
2011-06-08 16:40 ` Rob Herring
2011-06-13 9:35 ` [PATCH 0/4] ARM: pmu: improve PMU type identification Mark Rutland
2011-06-13 9:35 ` [PATCH 1/4] ARM: pmu: refactor reservation Mark Rutland
2011-06-13 9:35 ` [PATCH 2/4] ARM: pmu: reject duplicate PMU registrations Mark Rutland
2011-06-13 9:35 ` [PATCH 3/4] ARM: pmu: add OF probing support Mark Rutland
2011-06-13 13:40 ` Rob Herring
2011-06-13 13:48 ` Mark Rutland
2011-06-13 13:55 ` Rob Herring
2011-06-13 9:35 ` [PATCH 4/4] ARM: pmu: add platform_device_id table support Mark Rutland
2011-06-13 12:33 ` Sergei Shtylyov
2011-06-13 12:41 ` Mark Rutland
2011-06-13 14:29 ` Jamie Iles
2011-06-13 16:44 ` [PATCH 1/3] ARM: pmu: add OF probing support Grant Likely
2011-06-07 14:22 ` [PATCH 2/3] ARM: gic: add OF based initialization Rob Herring
2011-06-13 16:53 ` Grant Likely
2011-06-13 21:39 ` Rob Herring
2011-06-13 22:14 ` Russell King - ARM Linux
2011-06-14 13:56 ` Grant Likely
2011-06-07 14:22 ` [PATCH 3/3] ARM: l2x0: Add " Rob Herring
2011-06-07 16:20 ` Olof Johansson
2011-06-07 16:54 ` Rob Herring [this message]
2011-06-07 18:49 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2011-06-01 16:37 [PATCH 0/3] DT bindings Cortex A9 peripherals Rob Herring
2011-06-01 16:37 ` [PATCH 3/3] ARM: l2x0: Add OF based initialization Rob Herring
2011-06-01 18:40 ` Olof Johansson
2011-06-01 19:01 ` Rob Herring
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=4DEE57D7.1030704@gmail.com \
--to=robherring2@gmail.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 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).