On 12/15/2017 01:46 PM, Mathieu Malaterre wrote:
Improve the DTS files by removing all the leading "0x" and zeros to fix the
following dtc warnings:

Warning (unit_address_format): Node /XXX unit name should not have leading "0x"


Warning (unit_address_format): Node /XXX unit name should not have leading 0s

Converted using the following command:

find . -type f \( -iname *.dts -o -iname *.dtsi \) -exec sed -i -e "s/@\([0-9a-fA-FxX\.;:#]+\)\s*{/@\L\1 
{/g" -e "s/@0x\(.*\) {/@\1 {/g" -e "s/@0+\(.*\) {/@\1 {/g" {} +^C

For simplicity, two sed expressions were used to solve each warnings separately.

To make the regex expression more robust a few other issues were resolved,
namely setting unit-address to lower case, and adding a whitespace before the
the opening curly brace:


This will solve as a side effect warning:

Warning (simple_bus_reg): Node /XXX@<UPPER> simple-bus unit address format error, expected 

This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from 
bindings notation")

Reported-by: David Daney <dda...@caviumnetworks.com>
Suggested-by: Rob Herring <r...@kernel.org>
Signed-off-by: Mathieu Malaterre <ma...@debian.org>

Applied on stm32-next.



  arch/arm/boot/dts/stm32h743.dtsi | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/arm/boot/dts/stm32h743.dtsi
index bbfcbaca0b36..a559d8b6a4a3 100644
--- a/arch/arm/boot/dts/stm32h743.dtsi
+++ b/arch/arm/boot/dts/stm32h743.dtsi
@@ -304,7 +304,7 @@
- vrefbuf: regulator@58003C00 {
+               vrefbuf: regulator@58003c00 {
                        compatible = "st,stm32-vrefbuf";
                        reg = <0x58003C00 0x8>;
                        clocks = <&rcc VREF_CK>;

Reply via email to