[PATCH] clk: ti: drop locking code from mux/divider drivers

TI's mux and divider clock drivers do not require locking and they do not initialize internal spinlocks. This code was occasionally copy-posted from generic mux/divider drivers. So remove it. Cc: Tony Lindgren Cc: Sekhar Nori Signed-off-by: Grygorii Strashko

[PATCH 1/4] ARM: OMAP: dmtimer: check for fixed timers during config

The omap_dm_timer_set_source() function provides a means for client users to configure the mux parent for a GPTimer's functional clock. However, not all timers are configurable (Eg: Timer12 on DRA7 is fed by an internal 32k oscillator clock, and does not have configurable parent clocks). So, check

[PATCH 0/4] DRA7 Timer12 Support

Hi Tony, The DRA7 Timer12 is completely missing from the kernel. This series adds the support for it, so that all the Timers on DRA7 are represented in the kernel. Timer12 is a special Timer, and is not available for kernel on HS devices, very much similar to the equivalent timer on OMAP3.

[PATCH 2/4] ARM: OMAP2+: timer: Remove secure timer for DRA7xx devices

Timer 12 on DRA7 SoCs is reserved for secure usage on high-secure (HS) devices. The timer cannot be used by the kernel on HS devices, but is available on regular general purpose (GP) devices. This is similar to the behavior on OMAP3 devices, so extend the logic used in commit ad24bde8f102 ("ARM:

[PATCH 4/4] ARM: DRA7: hwmod: Add data for GPTimer 12

Add the hwmod data for GPTimer 12. GPTimer 12 is present in WKUPAON power domain and is clocked from a secure 32K clock. GPTimer 12 serves as a secure timer on HS devices, but is available for kernel on regular GP devices. The hwmod link is registered only on GP devices. The hwmod data also

[PATCH 3/4] ARM: dts: DRA7: Add timer12 node

Add the DT node for Timer12 present on DRA7 family of SoCs. Timer12 is present in PD_WKUPAON power domain, and has the same capabilities as the other timers, except for the fact that it serves as a secure timer on HS devices and is clocked only from the secure 32K clock. The node is marked

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

On Tue, Sep 29, 2015 at 1:44 PM, Felipe Balbi wrote: > Introduce a new clocksource driver for Texas > Instruments 32.768 Hz device which is available > on most OMAP-like devices. > > Signed-off-by: Felipe Balbi > --- > drivers/clocksource/Kconfig| 8 +++ >

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

Hi Felipe, On 09/29/2015 10:44 PM, Felipe Balbi wrote: Introduce a new clocksource driver for Texas Instruments 32.768 Hz device which is available on most OMAP-like devices. Signed-off-by: Felipe Balbi --- [ ... ] +config CLKSRC_TI_32K + bool "Texas Instruments

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

On Thu, Oct 01, 2015 at 03:20:18PM -0700, John Stultz wrote: > On Tue, Sep 29, 2015 at 1:44 PM, Felipe Balbi wrote: > > Introduce a new clocksource driver for Texas > > Instruments 32.768 Hz device which is available > > on most OMAP-like devices. > > > > Signed-off-by: Felipe Balbi

Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

On Tue, Sep 29, 2015 at 1:44 PM, Felipe Balbi wrote: > Introduce a new clocksource driver for Texas > Instruments 32.768 Hz device which is available > on most OMAP-like devices. > > Signed-off-by: Felipe Balbi > --- > drivers/clocksource/Kconfig| 8 +++ >

Re: [PATCH 10/13] twl4030_charger: add software controlled linear charging mode.

Pavel Machek writes: > On Thu 2015-07-30 10:11:24, NeilBrown wrote: >> >> Add a 'continuous' option for usb charging which enables >> the "linear" charging mode of the twl4030. >> >> Linear charging does a good job with not-so-reliable power sources. >> Auto mode does not work

Re: [PATCH v2] clk: ti: fix dual-registration of uart4_ick

On 09/29, Ben Dooks wrote: > On the OMAP AM3517 platform the uart4_ick gets registered > twice, causing any power managment to /dev/ttyO3 to fail > when trying to wake the device up. > > This solves the following oops: > > [] Unhandled fault: external abort on non-linefetch (0x1028) at

Queueing b0a688ddcc50 "usb: musb: cppi41: allow it to work again" for -stable

Hello, Commit b0a688ddcc50 "usb: musb: cppi41: allow it to work again" seems to fix a regression. It applies cleanly on v4.1 and removes the "musb-hdrc musb-hdrc.1.auto: Need DT for the DMA engine." error. Any chance you can queue it for -stable? Thanks! -- Ezequiel García, VanguardiaSur