ix.de
>Subject: Re: [PATCH v3] clocksource: add MVF600 pit timer support
>
>On Mon, May 20, 2013 at 03:08:54AM +, Lu Jingchang-B35083 wrote:
>> [Lu Jingchang-B35083]
>> I am not sure MVF5xx and MVF7xx have the same PIT block, if you have
>information that it is the same on
On Mon, May 20, 2013 at 03:08:54AM +, Lu Jingchang-B35083 wrote:
> [Lu Jingchang-B35083]
> I am not sure MVF5xx and MVF7xx have the same PIT block, if you have
> information that it is the same on other Vybrid SoCs, it is ok to change the
> driver name to mvf. Thanks!
Even the PIT block o
ix.de
>Subject: Re: [PATCH v3] clocksource: add MVF600 pit timer support
>
>On Thu, May 16, 2013 at 02:15:24PM +0800, Jingchang Lu wrote:
>> Add Freescale Vybrid MVF600 period interrupt timer support.
>>
>> Signed-off-by: Jingchang Lu
>> ---
>> v3:
>&g
On Thu, May 16, 2013 at 02:15:24PM +0800, Jingchang Lu wrote:
> Add Freescale Vybrid MVF600 period interrupt timer support.
>
> Signed-off-by: Jingchang Lu
> ---
> v3:
> move the pit driver to drivers/clocksource.
>
> drivers/clocksource/Kconfig| 5 +
> drivers/clocksource/Makef
tronix.de
>Subject: Re: [PATCH v3] clocksource: add MVF600 pit timer support
>
>> +static int pit_set_next_event(unsigned long delta,
>> +struct clock_event_device *unused) {
>> +pit_timer_disable();
>> +__raw_writel(delta - 1, clke
On Thu, 16 May 2013, Jingchang Lu wrote:
> +/*
> + * 8 timers: pit0 - pit7,
> + * Each takes 0x10 Bytes register sapce
> + */
> +#define PITMCR 0x00
> +#define PIT0_OFFSET 0x100
> +#define PITn_OFFSET(n) (PIT0_OFFSET + 0x10 * (n))
> +#define PITLDVAL 0x00
> +#define PITCVAL
6 matches
Mail list logo
