Hi,
On 10/19/2016 07:55 PM, Laurent Pinchart wrote:
The drm_bridge object models on- or off-chip hardware encoders and
provide an abstract control API to display drivers. In order to help
display drivers creating the right kind of drm_encoder object, expose
the type of the hardware encoder associated with each bridge.
Signed-off-by: Laurent Pinchart <laurent.pinchart+rene...@ideasonboard.com>
---
include/drm/drm_bridge.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h
index 530a1d6e8cde..e93105bffc3c 100644
--- a/include/drm/drm_bridge.h
+++ b/include/drm/drm_bridge.h
@@ -194,6 +194,14 @@ struct drm_bridge {
#endif
struct list_head list;
+ /**
+ * @encoder_type:
+ *
+ * Type of the hardware encoder modeled by the bridge as one of the
+ * DRM_MODE_ENCODER_* types. This will usually be identical to the
+ * ->encoder.encoder_type for the last bridge in the chain only.
It isn't entirely clear in the comment that we're mentioning
drm_encoder's encoder_type here. Maybe we can give a &drm_encoder
back reference?
+ */
+ int encoder_type;
const struct drm_bridge_funcs *funcs;
void *driver_private;
};
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
