From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] PL1 power limit fixes for ATSM
Date: Thu, 16 Feb 2023 16:55:38 -0500 [thread overview]
Message-ID: <Y+6mWiPNgvYPfCoj@intel.com> (raw)
In-Reply-To: <20230216164944.2366150-1-ashutosh.dixit@intel.com>
On Thu, Feb 16, 2023 at 08:49:42AM -0800, Ashutosh Dixit wrote:
> Previous PL1 power limit implementation assumed that the PL1 limit is
> always enabled in HW. However we now find this not to be the case on ATSM
> where the PL1 limit is disabled at power up. This requires changes in the
> previous PL1 limit implementation.
>
> v2: Dropping Patch 3 (since it is NAK'd by hwmon) so that the first two
> patches can get merged. The first two patches are sufficient to fix the
> main ATSM issue.
pushed both patches to drm-intel-next.
>
> Ashutosh Dixit (2):
> drm/i915/hwmon: Replace hwm_field_scale_and_write with
> hwm_power_max_write
> drm/i915/hwmon: Enable PL1 limit when writing limit value to HW
>
> drivers/gpu/drm/i915/i915_hwmon.c | 37 ++++++++++++++-----------------
> 1 file changed, 17 insertions(+), 20 deletions(-)
>
> --
> 2.38.0
>
next prev parent reply other threads:[~2023-02-16 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 16:49 [Intel-gfx] [PATCH 0/2] PL1 power limit fixes for ATSM Ashutosh Dixit
2023-02-16 16:49 ` [Intel-gfx] [PATCH 1/2] drm/i915/hwmon: Replace hwm_field_scale_and_write with hwm_power_max_write Ashutosh Dixit
2023-02-16 16:49 ` [Intel-gfx] [PATCH 2/2] drm/i915/hwmon: Enable PL1 limit when writing limit value to HW Ashutosh Dixit
2023-02-16 20:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for PL1 power limit fixes for ATSM (rev2) Patchwork
2023-02-16 21:55 ` Rodrigo Vivi [this message]
2023-02-17 8:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=Y+6mWiPNgvYPfCoj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=ashutosh.dixit@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