Re: omap DSS fails with tft410 driver panel?

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

On 2012-10-15 19:08, Enric Balletbo Serra wrote:
> Hi Tomi,
> 
> Thanks for your answer.
> 
> 2012/10/12 Tomi Valkeinen <tomi.valkeinen@ti.com>:
>> On 2012-10-11 18:58, Enric Balletbo Serra wrote:
>>> Hi all,
>>>
>>> I see that commit dac8eb5f (OMAPDSS: TFP410: rename dvi files to
>>> tfp410) and commit 2e6f2ee7 (OMAPDSS: TFP410: rename dvi -> tfp410)
>>> changes the panel driver used on some boards. I tested current
>>> linux-next-20101011 kernel with my IGEPv2 board and DSS fails with
>>> following error (see http://pastebin.com/VjPGCQDt for full log) :
>>>
>>>    [   21.222808] omapdss OVERLAY error: check_overlay: paddr cannot be 0
>>>    [   21.229583] omapdss OVERLAY error: check_overlay: paddr cannot be 0
>>>    [   21.236236] omapfb omapfb: setup_plane failed
>>>
>>> Before checking what happens there is a known issue with this ?
>>
>> Works fine for me, although only with a quite minimal test environment.
>>
> 
> I tried with a minimal environment (without X) and I don't see the
> error, so looks you've reason and the problem is with my userspace
> application (X). OTOH, I don't see the video output. I remember that
> this worked before, but seems now is broken. I'll check mux and others
> hints to try to solve the problem ..

It's not about muxing, but something else. So an earlier kernel works
with the exact same userspace and kernel boot arguments? Then we
probably have a bug in the kernel driver. But I can't say much from the
debug prints, except that probably something goes wrong in the
SETUP_PLANE ioctl.

If you can, please add debug prints to omapfb-ioctl.c's
omapfb_setup_plane() and print out the data in the  omapfb_plane_info
parameter, and also prints to the error code paths in the function.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]