All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"mathew.j.martineau@linux.intel.com"
	<mathew.j.martineau@linux.intel.com>
Subject: Re: [PATCH] drm/i915/skl: Fix DMC load on Skylake J0 and K0
Date: Thu, 28 Jan 2016 23:26:43 +0000	[thread overview]
Message-ID: <1454023602.12448.100.camel@intel.com> (raw)
In-Reply-To: <1454023163-25469-1-git-send-email-mathew.j.martineau@linux.intel.com>


First of all:

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

I've checked with DMC folks that DMC 1.23 that we are currently using
and the following releases support J0 and K0.

With this patch we are covering all SKL steppings we know so far, but
besides being concern with new steppings appearing at any moment I'm
mostly concerned about KBL where I just saw a KBL revid=8 and we were
considering revid=0 as KBL H0. So I'm asking myself if we do have
better ways of handling this and preferably killing this table.

In case someone have a good idea please let me know.

But for now we need to move fast with this patch.

Thanks,
Rodrigo.

On Thu, 2016-01-28 at 15:19 -0800, Mat Martineau wrote:
> The driver does not load firmware for unknown steppings, so these new
> steppings must be added to the list.
> 
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/intel_csr.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_csr.c 
> b/drivers/gpu/drm/i915/intel_csr.c
> index 9bb63a8..450bab7 100644
> --- a/drivers/gpu/drm/i915/intel_csr.c
> +++ b/drivers/gpu/drm/i915/intel_csr.c
> @@ -177,7 +177,8 @@ static const struct stepping_info 
> kbl_stepping_info[] = {
>  static const struct stepping_info skl_stepping_info[] = {
>  	{'A', '0'}, {'B', '0'}, {'C', '0'},
>  	{'D', '0'}, {'E', '0'}, {'F', '0'},
> -	{'G', '0'}, {'H', '0'}, {'I', '0'}
> +	{'G', '0'}, {'H', '0'}, {'I', '0'},
> +	{'J', '0'}, {'K', '0'}
>  };
>  
>  static const struct stepping_info bxt_stepping_info[] = {
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-28 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 23:19 [PATCH] drm/i915/skl: Fix DMC load on Skylake J0 and K0 Mat Martineau
2016-01-28 23:26 ` Vivi, Rodrigo [this message]
2016-02-01 16:01   ` Mat Martineau
2016-02-01 17:00     ` Vivi, Rodrigo
2016-01-29 11:30 ` ✗ Fi.CI.BAT: failure for " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2016-05-05 18:04 [PATCH] " Mat Martineau

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=1454023602.12448.100.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mathew.j.martineau@linux.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 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.