From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/6] drm/tile: expose the tile property to userspace
Date: Mon, 20 Oct 2014 17:35:16 +0200 [thread overview]
Message-ID: <20141020153516.GQ26941@phenom.ffwll.local> (raw)
In-Reply-To: <20141020153411.GP26941@phenom.ffwll.local>
On Mon, Oct 20, 2014 at 05:34:11PM +0200, Daniel Vetter wrote:
> On Mon, Oct 20, 2014 at 05:31:51PM +0200, Daniel Vetter wrote:
> > On Mon, Oct 20, 2014 at 04:37:15PM +1000, Dave Airlie wrote:
> > > From: Dave Airlie <airlied@redhat.com>
> > >
> > > This takes the tiling info from the connector and
> > > exposes it to userspace, as a blob object in a
> > > connector property.
> > >
> > > The contents of the blob is ABI.
> > >
> > > Signed-off-by: Dave Airlie <airlied@redhat.com>
> > > ---
> > > drivers/gpu/drm/drm_crtc.c | 36 ++++++++++++++++++++++++++++++++++++
> > > drivers/gpu/drm/i915/intel_dp_mst.c | 2 ++
> > > include/drm/drm_crtc.h | 4 ++++
> > > 3 files changed, 42 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> > > index 93135d4..81e867a 100644
> > > --- a/drivers/gpu/drm/drm_crtc.c
> > > +++ b/drivers/gpu/drm/drm_crtc.c
> > > @@ -1319,6 +1319,11 @@ static int drm_mode_create_standard_connector_properties(struct drm_device *dev)
> > > "PATH", 0);
> > > dev->mode_config.path_property = dev_path;
> > >
> > > + dev->mode_config.tile_property = drm_property_create(dev,
> > > + DRM_MODE_PROP_BLOB |
> > > + DRM_MODE_PROP_IMMUTABLE,
> > > + "TILE", 0);
> > > +
> > > return 0;
> > > }
> > >
> > > @@ -4004,6 +4009,37 @@ int drm_mode_connector_set_path_property(struct drm_connector *connector,
> > > }
> > > EXPORT_SYMBOL(drm_mode_connector_set_path_property);
> > >
> > > +int drm_mode_connector_set_tile_property(struct drm_connector *connector)
> >
> > Same again, please add some kerneldoc for this function here.
>
> While at it, please also add the missing kerneldoc for the functions
> you've already added for dp mst support.
And the docbook xml table with all the properties we have should also be
updated for both of them.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-10-20 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 6:37 drm tiled monitor support (not hiding in kernel) Dave Airlie
2014-10-20 6:37 ` [PATCH 1/6] drm/displayid: add displayid defines and edid extension Dave Airlie
2014-10-20 16:16 ` Jani Nikula
2014-10-20 6:37 ` [PATCH 2/6] drm: add tile_group support Dave Airlie
2014-10-20 9:11 ` David Herrmann
2014-10-20 15:32 ` Daniel Vetter
2014-10-22 2:23 ` Dave Airlie
2014-10-22 8:42 ` Daniel Vetter
2014-10-20 6:37 ` [PATCH 3/6] drm/mst: cached EDID for logical ports Dave Airlie
2014-10-20 6:37 ` [PATCH 4/6] drm/connector: store tile information from displayid Dave Airlie
2014-10-20 6:37 ` [PATCH 5/6] drm/tile: expose the tile property to userspace Dave Airlie
2014-10-20 9:15 ` David Herrmann
2014-10-20 15:31 ` Daniel Vetter
2014-10-20 15:34 ` [Intel-gfx] " Daniel Vetter
2014-10-20 15:35 ` Daniel Vetter [this message]
2014-10-20 6:37 ` [PATCH 6/6] drm/fb: add support for tiled monitor configurations Dave Airlie
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=20141020153516.GQ26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox