From: Daniel Vetter <daniel@ffwll.ch>
To: Archit Taneja <architt@codeaurora.org>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
airlied@redhat.com, andy.yan@rock-chips.com,
ajaykumar.rs@samsung.com
Subject: Re: [PATCH v3 1/2] drm: bridge: Allow daisy chaining of bridges
Date: Wed, 20 May 2015 09:46:19 +0200 [thread overview]
Message-ID: <20150520074619.GA15256@phenom.ffwll.local> (raw)
In-Reply-To: <555C3424.9020003@codeaurora.org>
On Wed, May 20, 2015 at 12:43:40PM +0530, Archit Taneja wrote:
> Where do you think drm_bridge documentation fits? I was considering putting
> it under 'KMS initialization and setup', while pointing out that it isn't
> exactly a drm_mode_object entity like crtcs or encoders etc.
Since drm_bridge is not exposed to userspace it's not part of core drm and
imo should be a helper library - it's only used by drivers internally to
help them implement modesetting. New chapter under "Mode Setting Helper
Functions" sounds best to me.
Btw drm_bridge being a core part of drm is another thing we probably
should fix up eventually. I looked into doing that a while ago, but it
wasn't quite that simple. And I don't have a good arm build-test setup, so
hard to make sure I've caught all drivers and made sure they depend upon
DRM_KMS_HELPER properly.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-05-20 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 8:35 [PATCH v3 1/2] drm: bridge: Allow daisy chaining of bridges Archit Taneja
2015-05-19 8:35 ` [PATCH v3 2/2] drm: bridge: Add missing headerdocs for older bridge functions Archit Taneja
2015-05-19 9:37 ` Daniel Vetter
2015-05-19 11:10 ` Archit Taneja
2015-05-19 9:34 ` [PATCH v3 1/2] drm: bridge: Allow daisy chaining of bridges Daniel Vetter
2015-05-19 11:07 ` Archit Taneja
2015-05-19 15:30 ` Daniel Vetter
2015-05-20 5:19 ` Archit Taneja
2015-05-20 6:35 ` Daniel Vetter
2015-05-20 7:13 ` Archit Taneja
2015-05-20 7:46 ` Daniel Vetter [this message]
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=20150520074619.GA15256@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@redhat.com \
--cc=ajaykumar.rs@samsung.com \
--cc=andy.yan@rock-chips.com \
--cc=architt@codeaurora.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.