Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 03 1月, 2017 1 次提交
  3. 04 11月, 2016 1 次提交
  5. 30 5月, 2016 1 次提交
  7. 20 4月, 2016 1 次提交
    • G
      ARM: dts: sh73a0: Correct interrupt type for ARM TWD · a4a72b47
      由 Geert Uytterhoeven 提交于 
      The ARM TWD interrupt is a private peripheral interrupt (PPI), and per
the ARM GIC documentation, whether the type for PPIs can be set is
IMPLEMENTATION DEFINED.

For SH-Mobile AG5 devices the PPI type cannot be set, and so when we
attempt to set the type for the ARM TWD interrupt it fails.  This has
gone unnoticed because it fails silently, and because we cannot
re-configure the type it has had no impact. Nevertheless fix the type
for the TWD interrupt so that it matches the hardware configuration.

Based on patches by Jon Hunter for Tegra20/30 and OMAP4.
Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      a4a72b47
  9. 28 3月, 2016 1 次提交
    • S
      ARM: dts: sh73a0: Remove unnecessary clock-output-names properties · 000025cf
      由 Simon Horman 提交于 
      * Fixed rate and fixed factor clocks do not require an
  clock-output-names property.
* Since 07705583 ("clk: shmobile: div6: Make clock-output-names
  optional") Renesas div6 clocks do not require a clock-output-names
  property.

In the above cases there is only one clock output and its name is taken
from that of the clock node.  Accordingly, remove the unnecessary
clock-output-names properties and as necessary update the node names.

The clock-output-names property is left in place for the zb_clk which is
thus treated as a special case as the MSTP clock driver (clk-mstp.c)
explicitly looks for a clock with node name zb_clk for the r8a73a4 and
sh73a0 SoCs.
Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
Acked-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      000025cf
  11. 10 2月, 2016 2 次提交
  13. 01 12月, 2015 2 次提交
  15. 25 11月, 2015 1 次提交
  17. 05 8月, 2015 1 次提交
    • G
      ARM: shmobile: sh73a0 dtsi: Add missing "gpio-ranges" to gpio node · 94bdc48d
      由 Geert Uytterhoeven 提交于 
      If a GPIO driver uses gpiochip_add_pin_range() (which is usually the
case for GPIO/PFC combos), the GPIO hogging mechanism configured from DT
doesn't work:

    requesting hog GPIO led1-high (chip sh73a0_pfc, offset 20) failed

The actual error code is -517 == -EPROBE_DEFER.

The problem is that PFC+GPIO registration is handled in multiple steps:
  1. pinctrl_register(),
  2. gpiochip_add(),
  3. gpiochip_add_pin_range().

Configuration of the hogs is handled in gpiochip_add():

    gpiochip_add
        of_gpiochip_add
            of_gpiochip_scan_hogs
                gpiod_hog
                    gpiochip_request_own_desc
                        __gpiod_request
                            chip->request
                                pinctrl_request_gpio
                                    pinctrl_get_device_gpio_range

However, at this point the GPIO controller hasn't been added to
pinctrldev_list yet, so the range can't be found, and the operation fails
with -EPROBE_DEFER.

To fix this, add a "gpio-ranges" property to the gpio device node, so
the ranges are added by of_gpiochip_add_pin_range(), which is called by
of_gpiochip_add() before the call to of_gpiochip_scan_hogs().
Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: NLinus Walleij <linus.walleij@linaro.org>
Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      94bdc48d
  19. 11 5月, 2015 1 次提交
  21. 28 4月, 2015 1 次提交
  23. 24 2月, 2015 6 次提交
  25. 15 1月, 2015 1 次提交
  27. 08 1月, 2015 1 次提交
  29. 21 12月, 2014 2 次提交
  31. 19 11月, 2014 1 次提交
  33. 09 9月, 2014 1 次提交
  35. 22 8月, 2014 2 次提交
  37. 12 7月, 2014 1 次提交
  39. 15 4月, 2014 1 次提交
  41. 19 12月, 2013 1 次提交
  43. 12 12月, 2013 1 次提交
  45. 10 12月, 2013 4 次提交
  47. 08 10月, 2013 1 次提交
  49. 22 9月, 2013 1 次提交
  51. 31 7月, 2013 1 次提交
  53. 22 7月, 2013 1 次提交
  55. 18 6月, 2013 1 次提交