All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/3] drm/i915/uc: Update drawing for firmware layout
Date: Thu, 25 Jul 2019 13:16:23 -0700	[thread overview]
Message-ID: <8ac751a3-9666-5b82-a298-c4e327a470f2@intel.com> (raw)
In-Reply-To: <20190725141308.24660-2-michal.wajdeczko@intel.com>



On 7/25/19 7:13 AM, Michal Wajdeczko wrote:
> Sphinx was rendering firmware layout as html table, but since
> we want to add sizes relations switch to plain text graphics.
> 
> v2: also update text and do it before move (Daniele)
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

> ---
>   Documentation/gpu/i915.rst                  | 12 ++++----
>   drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 31 ++++++++++-----------
>   2 files changed, 20 insertions(+), 23 deletions(-)
> 
> diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst
> index c2173d120492..3e233f9d675f 100644
> --- a/Documentation/gpu/i915.rst
> +++ b/Documentation/gpu/i915.rst
> @@ -430,6 +430,12 @@ WOPCM Layout
>   GuC
>   ===
>   
> +Firmware Layout
> +-------------------
> +
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> +   :doc: Firmware Layout
> +
>   GuC-specific firmware loader
>   ----------------------------
>   
> @@ -445,12 +451,6 @@ GuC-based command submission
>   .. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>      :internal:
>   
> -GuC Firmware Layout
> --------------------
> -
> -.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> -   :doc: GuC Firmware Layout
> -
>   GuC Address Space
>   -----------------
>   
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h b/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> index 30cca3a29323..108b386c52ec 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> @@ -122,23 +122,20 @@
>   #define GUC_CTL_MAX_DWORDS		(SOFT_SCRATCH_COUNT - 2) /* [1..14] */
>   
>   /**
> - * DOC: GuC Firmware Layout
> + * DOC: Firmware Layout
>    *
> - * The GuC firmware layout looks like this:
> + * The GuC/HuC firmware layout looks like this::
>    *
> - *     +-------------------------------+
> - *     |         uc_css_header         |
> - *     |                               |
> - *     | contains major/minor version  |
> - *     +-------------------------------+
> - *     |             uCode             |
> - *     +-------------------------------+
> - *     |         RSA signature         |
> - *     +-------------------------------+
> - *     |          modulus key          |
> - *     +-------------------------------+
> - *     |          exponent val         |
> - *     +-------------------------------+
> + *      +======================================================================+
> + *      |  Firmware blob                                                       |
> + *      +===============+===============+============+============+============+
> + *      |  CSS header   |     uCode     |  RSA key   |  modulus   |  exponent  |
> + *      +===============+===============+============+============+============+
> + *       <-header size->                 <---header size continued ----------->
> + *       <--- size ----------------------------------------------------------->
> + *                                       <-key size->
> + *                                                    <-mod size->
> + *                                                                 <-exp size->
>    *
>    * The firmware may or may not have modulus key and exponent data. The header,
>    * uCode and RSA signature are must-have components that will be used by driver.
> @@ -155,8 +152,8 @@
>    * 4. Modulus and exponent key are not required by driver. They may not appear
>    *    in fw. So driver will load a truncated firmware in this case.
>    *
> - * HuC firmware layout is same as GuC firmware.
> - * Only HuC version information is saved in a different way.
> + * The only difference between GuC and HuC firmwares is how the version
> + * information is saved.
>    */
>   
>   struct uc_css_header {
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-25 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 14:13 [PATCH v2 1/3] drm/i915: Fix GuC documentation links Michal Wajdeczko
2019-07-25 14:13 ` [PATCH v2 2/3] drm/i915/uc: Update drawing for firmware layout Michal Wajdeczko
2019-07-25 20:16   ` Daniele Ceraolo Spurio [this message]
2019-07-25 20:24     ` Chris Wilson
2019-07-25 14:13 ` [PATCH v2 3/3] drm/i915/uc: Move uc firmware layout definitions to dedicated file Michal Wajdeczko
2019-07-25 15:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915: Fix GuC documentation links Patchwork
2019-07-25 16:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-26  5:47 ` ✗ Fi.CI.IGT: failure " Patchwork

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=8ac751a3-9666-5b82-a298-c4e327a470f2@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@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.