From: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
To: Anusha Srivatsa <anusha.srivatsa@intel.com>,
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 0/4] Prep series - CDCLK code churn
Date: Fri, 21 Oct 2022 12:36:06 +0530 [thread overview]
Message-ID: <Y1JE3kDZXBBjKOPz@bala-ubuntu> (raw)
In-Reply-To: <20221021002024.390052-1-anusha.srivatsa@intel.com>
On 20.10.2022 17:20, Anusha Srivatsa wrote:
> No functional changes. The series is more of a prep series
> for the mid_cdclk_config series:
> https://patchwork.freedesktop.org/series/109694/
>
> Main change:
> - Change usage of "crawler" and "squasher". Use crawling and
> squashing instead.
> - Handle bot hsquash and cralw similar in terms of checking
Please check the typos here
Regards,
Bala
> if the platform supports them or not. With the changes introduced,
> both are a display feature flag.
> - Move code from bxt_set_cdclk() to make it more modularized
> and easy to read and understand.
>
> Cc: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Anusha Srivatsa (4):
> drm/i915/display: Change terminology for cdclk actions
> drm/i915/display: Introduce HAS_CDCLK_SQUASH macro
> drm/i915/display: Move chunks of code out of bxt_set_cdclk()
> drm/i915/display: Move squash_ctl register programming to its own
> function
>
> drivers/gpu/drm/i915/display/intel_cdclk.c | 80 ++++++++++++----------
> drivers/gpu/drm/i915/i915_drv.h | 1 +
> drivers/gpu/drm/i915/i915_pci.c | 1 +
> drivers/gpu/drm/i915/intel_device_info.h | 1 +
> 4 files changed, 48 insertions(+), 35 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-10-21 7:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 0:20 [Intel-gfx] [PATCH 0/4] Prep series - CDCLK code churn Anusha Srivatsa
2022-10-21 0:20 ` [Intel-gfx] [PATCH 1/4] drm/i915/display: Change terminology for cdclk actions Anusha Srivatsa
2022-10-21 0:20 ` [Intel-gfx] [PATCH 2/4] drm/i915/display: Introduce HAS_CDCLK_SQUASH macro Anusha Srivatsa
2022-10-21 7:11 ` Balasubramani Vivekanandan
2022-10-21 8:46 ` Jani Nikula
2022-10-21 20:28 ` Srivatsa, Anusha
2022-10-21 0:20 ` [Intel-gfx] [PATCH 3/4] drm/i915/display: Move chunks of code out of bxt_set_cdclk() Anusha Srivatsa
2022-10-21 8:32 ` Jani Nikula
2022-10-21 20:33 ` Srivatsa, Anusha
2022-10-21 0:20 ` [Intel-gfx] [PATCH 4/4] drm/i915/display: Move squash_ctl register programming to its own function Anusha Srivatsa
2022-10-21 7:07 ` Balasubramani Vivekanandan
2022-10-21 21:06 ` Srivatsa, Anusha
2022-10-21 8:41 ` Jani Nikula
2022-10-21 20:31 ` Srivatsa, Anusha
2022-10-21 1:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prep series - CDCLK code churn Patchwork
2022-10-21 1:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-21 1:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-21 6:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-21 7:06 ` Balasubramani Vivekanandan [this message]
2022-10-21 8:42 ` [Intel-gfx] [PATCH 0/4] " Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2022-10-21 21:39 Anusha Srivatsa
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=Y1JE3kDZXBBjKOPz@bala-ubuntu \
--to=balasubramani.vivekanandan@intel.com \
--cc=anusha.srivatsa@intel.com \
--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