Skip to content

L
linux
Switch branch/tag
  1. 25 Oct, 2019 1 commit
  3. 24 Oct, 2019 2 commits
  5. 23 Oct, 2019 3 commits
  7. 21 Oct, 2019 7 commits
  9. 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
  11. 17 Oct, 2019 2 commits
  13. 16 Oct, 2019 1 commit
  15. 15 Oct, 2019 1 commit
  17. 14 Oct, 2019 8 commits
  19. 12 Oct, 2019 1 commit
  21. 11 Oct, 2019 2 commits
  23. 10 Oct, 2019 4 commits
  25. 09 Oct, 2019 2 commits
    • Tony Lindgren's avatar
      ARM: dts: Use level interrupt for omap4 & 5 wlcore · 087a2b7e
      Tony Lindgren authored 
      Commit 572cf7d7 ("ARM: dts: Improve omap l4per idling with wlcore edge
sensitive interrupt") changed wlcore interrupts to use edge interrupt based
on what's specified in the wl1835mod.pdf data sheet.

However, there are still cases where we can have lost interrupts as
described in omap_gpio_unidle(). And using a level interrupt instead of edge
interrupt helps as we avoid the check for untriggered GPIO interrupts in
omap_gpio_unidle().

And with commit e6818d29 ("gpio: gpio-omap: configure edge detection
for level IRQs for idle wakeup") GPIOs idle just fine with level interrupts.

Let's change omap4 and 5 wlcore users back to using level interrupt
instead of edge interrupt. Let's not change the others as I've only seen
this on omap4 and 5, probably because the other SoCs don't have l4per idle
independent of the CPUs.

Fixes: 572cf7d7 ("ARM: dts: Improve omap l4per idling with wlcore edge sensitive interrupt")
Depends-on: e6818d29 ("gpio: gpio-omap: configure edge detection for level IRQs for idle wakeup")
Cc: Anders Roxell <anders.roxell@linaro.org>
Cc: Eyal Reizer <eyalr@ti.com>
Cc: Guy Mishol <guym@ti.com>
Cc: John Stultz <john.stultz@linaro.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      087a2b7e
    • Marek Behún's avatar
      arm64: dts: armada-3720-turris-mox: convert usb-phy to phy-supply · 187c195a
      Marek Behún authored 
      Update Turris Mox device tree to use the phy-supply property of the
generic PHY framework instead of the legacy usb-phy property.

This is needed since it caused a regression on Turris Mox since "usb:
host: xhci-plat: Prevent an abnormally restrictive PHY init skipping".
Signed-off-by: default avatarMarek Behún <marek.behun@nic.cz>
Fixes: eb6c2eb6 ("usb: host: xhci-plat: Prevent an abnormally restrictive PHY init skipping")
Reviewed-by: default avatarMiquel Raynal <miquel.raynal@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: default avatarGregory CLEMENT <gregory.clement@bootlin.com>
      187c195a
  27. 08 Oct, 2019 1 commit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7