From: Jim Bride <jim.bride@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 02/10] drm: Drop VGA from bpc definitions
Date: Mon, 25 Jul 2016 08:03:59 -0700 [thread overview]
Message-ID: <20160725150359.GB5859@shiv> (raw)
In-Reply-To: <1467803094-10473-3-git-send-email-mika.kahola@intel.com>
On Wed, Jul 06, 2016 at 02:04:46PM +0300, Mika Kahola wrote:
> Drop "VGA" from bits per component definitions as these
> are also used by other standards such as DVI, HDMI,
> DP++.
Reviewed-by: Jim Bride <jim.bride@linux.intel.com>
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
> include/drm/drm_dp_helper.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index 6e8b92e..336d742 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -216,11 +216,11 @@
> # define DP_DS_PORT_HPD (1 << 3)
> /* offset 1 for VGA is maximum megapixels per second / 8 */
> /* offset 2 */
> -# define DP_DS_VGA_MAX_BPC_MASK (3 << 0)
> -# define DP_DS_VGA_8BPC 0
> -# define DP_DS_VGA_10BPC 1
> -# define DP_DS_VGA_12BPC 2
> -# define DP_DS_VGA_16BPC 3
> +# define DP_DS_MAX_BPC_MASK (3 << 0)
> +# define DP_DS_8BPC 0
> +# define DP_DS_10BPC 1
> +# define DP_DS_12BPC 2
> +# define DP_DS_16BPC 3
>
> /* link configuration */
> #define DP_LINK_BW_SET 0x100
> --
> 1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-25 15:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 11:04 [PATCH v6 00/10] drm/i915: DP branch devices Mika Kahola
2016-07-06 11:04 ` [PATCH v6 01/10] drm: Add missing DP downstream port types Mika Kahola
2016-07-25 15:03 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 02/10] drm: Drop VGA from bpc definitions Mika Kahola
2016-07-25 15:03 ` Jim Bride [this message]
2016-07-06 11:04 ` [PATCH v6 03/10] drm: Helper to read max clock rate Mika Kahola
2016-07-25 15:05 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 04/10] drm: Helper to read max bits per component Mika Kahola
2016-07-25 15:07 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 05/10] drm: Read DP branch device id Mika Kahola
2016-07-25 15:08 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 06/10] drm: Read DP branch device HW revision Mika Kahola
2016-07-12 13:54 ` Daniel Vetter
2016-08-02 11:16 ` Mika Kahola
2016-07-06 11:04 ` [PATCH v6 07/10] drm: Read DP branch device SW revision Mika Kahola
2016-07-25 15:09 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 08/10] drm/i915: Check pixel rate for DP to VGA dongle Mika Kahola
2016-07-12 13:50 ` Daniel Vetter
2016-08-02 11:18 ` Mika Kahola
2016-07-06 11:04 ` [PATCH v6 09/10] drm/i915: Update bits per component for display info Mika Kahola
2016-07-12 13:51 ` Daniel Vetter
2016-08-02 11:23 ` Mika Kahola
2016-08-02 11:41 ` Ville Syrjälä
2016-08-02 13:18 ` Daniel Vetter
2016-07-06 11:04 ` [PATCH v6 10/10] drm/i915: Add DP branch device info on debugfs Mika Kahola
2016-07-12 13:52 ` Daniel Vetter
2016-07-06 11:50 ` ✗ Ro.CI.BAT: failure for drm/i915: DP branch devices (rev6) Patchwork
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=20160725150359.GB5859@shiv \
--to=jim.bride@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@intel.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 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.