1. 06 Jan, 2018 1 commit
  2. 05 Jan, 2018 2 commits
    • Mathieu Malaterre's avatar
      ARM: dts: da850-lcdk: Remove leading 0x and 0s from unit address · 7669b122
      Mathieu Malaterre authored
      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"
      
      and
      
      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:
      
      https://elinux.org/Device_Tree_Linux#Linux_conventions
      
      This will solve as a side effect warning:
      
      Warning (simple_bus_reg): Node /XXX@<UPPER> simple-bus unit address format error, expected "<lower>"
      
      This is a follow up to commit 4c9847b7
      
       ("dt-bindings: Remove leading 0x from bindings notation")
      Reported-by: default avatarDavid Daney <ddaney@caviumnetworks.com>
      Suggested-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarMathieu Malaterre <malat@debian.org>
      Signed-off-by: default avatarSekhar Nori <nsekhar@ti.com>
      7669b122
    • Thomas Petazzoni's avatar
      ARM: dts: kirkwood: fix pin-muxing of MPP7 on OpenBlocks A7 · 56aeb07c
      Thomas Petazzoni authored
      MPP7 is currently muxed as "gpio", but this function doesn't exist for
      MPP7, only "gpo" is available. This causes the following error:
      
      kirkwood-pinctrl f1010000.pin-controller: unsupported function gpio on pin mpp7
      pinctrl core: failed to register map default (6): invalid type given
      kirkwood-pinctrl f1010000.pin-controller: error claiming hogs: -22
      kirkwood-pinctrl f1010000.pin-controller: could not claim hogs: -22
      kirkwood-pinctrl f1010000.pin-controller: unable to register pinctrl driver
      kirkwood-pinctrl: probe of f1010000.pin-controller failed with error -22
      
      So the pinctrl driver is not probed, all device drivers (including the
      UART driver) do a -EPROBE_DEFER, and therefore the system doesn't
      really boot (well, it boots, but with no UART, and no devices that
      require pin-muxing).
      
      Back when the Device Tree file for this board was introduced, the
      definition was already wrong. The pinctrl driver also always described
      as "gpo" this function for MPP7. However, between Linux 4.10 and 4.11,
      a hog pin failing to be muxed was turned from a simple warning to a
      hard error that caused the entire pinctrl driver probe to bail
      out. This is probably the result of commit 61187142 ("pinctrl:
      core: Fix pinctrl_register_and_init() with pinctrl_enable()").
      
      This commit fixes the Device Tree to use the proper "gpo" function for
      MPP7, which fixes the boot of OpenBlocks A7, which was broken since
      Linux 4.11.
      
      Fixes: f24b56cb
      
       ("ARM: kirkwood: add support for OpenBlocks A7 platform")
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Reviewed-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarGregory CLEMENT <gregory.clement@free-electrons.com>
      56aeb07c
  3. 22 Dec, 2017 2 commits
    • Arnd Bergmann's avatar
      ARM: dts: tango4: remove bogus interrupt-controller property · fbd90b4c
      Arnd Bergmann authored
      
      
      dtc points out that the parent node of the interrupt controllers is not
      actually an interrupt controller itself, and lacks an #interrupt-cells
      property:
      
      arch/arm/boot/dts/tango4-vantage-1172.dtb: Warning (interrupts_property): Missing #interrupt-cells in interrupt-parent /soc/interrupt-controller@6e000
      
      This removes the annotation.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      fbd90b4c
    • Arnd Bergmann's avatar
      ARM: dts: ls1021a: fix incorrect clock references · 506e8a91
      Arnd Bergmann authored
      
      
      dtc warns about two 'clocks' properties that have an extraneous '1'
      at the end:
      
      arch/arm/boot/dts/ls1021a-qds.dtb: Warning (clocks_property): arch/arm/boot/dts/ls1021a-twr.dtb: Warning (clocks_property): Property 'clocks', cell 1 is not a phandle reference in /soc/i2c@2180000/mux@77/i2c@4/sgtl5000@2a
      arch/arm/boot/dts/ls1021a-qds.dtb: Warning (clocks_property): Missing property '#clock-cells' in node /soc/interrupt-controller@1400000 or bad phandle (referred from /soc/i2c@2180000/mux@77/i2c@4/sgtl5000@2a:clocks[1])
      Property 'clocks', cell 1 is not a phandle reference in /soc/i2c@2190000/sgtl5000@a
      arch/arm/boot/dts/ls1021a-twr.dtb: Warning (clocks_property): Missing property '#clock-cells' in node /soc/interrupt-controller@1400000 or bad phandle (referred from /soc/i2c@2190000/sgtl5000@a:clocks[1])
      
      The clocks that get referenced here are fixed-rate, so they do not
      take any argument, and dtc interprets the next cell as a phandle, which
      is invalid.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      506e8a91
  4. 21 Dec, 2017 2 commits
  5. 19 Dec, 2017 1 commit
  6. 13 Dec, 2017 1 commit
  7. 07 Dec, 2017 2 commits
  8. 05 Dec, 2017 3 commits
  9. 04 Dec, 2017 2 commits
  10. 03 Dec, 2017 1 commit
  11. 02 Dec, 2017 1 commit
  12. 30 Nov, 2017 2 commits
  13. 29 Nov, 2017 2 commits
  14. 28 Nov, 2017 5 commits
  15. 27 Nov, 2017 2 commits
  16. 20 Nov, 2017 1 commit
    • Arnd Bergmann's avatar
      ARM: dts: r8a779x: Add '#reset-cells' in cpg-mssr · 098f5305
      Arnd Bergmann authored
      
      
      With the latest dtc, we get many warnings about the missing
      '#reset-cells' property in these controllers, e.g.:
      
      arch/arm/boot/dts/r8a7790-lager.dtb: Warning (resets_property): Missing property '#reset-cells' in node /clock-controller@e6150000 or bad phandle (referred from /can@e6e80000:resets[0])
      arch/arm/boot/dts/r8a7792-blanche.dtb: Warning (resets_property): Missing property '#reset-cells' in node /soc/clock-controller@e6150000 or bad phandle (referred from /soc/dma-controller@e6700000:resets[0])
      arch/arm/boot/dts/r8a7792-wheat.dtb: Warning (resets_property): Missing property '#reset-cells' in node /soc/clock-controller@e6150000 or bad phandle (referred from /soc/ethernet@e6800000:resets[0])
      arch/arm/boot/dts/r8a7793-gose.dtb: Warning (resets_property): Missing property '#reset-cells' in node /clock-controller@e6150000 or bad phandle (referred from /gpio@e6050000:resets[0])
      arch/arm/boot/dts/r8a7794-alt.dtb: Warning (resets_property): Missing property '#reset-cells' in node /clock-controller@e6150000 or bad phandle (referred from /i2c@e6500000:resets[0])
      arch/arm/boot/dts/r8a7794-silk.dtb: Warning (resets_property): Missing property '#reset-cells' in node /clock-controller@e6150000 or bad phandle (referred from /interrupt-controller@e61c0000:resets[0])
      
      This adds it for the three r8a779x chips that were lacking it. The
      binding mandates this as <1>, so this is the value I use.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      [geert: Add fix for r8a7793.dtsi]
      Fixes: 34fbd2b1 ("ARM: dts: r8a7790: Add reset control properties")
      Fixes: 6e11a322 ("ARM: dts: r8a7792: Add reset control properties")
      Fixes: 84fb19e1 ("ARM: dts: r8a7793: Add reset control properties")
      Fixes: 615beb75
      
       ("ARM: dts: r8a7794: Add reset control properties")
      Signed-off-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
      098f5305
  17. 15 Nov, 2017 1 commit
  18. 10 Nov, 2017 3 commits
  19. 09 Nov, 2017 1 commit
    • Masahiro Yamada's avatar
      kbuild: handle dtb-y and CONFIG_OF_ALL_DTBS natively in Makefile.lib · 7e7962dd
      Masahiro Yamada authored
      
      
      If CONFIG_OF_ALL_DTBS is enabled, "make ARCH=arm64 dtbs" compiles each
      DTB twice; one from arch/arm64/boot/dts/*/Makefile and the other from
      the dtb-$(CONFIG_OF_ALL_DTBS) line in arch/arm64/boot/dts/Makefile.
      It could be a race problem when building DTBS in parallel.
      
      Another minor issue is CONFIG_OF_ALL_DTBS covers only *.dts in vendor
      sub-directories, so this broke when Broadcom added one more hierarchy
      in arch/arm64/boot/dts/broadcom/<soc>/.
      
      One idea to fix the issues in a clean way is to move DTB handling
      to Kbuild core scripts.  Makefile.dtbinst already recognizes dtb-y
      natively, so it should not hurt to do so.
      
      Add $(dtb-y) to extra-y, and $(dtb-) as well if CONFIG_OF_ALL_DTBS is
      enabled.  All clutter things in Makefiles go away.
      
      As a bonus clean-up, I also removed dts-dirs.  Just use subdir-y
      directly to traverse sub-directories.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      [robh: corrected BUILTIN_DTB to CONFIG_BUILTIN_DTB]
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      7e7962dd
  20. 08 Nov, 2017 1 commit
  21. 04 Nov, 2017 3 commits
  22. 02 Nov, 2017 1 commit