OMAPDSS: outputs: Create and register output instances
authorArchit Taneja <archit@ti.com>
Wed, 26 Sep 2012 11:00:49 +0000 (16:30 +0530)
committerArchit Taneja <archit@ti.com>
Wed, 26 Sep 2012 11:00:49 +0000 (16:30 +0530)
commit81b87f515f6abbbe4eef42835065db9d0831ef35
tree3eebf0e10cd70425bb80c60202236f8a2ce96a38
parent484dc404d233696ef65a8e676f9d4fe563b091ee
OMAPDSS: outputs: Create and register output instances

Add output structs to output driver's private data. Register output instances by
having an init function in the probes of the platform device drivers for
different outputs. The *_init_output for each output registers the output and
fill up the output's plaform device, type and id fields. The *_uninit_output
functions unregister the output.

In the probe of each interface driver, the output entities are initialized
before the *_probe_pdata() functions intentionally. This is done to ensure that
the output entity is prepared before the panels connected to the output are
registered. We need the output entities to be ready because OMAPDSS will try
to make connections between overlays, managers, outputs and devices during the
panel's probe.

Signed-off-by: Archit Taneja <archit@ti.com>
drivers/video/omap2/dss/dpi.c
drivers/video/omap2/dss/dsi.c
drivers/video/omap2/dss/hdmi.c
drivers/video/omap2/dss/rfbi.c
drivers/video/omap2/dss/sdi.c
drivers/video/omap2/dss/venc.c
This page took 0.031164 seconds and 5 git commands to generate.