You've already forked linux-apfs
mirror of
https://github.com/linux-apfs/linux-apfs.git
synced 2026-05-01 15:00:59 -07:00
drm/rcar-du: Rework output routing support
Split the output routing specification between SoC-internal data, specified in the rcar_du_device_info structure, and board data, passed through platform data. The DU has 5 possible outputs (DPAD0/1, LVDS0/1, TCON). SoC-internal output routing data specify which output are valid, which CRTCs can be connected to the valid outputs, and the type of in-SoC encoder for the output. Platform data then specifies external encoders and the output they are connected to. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
This commit is contained in:
@@ -22,7 +22,7 @@ struct rcar_du_device;
|
||||
|
||||
struct rcar_du_encoder {
|
||||
struct drm_encoder encoder;
|
||||
unsigned int output;
|
||||
enum rcar_du_output output;
|
||||
};
|
||||
|
||||
#define to_rcar_encoder(e) \
|
||||
@@ -40,7 +40,8 @@ struct drm_encoder *
|
||||
rcar_du_connector_best_encoder(struct drm_connector *connector);
|
||||
|
||||
int rcar_du_encoder_init(struct rcar_du_device *rcdu,
|
||||
enum rcar_du_encoder_type type, unsigned int output,
|
||||
enum rcar_du_encoder_type type,
|
||||
enum rcar_du_output output,
|
||||
const struct rcar_du_encoder_data *data);
|
||||
|
||||
#endif /* __RCAR_DU_ENCODER_H__ */
|
||||
|
||||
Reference in New Issue
Block a user