public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/skl: Implementation of SKL display power well support
Date: Wed, 04 Feb 2015 16:29:33 +0200	[thread overview]
Message-ID: <1423060173.6792.9.camel@intel.com> (raw)
In-Reply-To: <20150204142416.GF16355@strange.ger.corp.intel.com>

On ke, 2015-02-04 at 14:24 +0000, Damien Lespiau wrote:
> On Wed, Feb 04, 2015 at 04:20:28PM +0200, Imre Deak wrote:
> > On ke, 2015-02-04 at 13:53 +0000, Damien Lespiau wrote:
> > > On Tue, Feb 03, 2015 at 01:06:31AM +0200, Imre Deak wrote:
> > > > > +static struct i915_power_well skl_power_wells[] = {
> > > > > +	{
> > > > > +		.name = "always-on",
> > > > > +		.always_on = 1,
> > > > > +		.domains = SKL_DISPLAY_ALWAYS_ON_POWER_DOMAINS,
> > > > > +		.ops = &i9xx_always_on_power_well_ops,
> > > > > +	},
> > > > > +	{
> > > > > +		.name = "power well 1",
> > > > > +		.domains = SKL_DISPLAY_POWERWELL_1_POWER_DOMAINS,
> > > > > +		.ops = &skl_power_well_ops,
> > > > > +		.data = SKL_DISP_PW_1,
> > > > > +	},
> > > 
> > > snip
> > > 
> > > > > +	{
> > > > > +		.name = "MISC IO power well",
> > > > > +		.domains = SKL_DISPLAY_MISC_IO_POWER_DOMAINS,
> > > > > +		.ops = &skl_power_well_ops,
> > > > > +		.data = SKL_DISP_PW_MISC_IO,
> > > > > +	}
> > > > 
> > > > Again, since the recent bspec change the misc IO power well should be
> > > > enabled before anything else, so it needs to be listed before "power
> > > > well 1" on the list.
> > > 
> > > So this one was causing problems. When I try to enabled MISC IO before
> > > PW1, the request times out. Enabling MISC IO just right after PW1 seems
> > > to work fine though.
> > 
> > Ok. Bspec doesn't say anything about the ordering between PW1 and MISC
> > IO, just that you have to enable them together and wait for PG1 fuse
> > afterwards. How about then moving the MISC IO power well right after PW1
> > in the list and wait for the PG1 fuse after enabling MISC IO?
>  
> I think we can even set the 2 requests in the same write and it should
> do the right thing (and so merge the two power wells). That's really a
> detail though and as the current code it seems to work, I'll leave such
> refinements for later/if needed.

Yes, I had the same thought, agreed that it could be done as a
follow-up.

--Imre

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-04 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 15:57 [PATCH 0/2] Power well support for SKL Damien Lespiau
2015-01-16 15:57 ` [PATCH 1/2] drm/i915/skl: Adding power domains for AUX controllers Damien Lespiau
2015-01-20 10:11   ` Daniel Vetter
2015-01-16 15:57 ` [PATCH 2/2] drm/i915/skl: Implementation of SKL display power well support Damien Lespiau
2015-01-17 10:08   ` shuang.he
2015-02-02 23:06   ` Imre Deak
2015-02-04 13:53     ` Damien Lespiau
2015-02-04 14:20       ` Imre Deak
2015-02-04 14:23         ` Imre Deak
2015-02-04 14:24         ` Damien Lespiau
2015-02-04 14:29           ` Imre Deak [this message]
2015-02-04 13:57     ` [PATCH 2/2 v10] " Damien Lespiau
2015-02-04 14:19       ` Daniel Vetter

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=1423060173.6792.9.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=damien.lespiau@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