From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Nilawar, Badal" <badal.nilawar@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/rps: Centralize computation of freq caps
Date: Wed, 23 Mar 2022 12:56:38 -0700 [thread overview]
Message-ID: <87lex0e93d.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <0ef3cf31-e799-61b9-6907-7e69b0642e3e@intel.com>
On Wed, 23 Mar 2022 00:03:23 -0700, Nilawar, Badal wrote:
>
> > +/* "Caps" frequencies should be converted to MHz using intel_gpu_freq() */
> > +void intel_rps_get_freq_caps(struct intel_rps *rps, struct intel_rps_freq_caps *capSis)
>
> Since this function is covering gen6 and above it would be good to rename
> it as gen6_rps_get_freq_caps.
I've made this change in v4. Thanks.
next prev parent reply other threads:[~2022-03-23 19:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 18:56 [Intel-gfx] [PATCH] drm/i915/rps: Centralize computation of freq caps Ashutosh Dixit
2022-03-22 19:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/rps: Centralize computation of freq caps (rev2) Patchwork
2022-03-22 19:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22 19:57 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 20:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-23 7:03 ` [Intel-gfx] [PATCH] drm/i915/rps: Centralize computation of freq caps Nilawar, Badal
2022-03-23 19:56 ` Dixit, Ashutosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-06 19:18 Ashutosh Dixit
2022-04-07 13:22 ` Gupta, Anshuman
2022-03-23 19:54 Ashutosh Dixit
2022-03-29 3:59 ` Nilawar, Badal
2022-04-06 10:09 ` Anshuman Gupta
2022-04-06 19:22 ` Dixit, Ashutosh
2022-03-22 21:06 Ashutosh Dixit
2022-03-21 17:56 Ashutosh Dixit
2022-03-21 18:17 ` Lucas De Marchi
2022-03-21 19:12 ` Dixit, Ashutosh
2022-03-22 18:55 ` Dixit, Ashutosh
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=87lex0e93d.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=badal.nilawar@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