All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Kamath <sunil.kamath@intel.com>
To: Animesh Manna <animesh.manna@intel.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 03/18] drm/i915/bxt: Stepping info added for bxt.
Date: Mon, 27 Jul 2015 10:29:20 +0530	[thread overview]
Message-ID: <55B5BAA8.80009@intel.com> (raw)
In-Reply-To: <1437850839-16782-4-git-send-email-animesh.manna@intel.com>

On Sunday 26 July 2015 12:30 AM, Animesh Manna wrote:
> Added stepping info in intel_csr.c which is required to extract
> specific firmware from packaged dmc firmware.
>
> Cc: Vetter, Daniel <daniel.vetter@intel.com>
> Cc: Damien Lespiau <damien.lespiau@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Cc: Sunil Kamath <sunil.kamath@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
>   drivers/gpu/drm/i915/intel_csr.c | 11 +++++++++++
>   1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
> index 1866426..f440299 100644
> --- a/drivers/gpu/drm/i915/intel_csr.c
> +++ b/drivers/gpu/drm/i915/intel_csr.c
> @@ -183,11 +183,19 @@ static const struct stepping_info skl_stepping_info[] = {
>   		{'G', '0'}, {'H', '0'}, {'I', '0'}
>   };
>   
> +static struct stepping_info bxt_stepping_info[] = {
> +		{'A', '0'}, {'A', '1'}, {'A', '2'},
> +		{'B', '0'}, {'B', '1'}, {'B', '2'}
> +};
> +

I understand that these stepping structure is as per present limited info.

>   static char intel_get_stepping(struct drm_device *dev)
>   {
>   	if (IS_SKYLAKE(dev) && (dev->pdev->revision <
>   			ARRAY_SIZE(skl_stepping_info)))
>   		return skl_stepping_info[dev->pdev->revision].stepping;
> +	else if (IS_BROXTON(dev) && (dev->pdev->revision <
> +			ARRAY_SIZE(bxt_stepping_info)))
> +		return bxt_stepping_info[dev->pdev->revision].stepping;
>   	else
>   		return -ENODATA;
>   }
> @@ -197,6 +205,9 @@ static char intel_get_substepping(struct drm_device *dev)
>   	if (IS_SKYLAKE(dev) && (dev->pdev->revision <
>   			ARRAY_SIZE(skl_stepping_info)))
>   		return skl_stepping_info[dev->pdev->revision].substepping;
> +	else if (IS_BROXTON(dev) && (dev->pdev->revision <
> +			ARRAY_SIZE(bxt_stepping_info)))
> +		return bxt_stepping_info[dev->pdev->revision].substepping;
>   	else
>   		return -ENODATA;
>   }

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-27  4:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 19:00 [PATCH 00/18] Redesign of dmc firmware loading Animesh Manna
2015-07-25 19:00 ` [PATCH 01/18] drm/i915/bxt: Path added of dmc firmware ver1 for BXT Animesh Manna
2015-07-27  4:51   ` Sunil Kamath
2015-07-25 19:00 ` [PATCH 02/18] drm/i915/bxt: Modified HAS_CSR, added support " Animesh Manna
2015-07-27  4:53   ` Sunil Kamath
2015-07-25 19:00 ` [PATCH 03/18] drm/i915/bxt: Stepping info added for bxt Animesh Manna
2015-07-27  4:59   ` Sunil Kamath [this message]
2015-07-25 19:00 ` [PATCH 04/18] drm/i915/gen9: block disable call for pw1 if dmc firmware is present Animesh Manna
2015-07-27  8:48   ` Daniel Vetter
2015-07-28  7:57     ` Daniel Vetter
2015-07-28 10:28       ` Sunil Kamath
2015-07-25 19:00 ` [PATCH 05/18] drm/i915/gen9: csr_init after runtime pm enable Animesh Manna
2015-07-28  7:56   ` Daniel Vetter
2015-07-25 19:00 ` [PATCH 06/18] drm/i915/gen9: move assert_csr_loaded into intel_rpm.c Animesh Manna
2015-07-25 19:00 ` [PATCH 07/18] drm/i915/gen9: Remove csr.state, csr_lock and related code Animesh Manna
2015-07-25 19:00 ` [PATCH 08/18] drm/i915/gen9: Align line continuations in intel_csr.c Animesh Manna
2015-07-25 19:00 ` [PATCH 09/18] drm/i915/gen9: Simplify csr loading failure printing Animesh Manna
2015-07-25 19:00 ` [PATCH 10/18] drm/i915/gen9: extract parse_csr_fw Animesh Manna
2015-07-25 19:00 ` [PATCH 11/18] drm/i915/gen9: Don't try to load garbage dmc firmware on resume Animesh Manna
2015-07-25 19:00 ` [PATCH 12/18] drm/i915/gen9: Use dev_priv in csr functions Animesh Manna
2015-07-25 19:00 ` [PATCH 13/18] drm/i915: Use request_firmware and our own async work Animesh Manna
2015-07-25 19:00 ` [PATCH 14/18] drm/i915/gen9: Use flush_work to synchronize with dmc loader Animesh Manna
2015-07-28  8:09   ` Daniel Vetter
2015-07-25 19:00 ` [PATCH 15/18] drm/i915/skl: Making DC6 entry is the last call in suspend flow Animesh Manna
2015-07-30  7:06   ` Sunil Kamath
2015-07-30 15:28   ` Nagaraju, Vathsala
2015-07-25 19:00 ` [PATCH 16/18] drm/i915/skl: Do not disable cdclk PLL if csr firmware is present Animesh Manna
2015-07-30  7:04   ` Sunil Kamath
2015-07-25 19:00 ` [PATCH 17/18] drm/i915/skl: Removed csr firmware load in resume path Animesh Manna
2015-07-28 11:23   ` Sunil Kamath
2015-07-29 10:57     ` Sunil Kamath
2015-07-29 11:10     ` Sunil Kamath
2015-07-30  7:04       ` Sunil Kamath
2015-07-25 19:00 ` [PATCH 18/18] drm/i915/gen9: Removed byte swapping for csr firmware Animesh Manna
2015-07-26  1:56   ` shuang.he
2015-07-28  8:08   ` Nagaraju, Vathsala
2015-07-28 11:09     ` Sunil Kamath
2015-07-30  7:04       ` Sunil Kamath
2015-07-30 15:24   ` Nagaraju, Vathsala
2015-07-27  4:37 ` [PATCH 00/18] Redesign of dmc firmware loading Sunil Kamath

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=55B5BAA8.80009@intel.com \
    --to=sunil.kamath@intel.com \
    --cc=animesh.manna@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.