From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Yetunde Adebisi <yetundex.adebisi@intel.com>,
isg-gms@eclists.intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size
Date: Thu, 31 Mar 2016 10:04:43 +0300 [thread overview]
Message-ID: <87egarnn5g.fsf@intel.com> (raw)
In-Reply-To: <1459348041-28165-2-git-send-email-yetundex.adebisi@intel.com>
On Wed, 30 Mar 2016, Yetunde Adebisi <yetundex.adebisi@intel.com> wrote:
> This is used when reading Display Control capability Registers on the sink
> device.
>
> cc: Jani Nikula <jani.nikula@intel.com>
> cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Yetunde Adebisi <yetundex.adebisi@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> include/drm/drm_dp_helper.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index 1252108..92d9a52 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -621,6 +621,7 @@ u8 drm_dp_get_adjust_request_pre_emphasis(const u8 link_status[DP_LINK_STATUS_SI
> #define DP_BRANCH_OUI_HEADER_SIZE 0xc
> #define DP_RECEIVER_CAP_SIZE 0xf
> #define EDP_PSR_RECEIVER_CAP_SIZE 2
> +#define EDP_DISPLAY_CTL_CAP_SIZE 3
>
> void drm_dp_link_train_clock_recovery_delay(const u8 dpcd[DP_RECEIVER_CAP_SIZE]);
> void drm_dp_link_train_channel_eq_delay(const u8 dpcd[DP_RECEIVER_CAP_SIZE]);
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-31 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 14:27 [PATCH 0/3] DPCD Backlight Control Yetunde Adebisi
2016-03-30 14:27 ` [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size Yetunde Adebisi
2016-03-31 7:04 ` Jani Nikula [this message]
2016-03-30 14:27 ` [PATCH 2/3] drm/i915: Add Backlight Control using DPCD for eDP connectors (v8) Yetunde Adebisi
2016-03-31 7:22 ` Jani Nikula
2016-03-30 14:27 ` [PATCH 3/3] drm/i915: Add backlight Control using DPCD registers for DP connectors Yetunde Adebisi
2016-03-31 7:31 ` Jani Nikula
2016-03-31 14:09 ` ✓ Fi.CI.BAT: success for DPCD Backlight Control (rev5) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-04-26 11:25 [PATCH 0/3] DPCD Backlight Control Yetunde Adebisi
2016-04-26 11:25 ` [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size Yetunde Adebisi
2016-04-05 14:10 [PATCH 0/3] DPCD Backlight Control Yetunde Adebisi
2016-04-05 14:10 ` [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size Yetunde Adebisi
2016-04-05 13:50 [PATCH 0/3] DPCD Backlight Control Yetunde Adebisi
2016-04-05 13:50 ` [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size Yetunde Adebisi
2016-03-07 12:58 [PATCH 0/3] DPCD Backlight Control Yetunde Adebisi
2016-03-07 12:58 ` [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size Yetunde Adebisi
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=87egarnn5g.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=isg-gms@eclists.intel.com \
--cc=yetundex.adebisi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox