From: Imre Deak <imre.deak@intel.com>
To: matthew.s.atwood@intel.com
Cc: intel-gfx@lists.freedesktop.org, marcheu@google.com,
Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com>
Subject: Re: [PATCH] drm/i915: decouple runtime PM enablement from DMC presence
Date: Wed, 14 Jun 2017 20:33:51 +0300 [thread overview]
Message-ID: <20170614173351.GA2072@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <1497460341-2747-1-git-send-email-matthew.s.atwood@intel.com>
On Wed, Jun 14, 2017 at 10:12:21AM -0700, matthew.s.atwood@intel.com wrote:
> From: Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com>
>
> Runtime PM is disabled when DMC firmware is not present. Runtime PM is still
> enabled even if DMC firmware fails to load.
Hm, that would be a bug, but I can't see how it can happen; could you
explain? We get a runtime PM reference in intel_csr_ucode_init() and
only put it if we loaded the firmware successfully.
> This patch enables runtime PM to be enabled if DMC firmware is not present.
Without DMC loaded we want to keep runtime PM disabled.
--Imre
>
> Signed-off-by: Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com>
> ---
> drivers/gpu/drm/i915/intel_csr.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
> index 965988f..3e4e705 100644
> --- a/drivers/gpu/drm/i915/intel_csr.c
> +++ b/drivers/gpu/drm/i915/intel_csr.c
> @@ -411,8 +411,6 @@ static void csr_load_work_fn(struct work_struct *work)
> if (dev_priv->csr.dmc_payload) {
> intel_csr_load_program(dev_priv);
>
> - intel_display_power_put(dev_priv, POWER_DOMAIN_INIT);
> -
> DRM_INFO("Finished loading DMC firmware %s (v%u.%u)\n",
> dev_priv->csr.fw_path,
> CSR_VERSION_MAJOR(csr->version),
> @@ -420,10 +418,11 @@ static void csr_load_work_fn(struct work_struct *work)
> } else {
> dev_notice(dev_priv->drm.dev,
> "Failed to load DMC firmware"
> - " [" FIRMWARE_URL "],"
> - " disabling runtime power management.\n");
> + " [" FIRMWARE_URL "]");
> }
>
> + intel_display_power_put(dev_priv, POWER_DOMAIN_INIT);
> +
> release_firmware(fw);
> }
>
> --
> 2.7.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-14 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:12 [PATCH] drm/i915: decouple runtime PM enablement from DMC presence matthew.s.atwood
2017-06-14 17:33 ` Imre Deak [this message]
2017-06-14 17:40 ` Atwood, Matthew S
2017-06-14 17:55 ` Imre Deak
2017-06-14 20:02 ` Rodrigo Vivi
2017-06-14 20:07 ` Atwood, Matthew S
2017-06-14 20:17 ` Imre Deak
2017-06-15 16:16 ` Atwood, Matthew S
2017-06-15 16:30 ` Imre Deak
2017-06-15 17:20 ` Rodrigo Vivi
2017-06-15 17:38 ` Imre Deak
2017-06-19 18:45 ` Jani Nikula
2017-08-18 1:00 ` Stéphane Marchesin
2017-08-18 9:07 ` Jani Nikula
2017-08-18 14:26 ` Tahvanainen, Jari
2017-08-18 14:35 ` Chris Wilson
2017-08-19 1:00 ` Stéphane Marchesin
2017-06-14 17:40 ` ✗ Fi.CI.BAT: failure for " 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=20170614173351.GA2072@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marcheu@google.com \
--cc=matthew.s.atwood@intel.com \
--cc=matthew.s.atwood@intel.corp-partner.google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox