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] drm/dp: DPCD register defines for link status within ESI field
Date: Thu, 14 Sep 2017 09:00:57 +0300 [thread overview]
Message-ID: <87o9qdizty.fsf@nikula.org> (raw)
In-Reply-To: <20170914010359.11016-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."
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> ---
> 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..0bf15525cdd0 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 LANE0_1_STATUS_ESI 0x200c /* Same as status in 0x202 */
> +#define LANE2_3_STATUS_ESI 0x200d /* Same as status in 0x203 */
> +#define LANE_ALIGN_STATUS_UPDATED_ESI 0x200e /* Same as status in 0x204 */
> +#define SINK_STATUS_ESI 0x200f /* Same as status in 0x205 */
With the macro names prefixed with DP_,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> +
> #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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-14 6:00 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 ` Jani Nikula [this message]
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
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=87o9qdizty.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox