Hi,
I am working on a minimal patch set for initial upstream support of
the Pyra with using omap2plus_defconfig.
It will not support all features (like TILER, sensors, nubs), but is quite simple:
* add panel driver
* add charger driver
* add device tree
* augment defconfig
When looking at my patch set that works, I have more fixes for v5.0-rc5
than there are specific additions for the Pyra. And fixes that were not needed
up to v4.20. I.e. the core is currently more broken than what is missing for
making the device supported...
These additional fixes which I currently have collected are:
Tomi (~18 dec)i:
drm/omap: fix dsi depopulate
drm/omap: hackfix dsi bus flags
drm/omap: fix crash in DSI debug dumps
Sebastian (~21 nov):
drm/omap: add support for manually updated displays
drm/omap: add framedone interrupt support
drm/omap: don't check dispc timings for DSI
drm/omap: use DRM_DEBUG_DRIVER instead of CORE
Tony (~15 jan):
ARM: dts: Configure clock parent for pwm vibra
ti-sysc: Fix timer handling with drop pm_runtime_irq_safe()
Hackfix for dm-timer9 to make Pyra backlight PWM work again
clocksource: timer-ti-dm: Fix pwm dmtimer usage of fck reparenting
ARM: OMAP5+: Fix inverted nirq pin interrupts with irq_set_type
Some are already sitting in linux-next and will likely be in v5.1-rc1,
but the majority is not even in linux-next.
So the question is when you plan to upstream and/or backport
these (or improved) bug fixes to v5.0?
BR and thanks,
Nikolaus