arm: omap: display: Ensure DRM/FB/V4L devices are created if DSS is available
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest4 patches 2 repliesIn review
Changes in v2 from the cover letter
- Move device creation for omapfb and omap_vout to omap_display_init too.
- Keep the DMM DT conversion as a separate patch series since this series does something different now.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | arm: omap: drm: Don't build device for DMMarch/ | +0 | 0 replies | |
| 2/4 | arm: omap: display: Create omapdrm device inside omap_display_initarch/ arch/ arch/ +1 more | +14 | 0 replies | |
| 3/4 | arm: omap: display: Create omapvrfb and omapfb devices inside omap_display_initarch/ arch/ arch/ | +23 | 0 replies | |
| 4/4 | arm: omap: display: Create omap_vout device inside omap_display_initarch/ arch/ arch/ | +13 | 0 replies |
Reviews trailers per patch
None of the 4 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Tomi Valkeinen |
|---|---|
| Series | A-b |
| 1/4 | |
| 2/4 | |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/4] arm: omap: display: Ensure DRM/FB/V4L devices are created if DSS is available
Currently, omapdrm, omapfb and omap_vout platform devices are created and registered through omap_arch_initcalls. In a multiplatform config. It's possible that all the corresponding configs for the above drivers along with omapdss config are selected even if the hardware doesn't have a DSS IP.
If the image is booted on a AM33xx platform, the above drm, fb and v4l devices would be registered throuth the omap_arch_initcalls even if omapdss itself isn't registered. These platform devices don't cause any harm, but are unnecessary.
Move the registration of these devices into omap_display_init(), which registers omapdss devices and is called only if the platform has DSS hardware.
Also, the first patch prevents creation of a DMM device when omapdrm device is registered. With the removal of address and irq data from the omap4 hwmods, the probe of DMM driver fails and omapdrm isn't able to utilize the DMM hardware. This will be fixed when DMM DT nodes are added for omap4, omap5 and dra7x.
Changes in v2:
- Move device creation for omapfb and omap_vout to omap_display_init too.
- Keep the DMM DT conversion as a separate patch series since this series does something different now.
Archit Taneja (4):
arm: omap: drm: Don't build device for DMM
arm: omap: display: Create omapdrm device inside omap_display_init
arm: omap: display: Create omapvrfb and omapfb devices inside
omap_display_init
arm: omap: display: Create omap_vout device inside omap_display_init
arch/arm/mach-omap2/Makefile | 6 +----- arch/arm/mach-omap2/devices.c | 10 +++++----- arch/arm/mach-omap2/display.c | 28 ++++++++++++++++++++++++++++ arch/arm/mach-omap2/display.h | 4 ++++ arch/arm/mach-omap2/drm.c | 24 +++++------------------- arch/arm/mach-omap2/fb.c | 14 +++++++------- 6 files changed, 50 insertions(+), 36 deletions(-)
Signature · 1 line
1.8.1.2