lkml.org 
[lkml]   [2012]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC PATCH] clk: add extension API
> > > on Tegra:
> > >
> > > device_reset(dev)
> > > -> dev_pm_domain->reset()
> > > -> tegra_periph_reset()
> > >
> >
> > These methods are also needed internally by the powergating code.
>
> so ? Just call them when you need...
>

the powergating code calls assert and deassert indepedently
ie:

tegra_periph_reset_assert()

do stuff

tegra_periph_reset_assert()

> > > on OMAP:
> > >
> > > device_reset(dev)
> > > -> dev_pm_domain->reset()
> > > -> omap_hwmod_reset()
> > >
> > >
> > > btw:
> > >
> > > tegra_periph_reset(....)
> > > {
> > > tegra_periph_reset_assert(...);
> > > udelay(2);
> > > tegra_periph_reset_deassert(...);
> > > }
> >
> > which uses the clockframework currently.
>
> no problems there. The point is that you already know which clock feed
> into which device, so if you have a device-based API for device
> soft-reset, you can figure out which exact clock to toggle, right ?

you have the struct clk, you could dive into that and grab clk_hw and call
some function directly. But sounds quite horrible to me.

Cheers,

Peter.


\
 
 \ /
  Last update: 2012-05-31 12:21    [from the cache]
©2003-2011 Jasper Spaans