From: Archit Taneja <architt@codeaurora.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 4/8] drm: Add encoder_type field to the drm_bridge structure
Date: Thu, 20 Oct 2016 17:45:46 +0530 [thread overview]
Message-ID: <644b6ca7-64d3-3bf0-1995-34e9f60f4c85@codeaurora.org> (raw)
In-Reply-To: <1476887143-24831-5-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
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+renesas@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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-20 12:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 14:25 [PATCH 0/8] R-Car DU: Use drm bridge API Laurent Pinchart
2016-10-19 14:25 ` [PATCH 1/8] drm: bridge: Add LVDS encoder driver Laurent Pinchart
2016-10-21 5:21 ` Archit Taneja
2016-10-21 10:21 ` Laurent Pinchart
2016-10-26 21:32 ` Rob Herring
2016-10-19 14:25 ` [PATCH 2/8] drm: bridge: vga-dac: Add adi,adv7123 compatible string Laurent Pinchart
2016-10-21 5:13 ` Archit Taneja
2016-10-21 10:22 ` Laurent Pinchart
2016-10-21 10:43 ` Archit Taneja
2016-10-19 14:25 ` [PATCH 3/8] drm: bridge: lvds-encoder: Add thine,thc63lvdm83d " Laurent Pinchart
2016-10-19 14:25 ` [PATCH 4/8] drm: Add encoder_type field to the drm_bridge structure Laurent Pinchart
2016-10-20 12:15 ` Archit Taneja [this message]
2016-10-19 14:25 ` [PATCH 5/8] drm: bridge: Set bridges' encoder type Laurent Pinchart
2016-10-19 14:25 ` [PATCH 6/8] drm: Set on-chip " Laurent Pinchart
2016-10-19 14:25 ` [PATCH 7/8] drm: rcar-du: Replace manual VGA DAC implementation with DRM bridge Laurent Pinchart
2016-10-19 14:25 ` [PATCH 8/8] drm: rcar-du: Initialize encoder's type based on the bridge's type Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=644b6ca7-64d3-3bf0-1995-34e9f60f4c85@codeaurora.org \
--to=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox