Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-25 Thread Daniel Lezcano
On 19/05/2017 15:58, Linus Walleij wrote: > On Thu, May 18, 2017 at 10:17 PM, Linus Walleij > wrote: > >> This merges the Moxa Art timer driver into the Faraday FTTMR010 >> driver and replaces all Kconfig symbols to use the Faraday >> driver instead. We are now so

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-25 Thread Daniel Lezcano
On 19/05/2017 15:58, Linus Walleij wrote: > On Thu, May 18, 2017 at 10:17 PM, Linus Walleij > wrote: > >> This merges the Moxa Art timer driver into the Faraday FTTMR010 >> driver and replaces all Kconfig symbols to use the Faraday >> driver instead. We are now so similar that the drivers can >>

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-19 Thread Linus Walleij
On Thu, May 18, 2017 at 10:17 PM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-19 Thread Linus Walleij
On Thu, May 18, 2017 at 10:17 PM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding a few lines to the Faraday

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-19 Thread Jonas Jensen
On 18 May 2017 at 22:17, Linus Walleij wrote: > ChangeLog v1->v2: > - As it appears that the Aspeed timers can only count downwards, > augment the code to deal with downward counting clockevent, > clock source and sched_clock(), and flag the Aspeed for this > mode.

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-19 Thread Jonas Jensen
On 18 May 2017 at 22:17, Linus Walleij wrote: > ChangeLog v1->v2: > - As it appears that the Aspeed timers can only count downwards, > augment the code to deal with downward counting clockevent, > clock source and sched_clock(), and flag the Aspeed for this > mode. Adding another

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-18 Thread Joel Stanley
On Fri, May 19, 2017 at 4:17 AM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding a

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-18 Thread Joel Stanley
On Fri, May 19, 2017 at 4:17 AM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding a few lines to the Faraday

[PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-18 Thread Linus Walleij
This merges the Moxa Art timer driver into the Faraday FTTMR010 driver and replaces all Kconfig symbols to use the Faraday driver instead. We are now so similar that the drivers can be merged by just adding a few lines to the Faraday timer. Differences: - The Faraday driver explicitly sets the

[PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

2017-05-18 Thread Linus Walleij
This merges the Moxa Art timer driver into the Faraday FTTMR010 driver and replaces all Kconfig symbols to use the Faraday driver instead. We are now so similar that the drivers can be merged by just adding a few lines to the Faraday timer. Differences: - The Faraday driver explicitly sets the