This only contains clksel tables that were used with the legacy clock data.
Now that legacy clock data is completely gone, this file can be removed
also.
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/Makefile|2 +-
arch/arm/mach-omap2/clock.h | 14
arch/ar
clkdm_control is used to determine, whether clocks should trigger a
clockdomain transition when they are enabled/disabled. Keep this
functionality intact, but replace this with a clk_features flag
which can be initialized during boot if needed.
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/
Clock driver requires access to certain clockdomain handling ops once
the code is being moved over under clock driver. Example of this is
clk_enable / clk_disable under omap3 DPLL code. The required clkdm
APIs are now exported through the ti_clk_ll_ops struct.
Signed-off-by: Tero Kristo
---
arch
We should avoid exporting data from drivers, instead use an API for
registering the clock low level operations.
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/clock.c | 17 +
arch/arm/mach-omap2/clock.h |1 +
arch/arm/mach-omap2/io.c |2 ++
drivers/clk/ti/clk.
Cleanup the mess in clock.h by removing all definitions that are no longer
used for anything.
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/clkt34xx_dpll3m2.c |1 -
arch/arm/mach-omap2/clock.h| 124
arch/arm/mach-omap2/clock34xx.h|
Hi Geert,
On 11/05/15 13:50, Geert Uytterhoeven wrote:
On Wed, Apr 15, 2015 at 10:14 AM, Roger Quadros wrote:
Without this system suspend is broken on systems that have
drivers calling enable/disable_irq_wake() for interrupts based off
the dummy irq hook.
Good to see this was applied. Still,
HI,
On Mon, May 11, 2015 at 11:46:13AM -0500, Nishanth Menon wrote:
> On Mon, May 11, 2015 at 10:19 AM, Felipe Balbi wrote:
> >
> >> in my opinion, doing a temporary hack in upstream kernel is not an
> >> elegant approach. I suggest helping review and approving Viresh's new
> >
> > however this i
Hi,
* Dave Gerlach [150401 12:38]:
> Add the device tree bindings document for the TI Wakeup M3 remote
> processor devices on AM33xx and AM43xx SoCs. These devices are used
> to offload low-level power management functionality, and are handled
> by the wkup_m3 remoteproc driver.
>
> Signed-off-b