From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/dmc: DMC 1.07 for Cannonlake
Date: Thu, 21 Dec 2017 11:26:48 -0800 [thread overview]
Message-ID: <20171221192648.lf3fa45op2p2rrtb@intel.com> (raw)
In-Reply-To: <43D4F724E12AB6478FC1572B3FBE89D075CCCA41@IRSMSX106.ger.corp.intel.com>
On Thu, Dec 21, 2017 at 12:08:15PM +0000, Saarinen, Jani wrote:
>
>
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
> > Anusha Srivatsa
> > Sent: torstai 21. joulukuuta 2017 3.38
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Subject: [Intel-gfx] [PATCH] drm/i915/dmc: DMC 1.07 for Cannonlake
> >
> > There is a new version of DMC available for KBL.
> For CNL you mean?
With this fixed feel free to use:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Jani, these results we got from CI are already with fw applied?
Although CNL is on blacklist still right?! :(
> >
> > The release notes mentions:
> > 1. Fix for the issue where DC_STATE was getting enabled even when disabled by
> > driver causing data corruption
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_csr.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
> > index 7fe4aac0..ed256de 100644
> > --- a/drivers/gpu/drm/i915/intel_csr.c
> > +++ b/drivers/gpu/drm/i915/intel_csr.c
> > @@ -37,8 +37,8 @@
> > #define I915_CSR_GLK "i915/glk_dmc_ver1_04.bin"
> > #define GLK_CSR_VERSION_REQUIRED CSR_VERSION(1, 4)
> >
> > -#define I915_CSR_CNL "i915/cnl_dmc_ver1_06.bin"
> > -#define CNL_CSR_VERSION_REQUIRED CSR_VERSION(1, 6)
> > +#define I915_CSR_CNL "i915/cnl_dmc_ver1_07.bin"
> > +#define CNL_CSR_VERSION_REQUIRED CSR_VERSION(1, 7)
> >
> > #define I915_CSR_KBL "i915/kbl_dmc_ver1_04.bin"
> > MODULE_FIRMWARE(I915_CSR_KBL);
> > --
> > 2.7.4
> >
> > _______________________________________________
> > 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:[~2017-12-21 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 1:37 [PATCH] CNL DMC v1.07 Anusha Srivatsa
2017-12-21 1:37 ` [PATCH] drm/i915/dmc: DMC 1.07 for Cannonlake Anusha Srivatsa
2017-12-21 12:08 ` Saarinen, Jani
2017-12-21 19:26 ` Rodrigo Vivi [this message]
2017-12-21 20:31 ` Saarinen, Jani
2017-12-21 1:57 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-21 3:43 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-21 21:07 ` ✓ Fi.CI.BAT: " Patchwork
2017-12-22 7:31 ` Saarinen, Jani
2017-12-21 22:19 ` ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-12-23 0:08 [PATCH] " Anusha Srivatsa
2017-12-28 16:16 ` Rodrigo Vivi
2018-01-03 21:22 Anusha Srivatsa
2018-01-04 7:52 ` Saarinen, Jani
2018-01-04 23:27 ` Srivatsa, Anusha
2018-01-03 23:00 Anusha Srivatsa
2018-01-04 23:51 Anusha Srivatsa
2018-01-05 0:30 ` Rodrigo Vivi
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=20171221192648.lf3fa45op2p2rrtb@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@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