Hi,
Am 14.11.2016 um 04:11 schrieb Michael Mrozek EvilDragon@openpandora.org:
Hi,
I've got some more questions.
The board I used for testing the didn't have a display board or LCD cable attached.
Sometimes, I got the Atomic Timeout errors from omapdrm and MIPI initializing but finding no device (even running X Server) while sometimes these errors don't appear and X simply doesn't find a screen.
Any idea what that is and how this happens?
That is likely a race condition, i.e. something assumes that some other thing is already initialized.
I think those atomic timeouts are no longer in effect when we have the non-rotated display boards. Then we can use the proper panel driver module and no longer need the mipi-panel-debug driver (which triggers those Atomic Timeout errors).
I also always see: palmas-usb 48070000.i2c:palmas@48:palmas_usb: failed to get id gpio
Yes, I have this as well.
Could that be related to our power issue or does this simply mean I've only have an AC power adaptor connected to the USB port?
Neither. It is about the USB ID pin (auto-detection of an OTG cable). It has been introduced here:
https://lkml.org/lkml/2015/7/13/319
I am not sure why it fails, but it likely is spurious from deferred probing until it succeeds.
BR, Nikolaus
PS: I had quite some problems booting the Pyra board - until I found out that I still had configured EARLY_PRINTK for OMAP3...