From mboxrd@z Thu Jan 1 00:00:00 1970 From: sudeep.holla@arm.com (Sudeep Holla) Date: Thu, 23 Aug 2018 16:31:10 +0100 Subject: [PATCH] arm64: dts: Fix various entry-method properties to reflect documentation In-Reply-To: <113f28acbc55f64762c9f0bcefe076a811f2ed82.1535014078.git.amit.kucheria@linaro.org> References: <113f28acbc55f64762c9f0bcefe076a811f2ed82.1535014078.git.amit.kucheria@linaro.org> Message-ID: <20180823153110.GA19131@e107155-lin> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Amit, Thanks for fixing this. On Thu, Aug 23, 2018 at 02:23:29PM +0530, Amit Kucheria wrote: > The idle-states binding documentation[1] mentions that the > 'entry-method' property is required on 64-bit platforms and must be > set to "psci". > > commit a13f18f59d26 ("Documentation: arm: Fix typo in the idle-states > bindings examples") attempted to fix this earlier but clearly more is > needed. > In fact, I assumed I fixed things with commit 978fa436231a ("drivers: firmware: psci: unify enable-method binding on ARM {64,32}-bit systems"), but I was wrong. I left quite a few instances including juno dtbs. > Fix the cpu-capacity.txt documentation that uses the incorrect value so > we don't get copy-paste errors like these. Clarify the language in > idle-states.txt by removing the reference to the psci bindings that > might be causing this confusion. > > Finally, fix devicetrees of various boards to reflect current > documentation. > > [1] Documentation/devicetree/bindings/arm/idle-states.txt (see > idle-states node) > > Signed-off-by: Amit Kucheria > --- > Documentation/devicetree/bindings/arm/cpu-capacity.txt | 2 +- > Documentation/devicetree/bindings/arm/idle-states.txt | 4 ++-- > arch/arm64/boot/dts/arm/juno-r1.dts | 2 +- > arch/arm64/boot/dts/arm/juno-r2.dts | 2 +- > arch/arm64/boot/dts/arm/juno.dts | 2 +- For all the above files, Acked-by: Sudeep Holla How do you plan to merge ? I prefer if you can send it via arm-soc as fixes for this cycle with all the necessary acks. Otherwise you may have to split this to send via platform maintainers which is bit mundane. -- Regards, Sudeep