summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-02-15 13:38:20 +0100
committerArnd Bergmann <arnd@arndb.de>2019-02-15 13:38:20 +0100
commit2ed5c2e3f27b5c934bdc50734f2496e823f22876 (patch)
tree323bd249768e8b8b31ed457e2b100638ad9e6ff2 /README
parentd13937116f1e82bf508a6325111b322c30c85eb9 (diff)
parentdc30e70391376ba3987aeb856ae6d9c0706534f1 (diff)
Merge tag 'omap-for-v5.0/fixes-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
SoC fixes for omaps for v5.0-rc cycle This series contains two SoC regression fixes and one uninitialized variable fix: - Fix inverted nirq pin handling for omap5 that started producing warnings with earlier GIC direction checks and took a while to understand and confirm. Basically there are two sys_nirq pins that are bypassing peripheral modules and inverted automatically by the SoC and need to be handled with a custom irq_set_type() - Recent ti-sysc changes caused a regression to the pwm-omap-dmtimer code where the device tree handling code for timer source clock gets confused. It looks like we can remove that code eventually, but for now we just drop a bogus pm_runtime_irq_safe() for the timers with the related quirks caused by pm_runtime_irq_safe(), and have the standard assigned-clocks and assigned-clock-parents deal with setting the source clock - Fix potentially uninitialized value for display init code if regmap_read() fails * tag 'omap-for-v5.0/fixes-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap: ARM: OMAP2+: Variable "reg" in function omap4_dsi_mux_pads() could be uninitialized ARM: dts: Configure clock parent for pwm vibra bus: ti-sysc: Fix timer handling with drop pm_runtime_irq_safe() ARM: OMAP5+: Fix inverted nirq pin interrupts with irq_set_type clocksource: timer-ti-dm: Fix pwm dmtimer usage of fck reparenting
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions