From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFCv1 02/12] drm: add object property type
Date: Mon, 7 Oct 2013 16:43:35 +0300 [thread overview]
Message-ID: <20131007134335.GI9395@intel.com> (raw)
In-Reply-To: <1381020350-1125-3-git-send-email-robdclark@gmail.com>
On Sat, Oct 05, 2013 at 08:45:40PM -0400, Rob Clark wrote:
> diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h
> index 5508117..35921ba 100644
> --- a/include/uapi/drm/drm_mode.h
> +++ b/include/uapi/drm/drm_mode.h
> @@ -231,6 +231,7 @@ struct drm_mode_get_connector {
> #define DRM_MODE_PROP_ENUM (1<<3) /* enumerated type with text strings */
> #define DRM_MODE_PROP_BLOB (1<<4)
> #define DRM_MODE_PROP_BITMASK (1<<5) /* bitmask of enumerated types */
> +#define DRM_MODE_PROP_OBJECT (1<<6) /* drm mode object */
This way to using up one bit for each type sucks big time. IIRC we
discussed this at Fosdem and one idea was to leave the current bits as
sort of base types, and reserve a bunch of the other bits to indicate a
sub-type. For instance the new signed range and object ID prop types
could be sub-types of the current range type.
Maybe we should reserve a few more bits for new base types in case we
need them in the future, or just add sometime king DRM_MODE_PROP_MISC,
which is where we'd stick every sub-type that doesn't fit the current
base types.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-10-07 13:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 0:45 [RFCv1 00/12] Atomic/nuclear modeset/pageflip Rob Clark
2013-10-06 0:45 ` [RFCv1 01/12] drm: add atomic fxns Rob Clark
2013-10-06 0:45 ` [RFCv1 02/12] drm: add object property type Rob Clark
2013-10-07 13:43 ` Ville Syrjälä [this message]
2013-10-07 14:44 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 03/12] drm: add DRM_MODE_PROP_DYNAMIC property flag Rob Clark
2013-10-07 13:46 ` Ville Syrjälä
2013-10-07 14:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 04/12] drm: add DRM_MODE_PROP_SIGNED " Rob Clark
2013-10-07 14:46 ` Matt Plumtree
2013-10-06 0:45 ` [RFCv1 05/12] drm: helpers to find mode objects (BEFORE drm: split property values out) Rob Clark
2013-10-06 0:48 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 06/12] drm: split propvals out and blob property support Rob Clark
2013-10-06 0:45 ` [RFCv1 07/12] drm: Allow drm_mode_object_find() to look up an object of any type Rob Clark
2013-10-06 0:45 ` [RFCv1 08/12] drm: Refactor object property check code Rob Clark
2013-10-07 13:47 ` Ville Syrjälä
2013-10-06 0:45 ` [RFCv1 09/12] drm: convert plane to properties/state Rob Clark
2013-10-06 0:45 ` [RFCv1 10/12] drm: convert crtc " Rob Clark
2013-10-07 13:39 ` Ville Syrjälä
2013-10-07 14:03 ` Rob Clark
2013-10-07 14:19 ` Ville Syrjälä
2013-10-07 14:29 ` Rob Clark
2013-10-07 17:51 ` Daniel Vetter
2013-10-06 0:45 ` [RFCv1 11/12] drm: Atomic modeset ioctl Rob Clark
2013-10-07 13:28 ` Ville Syrjälä
2013-10-07 13:55 ` Rob Clark
2013-10-07 14:18 ` Ville Syrjälä
2013-10-07 14:39 ` Rob Clark
2013-10-07 15:05 ` Ville Syrjälä
2013-10-07 15:20 ` Rob Clark
2013-10-07 17:56 ` Daniel Vetter
2013-10-07 18:49 ` Rob Clark
2013-10-08 18:35 ` Matt Roper
2013-10-08 18:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 12/12] ARM: add get_user() support for 8 byte types Rob Clark
2013-10-06 8:53 ` Russell King - ARM Linux
2013-10-06 14:09 ` Rob Clark
2013-10-06 15:56 ` Russell King - ARM Linux
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=20131007134335.GI9395@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).