Searched hist:cc219afa1853f230ac35f40e6ead5b143f9614b5 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/gpu/drm/omapdrm/dss/ |
| H A D | hdmi_phy.c | diff cc219afa1853f230ac35f40e6ead5b143f9614b5 Fri Aug 04 17:43:51 CDT 2017 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: omapdrm: hdmi: Store PHY features in PHY data structure
PHY features are stored in a global variable, while they should be
properties of the PHY object. As existing OMAP platforms have a single
HDMI PHY this doesn't cause any issue, but doesn't follow the driver
model.
Move the PHY features to the HDMI PHY data structure to follow the
driver model and pave the road for multiple HDMI PHYs support.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
|
| H A D | hdmi.h | diff cc219afa1853f230ac35f40e6ead5b143f9614b5 Fri Aug 04 17:43:51 CDT 2017 Laurent Pinchart <laurent.pinchart@ideasonboard.com> drm: omapdrm: hdmi: Store PHY features in PHY data structure
PHY features are stored in a global variable, while they should be
properties of the PHY object. As existing OMAP platforms have a single
HDMI PHY this doesn't cause any issue, but doesn't follow the driver
model.
Move the PHY features to the HDMI PHY data structure to follow the
driver model and pave the road for multiple HDMI PHYs support.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
|