From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH v2] drm/dp: DPCD register defines for link status within ESI field
Date: Mon, 18 Sep 2017 10:54:33 +0300 [thread overview]
Message-ID: <87o9q8a1c6.fsf@nikula.org> (raw)
In-Reply-To: <20170914062127.12047-1-dhinakaran.pandiyan@intel.com>
On Wed, 13 Sep 2017, Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com> wrote:
> Link status is available in the ESI field on devices with DPCD r1.2 or
> higher. DP spec also says "An MST upstream device shall use this field
> instead of the Link/Sink Device Status field registers, starting from DPCD
> Address 00200h."
>
> v2: Prefixed DP_ (Jani)
> Rewrote commment to stay within 80 cols.
> Cc: Jani Nikula <jani.nikula@intel.com>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Thanks, pushed to drm-misc-next.
BR,
Jani.
> ---
> include/drm/drm_dp_helper.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index 2c412a15cfa1..11c39f15f1b3 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -738,6 +738,11 @@
> #define DP_RECEIVER_ALPM_STATUS 0x200b /* eDP 1.4 */
> # define DP_ALPM_LOCK_TIMEOUT_ERROR (1 << 0)
>
> +#define DP_LANE0_1_STATUS_ESI 0x200c /* status same as 0x202 */
> +#define DP_LANE2_3_STATUS_ESI 0x200d /* status same as 0x203 */
> +#define DP_LANE_ALIGN_STATUS_UPDATED_ESI 0x200e /* status same as 0x204 */
> +#define DP_SINK_STATUS_ESI 0x200f /* status same as 0x205 */
> +
> #define DP_DPRX_FEATURE_ENUMERATION_LIST 0x2210 /* DP 1.3 */
> # define DP_GTC_CAP (1 << 0) /* DP 1.3 */
> # define DP_SST_SPLIT_SDP_CAP (1 << 1) /* DP 1.4 */
--
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:[~2017-09-18 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 1:03 [PATCH] drm/dp: DPCD register defines for link status within ESI field Dhinakaran Pandiyan
2017-09-14 1:25 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-09-14 6:00 ` [PATCH] " Jani Nikula
2017-09-14 6:18 ` [PATCH] drm/dp: DPCD register defines for link Pandiyan, Dhinakaran
2017-09-14 6:21 ` [PATCH v2] drm/dp: DPCD register defines for link status within ESI field Dhinakaran Pandiyan
2017-09-18 7:54 ` Jani Nikula [this message]
2017-09-14 6:46 ` ✓ Fi.CI.BAT: success for drm/dp: DPCD register defines for link status within ESI field (rev2) Patchwork
2017-09-14 7:44 ` ✗ Fi.CI.IGT: warning " 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=87o9q8a1c6.fsf@nikula.org \
--to=jani.nikula@intel.com \
--cc=dhinakaran.pandiyan@intel.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 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.