Hi again,
On Mon, 2016-11-21 at 09:51 -0500, Tom Rini wrote:
> On Mon, Nov 21, 2016 at 02:38:30PM +, Vlad Zakharov wrote:
> >
> > Hi Tom,
> >
> > On Sat, 2016-11-19 at 19:57 +0300, Vlad Zakharov wrote:
> > >
> > > Earlier timer driver needed a clock-frequency property in compatible
> > > de
On Mon, Nov 21, 2016 at 02:38:30PM +, Vlad Zakharov wrote:
> Hi Tom,
>
> On Sat, 2016-11-19 at 19:57 +0300, Vlad Zakharov wrote:
> > Earlier timer driver needed a clock-frequency property in compatible
> > device-tree nodes. Another way is to reference a clock via a phandle.
> >
> > So now ti
Hi Tom,
On Sat, 2016-11-19 at 19:57 +0300, Vlad Zakharov wrote:
> Earlier timer driver needed a clock-frequency property in compatible
> device-tree nodes. Another way is to reference a clock via a phandle.
>
> So now timer_pre_probe tries to get clock by reference through device
> tree. In case
Earlier timer driver needed a clock-frequency property in compatible
device-tree nodes. Another way is to reference a clock via a phandle.
So now timer_pre_probe tries to get clock by reference through device
tree. In case it is impossible to get clock device through the
reference, clock-frequency
4 matches
Mail list logo