From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: imre.deak@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add more keywords to firmware loading message
Date: Mon, 21 Nov 2016 14:54:48 +0200 [thread overview]
Message-ID: <87mvgtuh5z.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1479293100.20526.17.camel@intel.com>
Imre Deak <imre.deak@intel.com> writes:
> On ke, 2016-11-16 at 11:33 +0200, Mika Kuoppala wrote:
>> To find out what firmware we actually loaded (from dmesg) the explicit
>> 'dmc' and 'firmware' are missing from the info printout. Add them.
>>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> Reviewed-by: Imre Deak <imre.deak@intel.com>
Pushed. Thanks for review.
>
>> ---
>> drivers/gpu/drm/i915/intel_csr.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
>> index d7a04bc..10e9abc 100644
>> --- a/drivers/gpu/drm/i915/intel_csr.c
>> +++ b/drivers/gpu/drm/i915/intel_csr.c
>> @@ -405,7 +405,7 @@ static void csr_load_work_fn(struct work_struct *work)
>>
>> intel_display_power_put(dev_priv, POWER_DOMAIN_INIT);
>>
>> - DRM_INFO("Finished loading %s (v%u.%u)\n",
>> + DRM_INFO("Finished loading DMC firmware %s (v%u.%u)\n",
>> dev_priv->csr.fw_path,
>> CSR_VERSION_MAJOR(csr->version),
>> CSR_VERSION_MINOR(csr->version));
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-21 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 9:33 [PATCH] drm/i915: Add more keywords to firmware loading message Mika Kuoppala
2016-11-16 10:45 ` Imre Deak
2016-11-21 12:54 ` Mika Kuoppala [this message]
2016-11-16 11:16 ` ✓ Fi.CI.BAT: success 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=87mvgtuh5z.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=imre.deak@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