LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian W MORRISON <ianwmorrison@gmail.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake
Date: Fri, 20 Apr 2018 15:47:15 +1000 [thread overview]
Message-ID: <CAFXWsS8o72qgO419muew4ei3VgorYWmGq0k=xPNe1es3DmD0gw@mail.gmail.com> (raw)
In-Reply-To: <152397448099.13647.3490065625139821046@jlahtine-desk.ger.corp.intel.com>
On 18 April 2018 at 00:14, Joonas Lahtinen
<joonas.lahtinen@linux.intel.com> wrote:
> Quoting Jani Nikula (2018-04-17 12:02:52)
>> On Mon, 16 Apr 2018, "Srivatsa, Anusha" <anusha.srivatsa@intel.com> wrote:
>> >>-----Original Message-----
>> >>From: Jani Nikula [mailto:jani.nikula@linux.intel.com]
>> >>Sent: Wednesday, April 11, 2018 5:27 AM
>> >>To: Ian W MORRISON <ianwmorrison@gmail.com>
>> >>Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>; Srivatsa, Anusha
>> >><anusha.srivatsa@intel.com>; Wajdeczko, Michal
>> >><Michal.Wajdeczko@intel.com>; Greg KH <gregkh@linuxfoundation.org>;
>> >>airlied@linux.ie; joonas.lahtinen@linux.intel.com; linux-kernel@vger.kernel.org;
>> >>stable@vger.kernel.org; intel-gfx@lists.freedesktop.org; dri-
>> >>devel@lists.freedesktop.org
>> >>Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for
>> >>Geminilake
<snip>
In summary so far:
Jani:
> NAK on indiscriminate Cc: stable. There are zero guarantees that
> older kernels will work with whatever firmware you throw at them.
> Who tested the firmware with v4.12 and later? We only have the CI
> results against *current* drm-tip. We don't even know about v4.16.
> I'm not going to ack and take responsibility for the stable backports
> unless someone actually comes forward with credible Tested-bys.
Anusha:
> The stable kernel version is 4.12 and beyond.
> It is appropriate to add the CC: stable in my opinion
Joonas:
> And even then, some distros will be surprised of the new MODULE_FIRMWARE
> and will need to update the linux-firmware package, too.
I've performed backport testing and some additional analysis as follows:
The DMC firmware for GLK was initially included in 4.11
(commit: dbb28b5c3d3cb945a63030fab8d3894cf335ce19).
Then the firmware version was upgraded to 1.03 in 4.12
(commit: f4a791819ed00a749a90387aa139706a507aa690).
However MODULE_FIRMWARE for the GLK DMC firmware
was also removed in 4.12
(commit: d9321a03efcda867b3a8c6327e01808516f0acd7)
together with the firmware version being bumped to 1.04
(commit: aebfd1d37194e00d4c417e7be97efeb736cd9c04).
The patch below effectively reverts commit d9321a03 because the GLK
firmware is now available in the linux-firmware repository.
To test stable backports I've used Ubuntu 18.04 (Beta 2) userspace with
both Ubuntu (generic) and self-compiled mainline (patched) kernels.
The conclusion was that the patch works across 4.12 to 4.17-rc1 kernels
additionally displaying a 'Possible missing firmware' message when
installing a kernel with the expected firmware missing.
The following are abridged backport test results:
Scenario: No DMC (glk_dmc_ver1_04.bin) firmware installed in
'/lib/firmware/i915'
Test:Kernel installation ('grep -i dmc' output from 'apt install'):
4.12-generic and 4.15-generic:
No output # as expected
4.12 to 4.17-rc1-patched:
W: Possible missing firmware
/lib/firmware/i915/glk_dmc_ver1_04.bin for module i915
Result: The effect of the patch is to add a 'Possible missing
firmware' message.
Test: Booting ('grep -i dmc' output from 'dmesg'):
4.12-generic:
No output # as expected
4.15-generic:
i915 0000:00:02.0: Direct firmware load for
i915/glk_dmc_ver1_04.bin failed with error -2
i915 0000:00:02.0: Failed to load DMC firmware
i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
i915 0000:00:02.0: DMC firmware homepage:
https://01.org/linuxgraphics/downloads/firmware
4.12-patched:
No output # as expected
4.13 to 4.14-patched:
i915 0000:00:02.0: Direct firmware load for
i915/glk_dmc_ver1_04.bin failed with error -2
i915 0000:00:02.0: Failed to load DMC firmware
[https://01.org/linuxgraphics/downloads/firmware], disabling runtime
power management.
4.15 to 4.17-rc1-patched:
i915 0000:00:02.0: Direct firmware load for
i915/glk_dmc_ver1_04.bin failed with error -2
i915 0000:00:02.0: Failed to load DMC firmware
i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
i915 0000:00:02.0: DMC firmware homepage:
https://01.org/linuxgraphics/downloads/firmware
Result: The effect of the patch does not change existing
(non-patched kernel) messages.
Scenario: DMC (glk_dmc_ver1_04.bin) firmware installed in '/lib/firmware/i915'
Test:Kernel installation ('grep -i dmc' output from 'apt install')
All kernels:
No messages # as expected
Result: The effect of the patch does not change existing messages.
Test" Booting ('grep -i dmc' output from 'dmesg'):
4.12-generic:
No output # as expected
4.15-generic:
i915 0000:00:02.0: Direct firmware load for
i915/glk_dmc_ver1_04.bin failed with error -2
i915 0000:00:02.0: Failed to load DMC firmware
i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
i915 0000:00:02.0: DMC firmware homepage:
https://01.org/linuxgraphics/downloads/firmware
4.12-patched:
No output # as expected
4.13 to 4.17-rc1-patched:
[drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4)
Result: The effect of the patch is to remove the 'Failed to load' message.
Regards,
Ian
next prev parent reply other threads:[~2018-04-20 5:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 4:42 ianwmorrison
2018-04-11 9:24 ` Jani Nikula
2018-04-11 10:41 ` Ian W MORRISON
2018-04-11 12:27 ` Jani Nikula
2018-04-11 13:04 ` Ian W MORRISON
2018-04-16 22:47 ` Srivatsa, Anusha
2018-04-17 9:02 ` Jani Nikula
2018-04-17 14:14 ` Joonas Lahtinen
2018-04-20 5:47 ` Ian W MORRISON [this message]
2018-04-20 7:50 ` Jani Nikula
2018-04-20 8:25 ` Ian W MORRISON
2018-04-20 18:03 ` Rodrigo Vivi
2018-04-20 18:30 ` Srivatsa, Anusha
2018-04-21 1:22 ` Botello Ortega, Luis
2018-04-21 22:46 ` Ian W MORRISON
2018-04-25 23:15 ` Ian W MORRISON
2018-04-27 9:20 ` Jani Nikula
2018-04-30 7:58 ` Joonas Lahtinen
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='CAFXWsS8o72qgO419muew4ei3VgorYWmGq0k=xPNe1es3DmD0gw@mail.gmail.com' \
--to=ianwmorrison@gmail.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=airlied@linux.ie \
--cc=anusha.srivatsa@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--subject='Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).