From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v6 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes
Date: Thu, 26 May 2022 09:39:53 +0100 [thread overview]
Message-ID: <fb8e48f7-dcd9-56fe-f329-97053d8e0126@linux.intel.com> (raw)
In-Reply-To: <87v8ts7lw4.wl-ashutosh.dixit@intel.com>
On 26/05/2022 09:12, Dixit, Ashutosh wrote:
> On Wed, 25 May 2022 01:21:06 -0700, Dixit, Ashutosh wrote:
>>
>> On Mon, 23 May 2022 01:57:51 -0700, Tvrtko Ursulin wrote:
>>>
>>> On 13/05/2022 02:36, Ashutosh Dixit wrote:
>>>> Some recent Intel dGfx platforms allow media IP to work at a different
>>>> frequency from the base GT. This patch series exposes sysfs controls for
>>>> this functionality in the new per-gt sysfs. Some enhancements and fixes to
>>>> previous per-gt functionality are also included to complete the new
>>>> functionality:
>>>> * Patches 1 and 2 implement basic sysfs controls for media freq
>>>> * Patch 3 extends previous pcode functions for multiple gt's
>>>> * Patch 4 inits pcode on different gt's
>>>> * Patch 5 adds a couple of pcode helpers
>>>> * Patch 6 uses the new pcode functions to retrieve media RP0/RPn freq
>>>> * Patch 7 fixes memory leaks in the previous per-gt sysfs implementation
>>>> and some code refactoring
>>>
>>> Patches 1, 3 and 5 have been merged to drm-intel-next, and then branch
>>> cross-merged into drm-intel-gt-next.
>>>
>>> You can try re-sending the rest of the series now and see if that goes
>>> smoothly.
>>
>> I sent the patches out Mon but am struggling to get a satisfactory CI run
>> from what it looks like are CI issues (CI runs were fine on previous
>> versions). Will update after we have successful CI. Thanks.
>
> Hi Tvrtko,
>
> We now have CI results. They look good to me (except that there is a false
> positive). In case you think this is good enough to merge these patches
> now:
>
> https://patchwork.freedesktop.org/series/102665/#rev10
Pushed, with no conflicts even! :)
Regards,
Tvrtko
prev parent reply other threads:[~2022-05-26 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 1:36 [Intel-gfx] [PATCH v6 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 1/7] drm/i915: Introduce has_media_ratio_mode Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 2/7] drm/i915/gt: Add media freq factor to per-gt sysfs Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 3/7] drm/i915/pcode: Extend pcode functions for multiple gt's Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 4/7] drm/i915/pcode: Init pcode on different gt's Ashutosh Dixit
2022-05-18 16:03 ` Tvrtko Ursulin
2022-05-13 1:36 ` [Intel-gfx] [PATCH 5/7] drm/i915/pcode: Add a couple of pcode helpers Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 6/7] drm/i915/gt: Add media RP0/RPn to per-gt sysfs Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 7/7] drm/i915/gt: Fix memory leaks in " Ashutosh Dixit
2022-05-13 4:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Media freq factor and per-gt enhancements/fixes (rev6) Patchwork
2022-05-13 4:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-13 6:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-13 7:18 ` Dixit, Ashutosh
2022-05-13 17:14 ` Vudum, Lakshminarayana
2022-05-13 16:06 ` Patchwork
2022-05-13 16:59 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-05-23 8:57 ` [Intel-gfx] [PATCH v6 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Tvrtko Ursulin
2022-05-25 8:21 ` Dixit, Ashutosh
2022-05-26 8:12 ` Dixit, Ashutosh
2022-05-26 8:39 ` Tvrtko Ursulin [this message]
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=fb8e48f7-dcd9-56fe-f329-97053d8e0126@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=ashutosh.dixit@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