Re: [PATCH v5 2/3] clocksource: keystone: add bindings for keystonetimer

[Ivan Khoronzhuk]

On 02/06/2014 01:36 AM, Rob Herring wrote:
> On Wed, Feb 5, 2014 at 12:52 PM, Ivan Khoronzhuk <ivan.khoronzhuk@xxxxxx> wrote:
> > On 02/05/2014 07:41 PM, Rob Herring wrote:
> > > On Wed, Feb 5, 2014 at 10:18 AM, Ivan Khoronzhuk <ivan.khoronzhuk@xxxxxx>
> > > wrote:
> > > > On 02/05/2014 04:39 PM, Rob Herring wrote:
> > > > > On Wed, Feb 5, 2014 at 7:47 AM, Ivan Khoronzhuk <ivan.khoronzhuk@xxxxxx>
> > > > > wrote:
> > > > > > This patch provides bindings for the 64-bit timer in the KeyStone
> > > > > > architecture devices. The timer can be configured as a general-purpose
> > > > > > 64-bit
> > > > > > timer, dual general-purpose 32-bit timers. When configured as dual
> > > > > > 32-bit
> > > > > > timers, each half can operate in conjunction (chain mode) or
> > > > > > independently
> > > > > > (unchained mode) of each other.
> > > > > This is software configurable or h/w design time configurations?
> > > > >
> > > > > Rob
> > > > This is h/w design time configurations
> > > Then it seems like the binding should provide for describing those
> > > differences either with a property or different compatible strings.
> > >
> > > Rob
> > Oh..sorry, seems I didn't catch, this is configurable by software.
> > These configurations are like modes in which timer can work
> > and they are not different hardware IPs. It depends on driver in
> > which mode it should work.
> In that case,
>
> Acked-by: Rob Herring <robh@xxxxxxxxxx>

Thanks

--
Regards,
Ivan Khoronzhuk

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/