LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian W MORRISON <ianwmorrison@gmail.com>
To: "Botello Ortega, Luis" <luis.botello.ortega@intel.com>
Cc: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	"Martinez Monroy, Elio" <elio.martinez.monroy@intel.com>,
	"Vega, Ricardo" <ricardo.vega@intel.com>,
	airlied@linux.ie, Greg KH <gregkh@linuxfoundation.org>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake
Date: Wed, 25 Apr 2018 23:15:26 +0000	[thread overview]
Message-ID: <CAFXWsS8H8V3RvArLnvGF1z_TuojgBU6pDoqBccCHGV=s9DNJfA@mail.gmail.com> (raw)
In-Reply-To: <CAFXWsS87X_QVFSA+BqefknE4x0o=7Edfp1iqdTD81YCcoLHsmQ@mail.gmail.com>

Hi Anusha,

Can I ask if this is on anyone's radar as I'm concerned this patch will
stall otherwise?

I see that the significance of testing with the 4.14 kernel enabled the
firmware to be included in the latest Chrome OS kernel (
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-reviews/jtpHvZOfZ-Q).
It is important to similarly include in the mainline and stable kernels to
facilitate various distros that are now raising bug reports (for example:
https://bugs.launchpad.net/intel/+bug/1760545).

Many thanks,
Ian
On Sun, 22 Apr 2018 at 08:46, Ian W MORRISON <ianwmorrison@gmail.com> wrote:

> On 21 April 2018 at 11:22, Botello Ortega, Luis
> <luis.botello.ortega@intel.com> wrote:
> > Hi all:
> >
> > We tested GLK DMC 1.04 FW in last week of September 2017, using the
latest drm-tip version for that time (4.14.0-rc2) and according to our
results we could declare this FW as acceptable and healthy to be used with
kernel version 4.14 .
> > However, we cannot guarantee quality and healthy of this FW if it is
used in top of current drm-tip kernel (4.17-rc0).
> >
> > Best Regards
> > Luis Botello
> >
> >

> Your measured response is appreciated and raises at least four
> possible alternatives for this patch to proceed:

> 1. It is normal that firmware is *only* tested at a certain point in
> time with the drm-tip version of the mainline kernel so that the
> statement 'firmware X is acceptable and healthy to be used with kernel
> version Y but is not guaranteed with Y+1 or Y+n' always holds true for
> any microarchitecture codename's DMC firmware. Therefore it is
> appropriate for this patch to have a restricted 'Cc:
> stable@vger.kernel.org # 4.14' tag together with an explicit
> 'Tested-by: (in 4.14)' tag.
> 2. As firmware testing was not performed on 4.15 and subsequent
> versions, testing is still required on versions 4.15 through to the
> current RC of version 4.17 for the patch to receive a 'Tested-by:' tag
> together with a 'Cc: stable@vger.kernel.org # 4.14' tag.
> 3. Further firmware testing will only be undertaken for the current RC
> of version 4.17 and on successful completion the patch will only
> receive a 'Tested-by:' tag. A 'Cc: stable@vger.kernel.org' tag is not
> applicable.
> 4. The firmware was not tested on 4.15 and subsequent versions as it's
> functionality was provided by alternative means and therefore the
> patch is only required in version 4.14 and should have a 'Cc:
> stable@vger.kernel.org # 4.14 only' tag together with a restricted
> 'Tested-by: (only in 4.14)' tag.

> Could you indicate which alternative is appropriate? If further
> firmware testing is required (as in points 2 or 3) then can an
> expected completion date be provided?

> Best regards,
> Ian

  reply	other threads:[~2018-04-25 23:15 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
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 [this message]
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='CAFXWsS8H8V3RvArLnvGF1z_TuojgBU6pDoqBccCHGV=s9DNJfA@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=elio.martinez.monroy@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.botello.ortega@intel.com \
    --cc=ricardo.vega@intel.com \
    --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).