From: Imre Deak <imre.deak@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Srivatsa, Anusha" <anusha.srivatsa@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/DMC/KBL: Load DMC on KBL using the no_stepping_info array
Date: Wed, 26 Oct 2016 15:32:52 +0300 [thread overview]
Message-ID: <1477485172.32205.17.camel@intel.com> (raw)
In-Reply-To: <1477418441.3029.4.camel@rdvivi-vienna>
On ti, 2016-10-25 at 18:00 +0000, Vivi, Rodrigo wrote:
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> On Mon, 2016-10-24 at 17:28 -0700, Anusha Srivatsa wrote:
> > Currently, for display there is only one DMC image for KBL.
> > Remove the stepping_info table for KBL and use the no_stepping_info
> > array for loading the firmware.
> >
> > v2: Removed the block of code as pointed out by Rodrigo to make the
> > loads as generic as possible.
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
I assume the goal is to simplify the code. kbl_dmc_ver1_01.bin has
indeed only a single *,* entry and I assume it was confirmed that there
is no plan to release KBL firmware images in the future with multiple
stepping entries. With that this looks ok:
Acked-by: Imre Deak <imre.deak@intel.com>
I think it would be good to also emit a warn from the driver if we use
no_stepping_info and there are stepping entries in the firmware image
other than *,* since then we may end up loading the wrong firmware
version.
> > ---
> > drivers/gpu/drm/i915/intel_csr.c | 11 +----------
> > 1 file changed, 1 insertion(+), 10 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_csr.c
> > b/drivers/gpu/drm/i915/intel_csr.c
> > index 1ea0e1f..d7a04bc 100644
> > --- a/drivers/gpu/drm/i915/intel_csr.c
> > +++ b/drivers/gpu/drm/i915/intel_csr.c
> > @@ -168,12 +168,6 @@ struct stepping_info {
> > char substepping;
> > };
> >
> > -static const struct stepping_info kbl_stepping_info[] = {
> > - {'A', '0'}, {'B', '0'}, {'C', '0'},
> > - {'D', '0'}, {'E', '0'}, {'F', '0'},
> > - {'G', '0'}, {'H', '0'}, {'I', '0'},
> > -};
> > -
> > static const struct stepping_info skl_stepping_info[] = {
> > {'A', '0'}, {'B', '0'}, {'C', '0'},
> > {'D', '0'}, {'E', '0'}, {'F', '0'},
> > @@ -194,10 +188,7 @@ intel_get_stepping_info(struct
> > drm_i915_private *dev_priv)
> > const struct stepping_info *si;
> > unsigned int size;
> >
> > - if (IS_KABYLAKE(dev_priv)) {
> > - size = ARRAY_SIZE(kbl_stepping_info);
> > - si = kbl_stepping_info;
> > - } else if (IS_SKYLAKE(dev_priv)) {
> > + if (IS_SKYLAKE(dev_priv)) {
> > size = ARRAY_SIZE(skl_stepping_info);
> > si = skl_stepping_info;
> > } else if (IS_BROXTON(dev_priv)) {
>
> _______________________________________________
> 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:[~2016-10-26 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 0:28 [PATCH] drm/i915/DMC/KBL: Load DMC on KBL using the no_stepping_info array Anusha Srivatsa
2016-10-25 0:46 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-10-25 18:00 ` [PATCH] " Vivi, Rodrigo
2016-10-26 12:32 ` Imre Deak [this message]
2016-10-26 16:13 ` Vivi, Rodrigo
2016-10-26 21:23 ` Vivi, Rodrigo
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=1477485172.32205.17.camel@intel.com \
--to=imre.deak@intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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