1. 28 Oct, 2019 2 commits
  2. 25 Oct, 2019 1 commit
  3. 24 Oct, 2019 6 commits
  4. 23 Oct, 2019 3 commits
  5. 22 Oct, 2019 1 commit
    • Kishon Vijay Abraham I's avatar
      reset: Fix memory leak in reset_control_array_put() · 532f9cd6
      Kishon Vijay Abraham I authored
      Memory allocated for 'struct reset_control_array' in
      of_reset_control_array_get() is never freed in
      reset_control_array_put() resulting in kmemleak showing
      the following backtrace.
      
        backtrace:
          [<00000000c5f17595>] __kmalloc+0x1b0/0x2b0
          [<00000000bd499e13>] of_reset_control_array_get+0xa4/0x180
          [<000000004cc02754>] 0xffff800008c669e4
          [<0000000050a83b24>] platform_drv_probe+0x50/0xa0
          [<00000000d3a0b0bc>] really_probe+0x108/0x348
          [<000000005aa458ac>] driver_probe_device+0x58/0x100
          [<000000008853626c>] device_driver_attach+0x6c/0x90
          [<0000000085308d19>] __driver_attach+0x84/0xc8
          [<00000000080d35f2>] bus_for_each_dev+0x74/0xc8
          [<00000000dd7f015b>] driver_attach+0x20/0x28
          [<00000000923ba6e6>] bus_add_driver+0x148/0x1f0
          [<0000000061473b66>] driver_register+0x60/0x110
          [<00000000c5bec167>] __platform_driver_register+0x40/0x48
          [<000000007c764b4f>] 0xffff800008c6c020
          [<0000000047ec2e8c>] do_one_initcall+0x5c/0x1b0
          [<0000000093d4b50d>] do_init_module+0x54/0x1d0
      
      Fixes: 17c82e20 ("reset: Add APIs to manage array of resets")
      Signed-off-by: default avatarKishon Vijay Abraham I <kishon@ti.com>
      Signed-off-by: default avatarPhilipp Zabel <p.zabel@pengutronix.de>
      532f9cd6
  6. 21 Oct, 2019 7 commits
  7. 18 Oct, 2019 5 commits
    • Stefan Wahren's avatar
      ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue · 626c45d2
      Stefan Wahren authored
      bcm2835-rpi.dtsi defines the behavior of the ACT LED, which is available
      on all Raspberry Pi boards. But there is no driver for this particual
      GPIO on CM3 in mainline yet, so this node was left incomplete without
      the actual GPIO definition. Since commit 025bf377 ("gpio: Fix return
      value mismatch of function gpiod_get_from_of_node()") this causing probe
      issues of the leds-gpio driver for users of the CM3 dtsi file.
      
        leds-gpio: probe of leds failed with error -2
      
      Until we have the necessary GPIO driver hide the ACT node for CM3
      to avoid this.
      Reported-by: default avatarFredrik Yhlen <fredrik.yhlen@endian.se>
      Signed-off-by: default avatarStefan Wahren <wahrenst@gmx.net>
      Fixes: a54fe8a6 ("ARM: dts: add Raspberry Pi Compute Module 3 and IO board")
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Krzysztof Kozlowski <krzk@kernel.org>
      Signed-off-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      626c45d2
    • Tony Lindgren's avatar
      Merge branch 'watchdog-fix' into fixes · 6aed5a0e
      Tony Lindgren authored
      6aed5a0e
    • Tony Lindgren's avatar
      bus: ti-sysc: Fix watchdog quirk handling · c7d8669f
      Tony Lindgren authored
      I noticed that when probed with ti-sysc, watchdog can trigger on am3, am4
      and dra7 causing a device reset.
      
      Turns out I made several mistakes implementing the watchdog quirk handling:
      
      1. We must do both writes to spr register
      
      2. We must also call the reset quirk on disable
      
      3. On am3 and am4 we need to also set swsup quirk flag
      
      I probably only tested this earlier with watchdog service running when the
      watchdog never gets disabled.
      
      Fixes: 4e23be47 ("bus: ti-sysc: Add support for module specific reset quirks")
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      c7d8669f
    • Suman Anna's avatar
      ARM: OMAP2+: Add pdata for OMAP3 ISP IOMMU · 0af3e1a4
      Suman Anna authored
      The OMAP3 ISP IOMMU does not have any reset lines, so it didn't
      need any pdata previously. The OMAP IOMMU driver now requires the
      platform data ops for device_enable/idle on all the IOMMU devices
      after commit db8918f6 ("iommu/omap: streamline enable/disable
      through runtime pm callbacks") to enable/disable the clocks properly
      and maintain the reference count and the omap_hwmod state machine.
      So, add these callbacks through iommu pdata quirks for the OMAP3
      ISP IOMMU.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      0af3e1a4
    • Suman Anna's avatar
      ARM: OMAP2+: Plug in device_enable/idle ops for IOMMUs · 19feeee5
      Suman Anna authored
      The OMAP IOMMU driver requires the device_enable/idle platform
      data ops on all the IOMMU devices to be able to enable and disable
      the clocks after commit db8918f6 ("iommu/omap: streamline
      enable/disable through runtime pm callbacks"). Plug in these
      pdata ops for all the existing IOMMUs through pdata quirks to
      maintain functionality.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      19feeee5
  8. 17 Oct, 2019 2 commits
  9. 16 Oct, 2019 1 commit
  10. 15 Oct, 2019 1 commit
  11. 14 Oct, 2019 8 commits
  12. 12 Oct, 2019 1 commit
  13. 11 Oct, 2019 2 commits