From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Oscar Mateo <oscar.mateo@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC] drm/i915: Allow the UMD to configure their own power clock state
Date: Thu, 11 May 2017 16:09:03 +0300 [thread overview]
Message-ID: <1494508143.4542.31.camel@linux.intel.com> (raw)
In-Reply-To: <b09b4894-c436-7e6f-cb6b-0dfdd507deb9@intel.com>
On ke, 2017-05-10 at 08:33 +0000, Oscar Mateo wrote:
>
>
> On 05/10/2017 01:28 PM, Daniel Vetter wrote:
> >
> > On Wed, May 10, 2017 at 2:59 PM, Joonas Lahtinen
> > <joonas.lahtinen@linux.intel.com> wrote:
> > >
> > > >
> > > > @@ -841,6 +847,11 @@ static int gen9_init_workarounds(struct
> > > > intel_engine_cs *engine)
> > > > if (ret)
> > > > return ret;
> > > >
> > > > + /* Allow the UMD to configure their own power clock state
> > > > */
> > > > + ret = wa_ring_whitelist_reg(engine,
> > > > GEN8_R_PWR_CLK_STATE);
> > > > + if (ret)
> > > > + return ret;
> > > This is not a workaround, so it should be part of the cmd parser
> > > and
> > > have an userspace.
>
> cmd parser? This is Gen8+, so the cmd parser shouldn't even be
> active.
> Or am I missing something?
That's correct, my bad.
>
> >
> > Yeah, the "This allows userspace ..." start of the commit message
> > should have been a dead giveaway that we do indeed need the
> > userspace
> > patch for this too.
> > -Daniel
>
> Yes, I got the memo :)
> Dmitry has opened a ticket against intel-vaapi-driver
> (https://github.com/01org/intel-vaapi-driver/issues/152) so hopefully
> we
> will have a userspace soon.
So with the userspace, we can merge.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-11 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 15:07 [RFC] drm/i915: Allow the UMD to configure their own power clock state Oscar Mateo
2017-05-02 22:24 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-10 12:59 ` [RFC] " Joonas Lahtinen
2017-05-10 13:28 ` Daniel Vetter
2017-05-10 8:33 ` Oscar Mateo
2017-05-11 13:09 ` Joonas Lahtinen [this message]
2017-05-10 13:47 ` Mika Kuoppala
2017-05-10 14:09 ` Michał Winiarski
2017-05-10 8:29 ` Oscar Mateo
2017-05-10 14:26 ` Chris Wilson
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=1494508143.4542.31.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.