From: Jani Nikula <jani.nikula@linux.intel.com>
To: Khaled Almahallawy <khaled.almahallawy@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, linux-arm-msm@vger.kernel.org
Cc: Khaled Almahallawy <khaled.almahallawy@intel.com>
Subject: Re: [Intel-gfx] [RFC PATCH 0/4] drm/dp: Use DP2.0 DPCD 248h updated register/field names for DP PHY CTS
Date: Thu, 21 Oct 2021 13:00:39 +0300 [thread overview]
Message-ID: <8735ouofy0.fsf@intel.com> (raw)
In-Reply-To: <20211021050713.836498-1-khaled.almahallawy@intel.com>
On Wed, 20 Oct 2021, Khaled Almahallawy <khaled.almahallawy@intel.com> wrote:
> This series updates DPCD 248h register name and PHY test patterns names to follow DP 2.0 Specs.
> Also updates the DP PHY CTS codes of the affected drivers (i915, amd, msm)
> No functional changes expected.
>
> Reference: “DPCD 248h/10Bh/10Ch/10Dh/10Eh Name/Description Consistency”
> https://groups.vesa.org/wg/AllMem/documentComment/2738
You can't do renames like this piece by piece. Every commit must build.
Incidentally, this is one of the reasons we often don't bother with
renames to follow spec changes, but rather stick to the original names.
However, in this case you could switch all drivers to the different test
pattern macros piece by piece, as they're already there.
BR,
Jani.
>
> Khaled Almahallawy (4):
> drm/dp: Rename DPCD 248h according to DP 2.0 specs
> drm/i915/dp: Use DP 2.0 LINK_QUAL_PATTERN_* Phy test pattern
> definitions
> drm/amd/dc: Use DPCD 248h DP 2.0 new name
> drm/msm/dp: Use DPCD 248h DP 2.0 new names/definitions
>
> drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | 2 +-
> drivers/gpu/drm/drm_dp_helper.c | 6 +++---
> drivers/gpu/drm/i915/display/intel_dp.c | 12 ++++++------
> drivers/gpu/drm/msm/dp/dp_catalog.c | 12 ++++++------
> drivers/gpu/drm/msm/dp/dp_ctrl.c | 12 ++++++------
> drivers/gpu/drm/msm/dp/dp_link.c | 16 ++++++++--------
> include/drm/drm_dp_helper.h | 13 +++----------
> 7 files changed, 33 insertions(+), 40 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-10-21 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 5:07 [Intel-gfx] [RFC PATCH 0/4] drm/dp: Use DP2.0 DPCD 248h updated register/field names for DP PHY CTS Khaled Almahallawy
2021-10-21 5:07 ` [Intel-gfx] [RFC PATCH 1/4] drm/dp: Rename DPCD 248h according to DP 2.0 specs Khaled Almahallawy
2021-10-21 9:56 ` Jani Nikula
2021-10-21 5:07 ` [Intel-gfx] [RFC PATCH 2/4] drm/i915/dp: Use DP 2.0 LINK_QUAL_PATTERN_* Phy test pattern definitions Khaled Almahallawy
2021-10-21 5:07 ` [Intel-gfx] [RFC PATCH 3/4] drm/amd/dc: Use DPCD 248h DP 2.0 new name Khaled Almahallawy
2021-10-21 5:07 ` [Intel-gfx] [RFC PATCH 4/4] drm/msm/dp: Use DPCD 248h DP 2.0 new names/definitions Khaled Almahallawy
2021-10-21 5:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp: Use DP2.0 DPCD 248h updated register/field names for DP PHY CTS Patchwork
2021-10-21 5:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-21 6:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-21 9:03 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-10-21 10:00 ` Jani Nikula [this message]
2021-10-21 23:13 ` [Intel-gfx] [RFC PATCH 0/4] " Almahallawy, Khaled
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=8735ouofy0.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=khaled.almahallawy@intel.com \
--cc=linux-arm-msm@vger.kernel.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