From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: miku@iki.fi
Subject: Re: [PATCH 2/5] drm/i915: Notify user about outdated dmc firmware
Date: Mon, 21 Sep 2015 11:30:36 +0300 [thread overview]
Message-ID: <876134w4wj.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <87twqo9qmc.fsf@intel.com>
Jani Nikula <jani.nikula@linux.intel.com> writes:
> On Fri, 18 Sep 2015, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
>> If csr/dmc firmware is known to be outdated, notify
>> user.
>
> What would break if we requested a firmware version that works? Or we've
> made it so that we only request the major version because there's not
> supposed to be changes like this between minor versions...?
>
I guess the question is more of a what should we do
if there is only outdated (known bad) firmware available.
Refuse to load and limb onwards, or return with error code
on driver init.
Latter would force firmware and version to be mandatory and the
version to be tightly coupled to kernel driver version.
-Mika
> BR,
> Jani.
>
>
>
>>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_csr.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
>> index 58edc3f..73807c3 100644
>> --- a/drivers/gpu/drm/i915/intel_csr.c
>> +++ b/drivers/gpu/drm/i915/intel_csr.c
>> @@ -45,6 +45,9 @@
>>
>> MODULE_FIRMWARE(I915_CSR_SKL);
>>
>> +#define RECOMMENDED_FW_MAJOR 1
>> +#define RECOMMENDED_FW_MINOR 21
>> +
>> /*
>> * SKL CSR registers for DC5 and DC6
>> */
>> @@ -387,6 +390,12 @@ static void finish_csr_load(const struct firmware *fw, void *context)
>>
>> DRM_DEBUG_KMS("Finished loading %s v%u.%u\n", dev_priv->csr.fw_path,
>> csr->dmc_ver_major, csr->dmc_ver_minor);
>> +
>> + if (csr->dmc_ver_major < RECOMMENDED_FW_MAJOR ||
>> + csr->dmc_ver_minor < RECOMMENDED_FW_MINOR)
>> + DRM_INFO("Outdated dmc firmware found, please upgrade to %u.%u or newer\n",
>> + RECOMMENDED_FW_MAJOR, RECOMMENDED_FW_MINOR);
>> +
>> out:
>> if (fw_loaded)
>> intel_runtime_pm_put(dev_priv);
>> --
>> 2.1.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-21 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 15:17 [PATCH 1/5] drm/i915: Store and print dmc firmware version Mika Kuoppala
2015-09-18 15:17 ` [PATCH 2/5] drm/i915: Notify user about outdated dmc firmware Mika Kuoppala
2015-09-21 7:30 ` Jani Nikula
2015-09-21 8:30 ` Mika Kuoppala [this message]
2015-10-08 9:41 ` Animesh Manna
2015-10-08 12:23 ` Mika Kuoppala
2015-10-08 14:45 ` Animesh Manna
2015-10-13 12:30 ` Dave Gordon
2015-10-22 0:48 ` Marc Herbert
2015-09-23 10:09 ` [PATCH 2/5] drm/i915/skl: Refuse to load " Mika Kuoppala
2015-09-18 15:17 ` [PATCH 3/5] drm/i915: Add dmc firmware version to error state Mika Kuoppala
2015-09-18 15:17 ` [PATCH 4/5] drm/i915: Add pci device revision " Mika Kuoppala
2015-09-18 15:17 ` [PATCH 5/5] drm/i915: Add dmc firmware debugfs status entry Mika Kuoppala
2015-10-08 10:08 ` Animesh Manna
2015-10-21 12:14 ` Mika Kuoppala
2015-10-08 9:56 ` [PATCH 1/5] drm/i915: Store and print dmc firmware version Animesh Manna
2015-10-08 11:03 ` Damien Lespiau
2015-10-08 15:04 ` Damien Lespiau
2015-10-21 13:46 ` Mika Kuoppala
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=876134w4wj.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=miku@iki.fi \
/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.