Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-31 Thread Laurent Pinchart
Hi Pawel, Sorry for the late reply, I'm currently attending LinuxCon Japan, my mail backlog is growing. On Tuesday 28 May 2013 11:52:52 Pawel Moll wrote: > On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote: > > On Monday 27 May 2013, Daniel Tang wrote: > > > > The one remaining bit that sti

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-29 Thread Arnd Bergmann
On Wednesday 29 May 2013, Daniel Tang wrote: > On 27/05/2013, at 8:31 PM, Arnd Bergmann wrote: > > > On Monday 27 May 2013, Daniel Tang wrote: > >>> The one remaining bit that sticks out is the clcd platform data. As I > >>> said before, I won't require you to convert that to DT in order to > >>>

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Daniel Tang
On 27/05/2013, at 8:31 PM, Arnd Bergmann wrote: > On Monday 27 May 2013, Daniel Tang wrote: >>> The one remaining bit that sticks out is the clcd platform data. As I >>> said before, I won't require you to convert that to DT in order to >>> get your code merged, but I'd also really like to see t

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Andy Shevchenko
On Tue, May 28, 2013 at 5:52 PM, Arnd Bergmann wrote: > depends on KMS_ARMCLCD != 'y' > depends on 'm' if KMS_ARMCLCD Those two above could be one actually. Just my 2 cents. -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Arnd Bergmann
On Tuesday 28 May 2013 15:21:04 Pawel Moll wrote: > On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote: > > On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote: > > > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote: > > >> b) add a new KMS driver for this hardware that can be used as an

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Pawel Moll
On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote: > On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote: > > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote: > >> b) add a new KMS driver for this hardware that can be used as an > >> alternative to the existing one and that works with D

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Linus Walleij
On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote: > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote: >> b) add a new KMS driver for this hardware that can be used as an >> alternative to the existing one and that works with DT. > > There are people working on this, just trying to jump thr

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Pawel Moll
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote: > b) add a new KMS driver for this hardware that can be used as an > alternative to the existing one and that works with DT. There are people working on this, just trying to jump through some legal hoops to post a RFC. Once this is done we'll

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-28 Thread Pawel Moll
On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote: > On Monday 27 May 2013, Daniel Tang wrote: > > > The one remaining bit that sticks out is the clcd platform data. As I > > > said before, I won't require you to convert that to DT in order to > > > get your code merged, but I'd also really li

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-27 Thread Arnd Bergmann
On Monday 27 May 2013, Daniel Tang wrote: > > On Saturday 25 May 2013, Daniel Tang wrote: > > The one remaining bit that sticks out is the clcd platform data. As I > > said before, I won't require you to convert that to DT in order to > > get your code merged, but I'd also really like to see that

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-27 Thread Arnd Bergmann
On Monday 27 May 2013, Daniel Tang wrote: > > The one remaining bit that sticks out is the clcd platform data. As I > > said before, I won't require you to convert that to DT in order to > > get your code merged, but I'd also really like to see that happen, > > as we will also need that to get rid

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-26 Thread Daniel Tang
On 27/05/2013, at 7:23 AM, Arnd Bergmann wrote: > On Saturday 25 May 2013, Daniel Tang wrote: >> Changes between v3 and v4: >> * Remove redundant clock-names in device tree >> * Re-enable bus access to some peripherals on bootup >> * Clean up nspire-classic-timer code. >> - Implement a nspire_t

Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support

2013-05-26 Thread Arnd Bergmann
On Saturday 25 May 2013, Daniel Tang wrote: > Changes between v3 and v4: > * Remove redundant clock-names in device tree > * Re-enable bus access to some peripherals on bootup > * Clean up nspire-classic-timer code. > - Implement a nspire_timer_set_mode function > - Removed messy IO_MATCHx and