Immediate followup: I got the touchscreen working together with framebuffer by setting the SPI clock to 50 kHz instead of 1.5 MHz in arch/arm/mach-omap2/board-2430sdp.c. BR Simon Braunschmidt 2008/5/5 Simon Braunschmidt <sbraunschmidt.linuxlists@xxxxxxxxxxxxxx>: > Hi > > Just a follow-up on the SYNCLOST problem we are seeing with the > framebuffer driver. > > It seems as if we only get SYNCLOST signal in the display controller > interrupt handler when we activate the ADS7846 touchscreen which is > connected via SPI. Maybe signal integrity is to blame, since both LCD > and touchscreen signal go over the same flat cable. > > Problem is seen on 2.6.23-omap1 with CONFIG_SPI_OMAP24XX, > CONFIG_TOUCHSCREEN_ADS7846 and CONFIG_FB_OMAP enabled, configured for > 2430sdp. > > Can anyone comment on this issue? > > > BR > Simon Braunschmidt > 2008/4/25 Simon Braunschmidt <sbraunschmidt.linuxlists@xxxxxxxxxxxxxx>: > > > > Hi Arun, all > > > > I just switched to 2.6.23-omap1, which is booting with framebuffer. > > Which recent kernel version would you recommend to get down and dirty > > with Android on the 2430sdp? > > > > btw 2.6.24-omap1 is booting for me on 2430sdp, but with not > > framebuffer, though framebuffer gets registered according to kernel > > bootlog and is now also usable with my testprogramm, just nothing on > > the lcd > > > > The bug we were seeing: > > > > SYNCLOST .... something in dispc.c irq handler > > > > disappeared, looking backwards this may be also related to our recent > > switch to git for maintaining kernel sources. Maybe our selfhosted > > sources got tainted by our half-baked patching approaches, so sorry > > for the noise... > > > > Greetings, Gruessla > > Simon > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
