From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM DT cpus/cpu and topology bindings
Date: Thu, 26 Sep 2013 11:02:50 +0100 [thread overview]
Message-ID: <20130926100250.GA20705@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <5242EA2E.1010106@gmail.com>
On Wed, Sep 25, 2013 at 02:50:38PM +0100, Rob Herring wrote:
> On 09/24/2013 11:01 AM, Lorenzo Pieralisi wrote:
> > [replying to self]
> >
> > Any further comments on this series ? If not, I think bindings are ready to be
> > queued, but for that I need acks from DT maintainers.
>
> Who do you plan to take this? Is this dependent on something for 3.13?
> If not, I'll apply it.
v3 on the lists, should be final. No, there are no dependencies on 3.13
to the best of my knowledge. The problem with pre-v7 UP systems with
cpus node #address-cells == 0 is still there and I would like to ask you
please what we/I should do about that, it can trigger a considerable
amount of churn. As soon as these bindings hit the mainline I will
update the DT parsing code, I can easily take all pre-v7 UP dts out
of the picture in the parsing loop (after all, reg property for those
processors is useless), but the dts are _wrong_ regardless when these
patches become the official bindings.
Thanks !
Lorenzo
>
> Rob
>
> > The issue with in kernel dts that (re)-need patching owing to re-introduction
> > of reg property on pre-v7 UP is still pending.
> >
> > Please advise, thank you very much,
> > Lorenzo
> >
> > On Mon, Sep 16, 2013 at 12:21:02PM +0100, Lorenzo Pieralisi wrote:
> >> This is v2 of a previous posting:
> >>
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/192322.html
> >>
> >> - v2 changes
> >> - Removed single core cpu-map example
> >> - Removed OS dependency from cpus/cpu bindings
> >> - Updated Marvell compatible strings
> >> - Clarified behaviour on pre ARM v7 uniprocessor systems and updated
> >> examples
> >>
> >> This patch resumes DT topology/cpu bindings discussions for ARM that were
> >> started here:
> >>
> >> https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-April/031725.html
> >> https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-April/032450.html
> >>
> >> Comments welcome, thanks,
> >> Lorenzo
> >>
> >> Lorenzo Pieralisi (2):
> >> Documentation: devicetree: arm: cpus/cpu nodes bindings updates
> >> Documentation: DT: arm: define CPU topology bindings
> >>
> >> Documentation/devicetree/bindings/arm/cpus.txt | 391 +++++++++++++++--
> >> Documentation/devicetree/bindings/arm/topology.txt | 474 +++++++++++++++++++++
> >> 2 files changed, 818 insertions(+), 47 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/arm/topology.txt
> >>
> >> --
> >> 1.8.2.2
> >>
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
>
>
next prev parent reply other threads:[~2013-09-26 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 11:21 [PATCH v2 0/2] ARM DT cpus/cpu and topology bindings Lorenzo Pieralisi
2013-09-16 11:21 ` [PATCH v2 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates Lorenzo Pieralisi
2013-09-16 13:32 ` Jason Cooper
2013-09-16 19:28 ` Gregory CLEMENT
2013-09-25 16:12 ` Mark Rutland
2013-09-16 11:21 ` [PATCH v2 2/2] Documentation: DT: arm: define CPU topology bindings Lorenzo Pieralisi
2013-09-24 16:01 ` [PATCH v2 0/2] ARM DT cpus/cpu and " Lorenzo Pieralisi
2013-09-25 13:50 ` Rob Herring
2013-09-26 10:02 ` Lorenzo Pieralisi [this message]
2013-09-26 21:42 ` Rob Herring
2013-09-27 14:51 ` 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=20130926100250.GA20705@e102568-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.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).