From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 00/13] ARM: DT cpu bindings updates
Date: Mon, 22 Apr 2013 21:18:41 +0200 [thread overview]
Message-ID: <201304222118.41262.arnd@arndb.de> (raw)
In-Reply-To: <20130422180057.GB17071@e102568-lin.cambridge.arm.com>
On Monday 22 April 2013, Lorenzo Pieralisi wrote:
> > Thoughts? I notice Catalin has some patches queued for arm64 which
> > unconditionally use of_property_read_u64, but I have a patch to honour the
> > #address-cells property instead.
>
> Basically you want me to rule out passing a dtb with cpus node having
> #address-cells == 2 to a 32-bit kernel, correct ? Or put it another way:
>
> - a 32-bit kernel must always get passed a dtb with cpus node
> #address-cells == 1.
Why that? For other registers, we allow leading zeroes. This is
already required for MMIO registers on LPAE capable machines.
> If the system is ARMv8 with CPUs having
> MPIDR_EL1[63:32] != 0x0, well, running 32-bit kernel on it is not
> the safest thing to do anyway.
I would assume the hypervisor to provide a virtual MPIDR_EL1 for
a 32 bit kernel in that case.
Arnd
next prev parent reply other threads:[~2013-04-22 19:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 15:27 [RFC PATCH v2 00/13] ARM: DT cpu bindings updates Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 01/13] ARM: DT: kernel: move temporary cpu map stack array to static data Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 02/13] ARM: mach-mv78xx0: cpus/cpu node dts updates Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 03/13] ARM: mach-at91: " Lorenzo Pieralisi
2013-04-22 15:48 ` Nicolas Ferre
2013-04-23 13:11 ` Rob Herring
2013-04-23 13:25 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-23 13:53 ` Lorenzo Pieralisi
2013-04-23 19:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-24 9:29 ` Lorenzo Pieralisi
2013-04-24 12:45 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-22 15:27 ` [RFC PATCH v2 04/13] ARM: mach-exynos: cpus/cpu nodes " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 05/13] ARM: mach-imx: " Lorenzo Pieralisi
2013-04-23 7:34 ` Shawn Guo
2013-04-22 15:27 ` [RFC PATCH v2 06/13] ARM: mach-lpc32xx: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 07/13] ARM: mach-omap2: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 08/13] ARM: mach-picoxcell: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 09/13] ARM: mach-shmobile: " Lorenzo Pieralisi
2013-04-23 1:55 ` Simon Horman
2013-04-22 15:27 ` [RFC PATCH v2 10/13] ARM: mach-spear: " Lorenzo Pieralisi
2013-04-23 6:18 ` Viresh Kumar
2013-04-22 15:27 ` [RFC PATCH v2 11/13] ARM: mach-sunxi: " Lorenzo Pieralisi
2013-04-24 7:15 ` Maxime Ripard
2013-04-22 15:27 ` [RFC PATCH v2 12/13] ARM: mach-vt8500: " Lorenzo Pieralisi
2013-04-23 2:13 ` Tony Prisk
2013-04-23 2:20 ` Tony Prisk
2013-04-23 9:16 ` Lorenzo Pieralisi
2013-04-23 9:15 ` Lorenzo Pieralisi
2013-04-23 2:43 ` Tony Prisk
2013-04-23 9:26 ` Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 13/13] ARM: DT: kernel: DT cpu node bindings update Lorenzo Pieralisi
2013-04-23 2:46 ` Tony Prisk
2013-05-02 18:31 ` Stephen Warren
2013-05-03 9:15 ` Lorenzo Pieralisi
2013-04-22 16:41 ` [RFC PATCH v2 00/13] ARM: DT cpu bindings updates Will Deacon
2013-04-22 18:00 ` Lorenzo Pieralisi
2013-04-22 19:18 ` Arnd Bergmann [this message]
2013-04-23 9:09 ` Will Deacon
2013-04-23 9:34 ` 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=201304222118.41262.arnd@arndb.de \
--to=arnd@arndb.de \
--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).