From: Yu Dai <yu.dai@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add GuC css header parser
Date: Thu, 03 Sep 2015 09:52:50 -0700 [thread overview]
Message-ID: <55E87AE2.2060506@intel.com> (raw)
In-Reply-To: <87k2s80x9y.fsf@intel.com>
On 09/03/2015 12:36 AM, Jani Nikula wrote:
> On Thu, 03 Sep 2015, yu.dai@intel.com wrote:
> > From: Alex Dai <yu.dai@intel.com>
> >
> > By using information from GuC css header, we can eliminate some
> > hard code w.r.t size of some components of firmware.
> >
> > Signed-off-by: Alex Dai <yu.dai@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_guc.h | 2 +-
> > drivers/gpu/drm/i915/intel_guc_fwif.h | 36 +++++++++++++
> > drivers/gpu/drm/i915/intel_guc_loader.c | 91 ++++++++++++++++++++++-----------
> > 3 files changed, 98 insertions(+), 31 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_guc.h b/drivers/gpu/drm/i915/intel_guc.h
> > index 4ec2d27..e1389fc 100644
> > --- a/drivers/gpu/drm/i915/intel_guc.h
> > +++ b/drivers/gpu/drm/i915/intel_guc.h
> > @@ -71,6 +71,7 @@ struct intel_guc_fw {
> > struct drm_i915_gem_object * guc_fw_obj;
> > enum intel_guc_fw_status guc_fw_fetch_status;
> > enum intel_guc_fw_status guc_fw_load_status;
> > + struct guc_css_header guc_fw_header;
> >
> > uint16_t guc_fw_major_wanted;
> > uint16_t guc_fw_minor_wanted;
> > @@ -80,7 +81,6 @@ struct intel_guc_fw {
> >
> > struct intel_guc {
> > struct intel_guc_fw guc_fw;
> > -
> > uint32_t log_flags;
> > struct drm_i915_gem_object *log_obj;
> >
> > diff --git a/drivers/gpu/drm/i915/intel_guc_fwif.h b/drivers/gpu/drm/i915/intel_guc_fwif.h
> > index e1f47ba..d6cb4e8 100644
> > --- a/drivers/gpu/drm/i915/intel_guc_fwif.h
> > +++ b/drivers/gpu/drm/i915/intel_guc_fwif.h
> > @@ -122,6 +122,42 @@
> >
> > #define GUC_CTL_MAX_DWORDS (GUC_CTL_RSRVD + 1)
> >
> > +struct guc_css_header {
> > + uint32_t module_type;
> > + uint32_t header_len; /* header length plus size of all other keys */
> > + uint32_t header_version;
> > + uint32_t module_id;
> > + uint32_t module_vendor;
> > + union {
> > + struct {
> > + uint8_t day;
> > + uint8_t month;
> > + uint16_t year;
> > + };
> > + uint32_t date;
> > + };
> > + uint32_t size; /* uCode size plus header_len */
> > + uint32_t key_size;
> > + uint32_t modulus_size;
> > + uint32_t exponent_size;
> > + union {
> > + struct {
> > + uint8_t hour;
> > + uint8_t min;
> > + uint16_t sec;
> > + };
> > + uint32_t time;
> > + };
> > +
> > + char username[8];
> > + char buildnumber[12];
> > + uint32_t device_id;
> > + uint32_t guc_sw_version;
> > + uint32_t prod_preprod_fw;
> > + uint32_t reserved[12];
> > + uint32_t header_info;
> > +};
>
> Drive-by review, this will need __packed.
>
>
Yes, will correct this in next version. Thanks, -Alex
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-03 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:52 [PATCH] drm/i915: Add GuC css header parser yu.dai
2015-09-03 7:36 ` Jani Nikula
2015-09-03 16:52 ` Yu Dai [this message]
2015-09-04 8:13 ` Daniel Vetter
2015-09-04 20:45 ` [PATCH v1] " yu.dai
2015-09-15 23:28 ` [PATCH 02/15] drm/i915/guc: " yu.dai
2015-09-25 14:36 ` Jani Nikula
2015-09-28 7:38 ` Daniel Vetter
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=55E87AE2.2060506@intel.com \
--to=yu.dai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox