diff for duplicates of <20130411181710.GC2239@linaro.org> diff --git a/a/1.txt b/N1/1.txt index 253aa13..737797a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -22,7 +22,7 @@ On Thu, Apr 11, 2013 at 12:55:20PM -0500, Rob Herring wrote: > >>> + The cluster node name must be "clusterN" as described in 2.1 above. > >>> + A cluster node can not be a leaf node. > >> -> >> Follow standard conventions with "cluster at N" and a reg property with the +> >> Follow standard conventions with "cluster@N" and a reg property with the > >> number. > > > > We are defining the topology to decouple the cluster/core/thread concept @@ -41,15 +41,15 @@ specify what a cluster is at all). However, we could require a platform or SoC binding to specify the -enumeration and it how it maps to the actual hardware -- i.e., cluster at 1 -on Tuesday should be the same physical cluster as cluster at 1 on Monday, -to the extent that cluster at 1 is present in the DT on both days and the -hardware hasn't been physically modified (i.e., cluster at 1 might refer +enumeration and it how it maps to the actual hardware -- i.e., cluster@1 +on Tuesday should be the same physical cluster as cluster@1 on Monday, +to the extent that cluster@1 is present in the DT on both days and the +hardware hasn't been physically modified (i.e., cluster@1 might refer to a fixed physical socket on a hypothetical board with physically pluggable CPU modules). -Correspondingly, on TC2, cluster at 0 would always be the A15 cluster; -cluster at 1 would always be the A7 cluster. But if the firmware disables +Correspondingly, on TC2, cluster@0 would always be the A15 cluster; +cluster@1 would always be the A7 cluster. But if the firmware disables one of them, that cluster and the relevant CPU nodes should be removed from the DT before passing it to the kernel. diff --git a/a/content_digest b/N1/content_digest index f6aa4d7..da120e8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,10 +3,16 @@ "ref\05166D01F.5070404@gmail.com\0" "ref\020130411155054.GA29509@e102568-lin.cambridge.arm.com\0" "ref\05166F908.9050503@gmail.com\0" - "From\0dave.martin@linaro.org (Dave Martin)\0" - "Subject\0[RFC PATCH 01/11] Documentation: DT: arm: define CPU topology bindings\0" + "From\0Dave Martin <dave.martin@linaro.org>\0" + "Subject\0Re: [RFC PATCH 01/11] Documentation: DT: arm: define CPU topology bindings\0" "Date\0Thu, 11 Apr 2013 19:17:10 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Rob Herring <robherring2@gmail.com>\0" + "Cc\0Mark Rutland <Mark.Rutland@arm.com>" + Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> + devicetree-discuss@lists.ozlabs.org <devicetree-discuss@lists.ozlabs.org> + Will Deacon <Will.Deacon@arm.com> + Rob Herring <rob.herring@calxeda.com> + " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0" "\00:1\0" "b\0" "On Thu, Apr 11, 2013 at 12:55:20PM -0500, Rob Herring wrote:\n" @@ -33,7 +39,7 @@ "> >>> +\tThe cluster node name must be \"clusterN\" as described in 2.1 above.\n" "> >>> +\tA cluster node can not be a leaf node.\n" "> >>\n" - "> >> Follow standard conventions with \"cluster at N\" and a reg property with the\n" + "> >> Follow standard conventions with \"cluster@N\" and a reg property with the\n" "> >> number.\n" "> > \n" "> > We are defining the topology to decouple the cluster/core/thread concept\n" @@ -52,15 +58,15 @@ "\n" "\n" "However, we could require a platform or SoC binding to specify the\n" - "enumeration and it how it maps to the actual hardware -- i.e., cluster at 1\n" - "on Tuesday should be the same physical cluster as cluster at 1 on Monday,\n" - "to the extent that cluster at 1 is present in the DT on both days and the\n" - "hardware hasn't been physically modified (i.e., cluster at 1 might refer\n" + "enumeration and it how it maps to the actual hardware -- i.e., cluster@1\n" + "on Tuesday should be the same physical cluster as cluster@1 on Monday,\n" + "to the extent that cluster@1 is present in the DT on both days and the\n" + "hardware hasn't been physically modified (i.e., cluster@1 might refer\n" "to a fixed physical socket on a hypothetical board with physically\n" "pluggable CPU modules).\n" "\n" - "Correspondingly, on TC2, cluster at 0 would always be the A15 cluster;\n" - "cluster at 1 would always be the A7 cluster. But if the firmware disables\n" + "Correspondingly, on TC2, cluster@0 would always be the A15 cluster;\n" + "cluster@1 would always be the A7 cluster. But if the firmware disables\n" "one of them, that cluster and the relevant CPU nodes should be removed\n" "from the DT before passing it to the kernel.\n" "\n" @@ -70,4 +76,4 @@ "Cheers\n" ---Dave -f123ca3a052395873fed95954790e0c76a410212dd522b98adb54c6ae48cb72b +e5fb1516aaad94dc8f57a928bcafd89e4e5af81b2af1b082fdba1a22d9793d0b
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.