Re: [PATCH 0/6] OMAP: board file changes for DSS2 porting

[Tony Lindgren <tony@atomide.com>]

* Tomi Valkeinen <tomi.valkeinen@ti.com> [110510 17:00]:
> On Tue, 2011-05-10 at 16:35 +0300, Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@ti.com> [110509 19:58]:
> > 
> > Do the dss platform data code coalescing patches affect these?
> 
> Do you mean the recent discussions about DSS regulator stuff? If so, no.
> These patches do not introduce any regulator uses.

OK
 
> > We just hate positive diffstats for arch/arm/*omap*/ for the upcoming
> > merge window :)
> 
> Well... I know, but if we want to port the old drivers to DSS2 it really
> can't be helped. The display device definitions in the board files are
> probably a bit more verbose with DSS2 than with old omapfb, due to more
> features and better configurability.
> 
> That said, if you want to calm down the arch/arm/*omap* changes for this
> merge window I can just postpone these (and some other display related
> board changes in dss2 tree) to the next one. They are not critical in
> any way regarding DSS2 development, they just would help us to clean up
> the old omapfb code (which probably won't affect arch/arm/*omap* much).

Let's do that, I guess that's your v2 of the set. Then we can have a
separate branch for the new code that we can then merge when we can.
 
> Speaking of which, the include file for DSS2 currently resides in
> arch/arm/plat-omap/include/plat/display.h. I guess this is not right
> place for it, as the driver itself is in drivers/, even if the driver is
> OMAP-only driver?

Yes it could be moved.
 
> > Also, these patches should also be posted to linux-arm-kernel list for
> > review before I can apply.
> 
> Ok. Should all arch/arm/*omap* code be posted to linux-arm-kernel also?
> I feel like spamming if I mail the patches to three different mailing
> lists =).

Yes, that way people on linux-arm-kernel can also review them.

Regards,

Tony