On Tue, Mar 25, 2014 at 01:38:47AM +0100, Mike Turquette wrote:
> Quoting Peter De Schrijver (2014-03-21 01:12:17)
> > On Thu, Mar 20, 2014 at 10:23:08PM +0100, Mike Turquette wrote:
> > > Quoting Tero Kristo (2014-03-05 05:10:17)
> > > > Ping.
> > > >
> > > > Mike, any feedback on this?
> > >
>
On Thu, Mar 20, 2014 at 10:23:08PM +0100, Mike Turquette wrote:
> Quoting Tero Kristo (2014-03-05 05:10:17)
> > Ping.
> >
> > Mike, any feedback on this?
>
> Hi Tero,
>
> Have you seen Sylwester's approach[1]? I prefer it since it is more
> device-oriented and less "centralized". The clock consu
On 03/20/2014 11:23 PM, Mike Turquette wrote:
Quoting Tero Kristo (2014-03-05 05:10:17)
Ping.
Mike, any feedback on this?
Hi Tero,
Have you seen Sylwester's approach[1]? I prefer it since it is more
device-oriented and less "centralized". The clock consumer enumerates
the default parent or r
Quoting Tero Kristo (2014-03-05 05:10:17)
> Ping.
>
> Mike, any feedback on this?
Hi Tero,
Have you seen Sylwester's approach[1]? I prefer it since it is more
device-oriented and less "centralized". The clock consumer enumerates
the default parent or rate of a consumed clock. This can be made to
Ping.
Mike, any feedback on this?
-Tero
On 02/13/2014 11:00 AM, Tero Kristo wrote:
Hi,
This set is a mix-match of new DT properties for generic and TI specific
clock drivers. Basically provided for commenting purposes. The patches
provide a way to configure clock parents / rates during boot t
