1. 14 11月, 2018 2 次提交
  2. 26 6月, 2018 2 次提交
  3. 04 5月, 2018 1 次提交
    • M
      ARM: dts: exynos/s3c: Remove leading 0x and 0s from bindings notation · edef4285
      Mathieu Malaterre 提交于
      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 arch/arm/boot/dts -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" {} +
      
      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 also 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: NDavid Daney <ddaney@caviumnetworks.com>
      Suggested-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NMathieu Malaterre <malat@debian.org>
      [krzk: Rerun the command to include few more changes, adjust the commit msg]
      Signed-off-by: NKrzysztof Kozlowski <krzk@kernel.org>
      edef4285
  4. 22 4月, 2018 1 次提交
  5. 17 4月, 2018 1 次提交
  6. 15 3月, 2018 1 次提交
  7. 12 3月, 2018 2 次提交
  8. 06 3月, 2018 1 次提交
  9. 14 2月, 2018 1 次提交
  10. 04 1月, 2018 1 次提交
  11. 19 12月, 2017 1 次提交
  12. 15 12月, 2017 1 次提交
  13. 12 12月, 2017 1 次提交
  14. 10 12月, 2017 3 次提交
  15. 05 12月, 2017 1 次提交
  16. 28 11月, 2017 1 次提交
  17. 20 10月, 2017 1 次提交
  18. 20 9月, 2017 3 次提交
  19. 08 6月, 2017 1 次提交
  20. 02 6月, 2017 1 次提交
  21. 01 2月, 2017 1 次提交
  22. 29 12月, 2016 1 次提交
  23. 04 11月, 2016 2 次提交
  24. 31 5月, 2016 2 次提交
  25. 13 4月, 2016 1 次提交
    • K
      ARM: dts: exynos: Fix DTC unit name warnings in Exynos5250 · 5c9cbade
      Krzysztof Kozlowski 提交于
      Fix following DTC warnings in all Exynos5250 boards:
      
      Warning (unit_address_vs_reg): Node /dp-controller@145B0000/display-timings/timing@0 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /usb@12000000 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /usb@12000000/dwc3 has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /hdmi has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /mixer has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /video-phy@10040720 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /fixed-regulator@0 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /fixed-regulator@1 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /fixed-regulator@2 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /i2c@12C70000/trackpad has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /i2c@12CD0000/lvds-bridge@20/ports/port@0 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /i2c@12CD0000/lvds-bridge@20/ports/port@1 has a unit name, but no reg property
      Warning (unit_address_vs_reg): Node /i2c-arbitrator/i2c@0/embedded-controller has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /i2c-arbitrator/i2c@0/power-regulator has a reg or ranges property, but no unit name
      Warning (unit_address_vs_reg): Node /i2c@12CA0000/embedded-controller has a reg or ranges property, but no unit name
      Signed-off-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      Reviewed-by: NJavier Martinez Canillas <javier@osg.samsung.com>
      5c9cbade
  26. 13 3月, 2016 1 次提交
  27. 25 1月, 2016 1 次提交
  28. 29 12月, 2015 1 次提交
  29. 24 10月, 2015 1 次提交
  30. 14 8月, 2015 1 次提交
  31. 21 7月, 2015 1 次提交
    • J
      ARM: dts: Include exynos5250-pinctrl after the nodes were defined for exynos5250 · dc561797
      Javier Martinez Canillas 提交于
      The dtc compiler combines all the defined nodes that have the same path
      so a device node definition can be in one file and later be extended in
      another one.
      
      That's the case of the Exynos5250 pinctrl device nodes that are defined
      in the exynos5250.dtsi file and extended in exynos5250-pinctrl.dtsi.
      
      But since the exynos5250.dtsi file includes the exynos5250-pinctrl.dtsi
      before the pinctrl device nodes are actually defined, the definition of
      the pinctrl device nodes happens in exynos5250-pinctrl.dtsi and are
      extended in exynos5250.dtsi.
      
      That is the opposite of the original intention so even when there is no
      difference in practice, the exynos5250-pinctrl.dtsi include should be
      moved at the end of the exynos5250.dtsi file after the pinctrl device
      nodes have been already defined.
      
      This will also allow to later change the exynos5250-pinctrl.dtsi file
      to use labels instead of full paths to extend the pinctrl nodes. Since
      keeping the include at the top, would cause a dtc build error due the
      pinctrl labels not being defined yet.
      Signed-off-by: NJavier Martinez Canillas <javier@osg.samsung.com>
      Signed-off-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      Signed-off-by: NKukjin Kim <kgene@kernel.org>
      dc561797