public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: mengdong.lin@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] intel_audio_dump: add support for Valleyview
Date: Fri, 7 Mar 2014 09:49:28 +0100	[thread overview]
Message-ID: <20140307084928.GD25837@phenom.ffwll.local> (raw)
In-Reply-To: <cover.1393947538.git.mengdong.lin@intel.com>

On Tue, Mar 04, 2014 at 11:17:33AM -0500, mengdong.lin@intel.com wrote:
> From: Mengdong Lin <mengdong.lin@intel.com>
> 
> Layout of display and audio registers can be same for different Intel GPUs,
> so we want maximum code sharing when adding support for VLV.
> 
> This patch set:
> - support using base address plus an offset to dump registers
> - share common audio dump code for Ironlake, Haswell and Broadwell
> - add support for Valleyview, by reusing Ironlake code.
> - adjust code algnment
> 
> The patches are reviewed by Xiang Haihao.
> 
> Now OEM Baytrail machines are sent to OSV like Ubuntu, so we need this for
> customer support.

When you push feature work like this please also update the NEWS file with
a short entry. We use that for the i-g-t release announcements. I've done
this for now.

Thanks, Daniel
> 
> Mengdong Lin (7):
>   intel_audio_dump: support using base address plus an offset to dump
>     registers
>   intel_audio_dump: move definitions of transcoder/pipe/port/converter
>     earlier
>   intel_audio_dump: define IS_HASWELL_PLUS to cover Haswell and its
>     successors
>   intel_audio_dump: define get_num_pipes() to get number of pipes for a
>     device ID
>   intel_audio_dump: share common audio dump code for Ironlake, Haswell &
>     Broadwell
>   intel_audio_dump: adjust code alignment
>   intel_audio_dump: add support for Valleyview
> 
>  tools/intel_audio_dump.c | 2011 ++++++++++++++++++++++++----------------------
>  1 file changed, 1041 insertions(+), 970 deletions(-)
> 
> -- 
> 1.8.1.2
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      parent reply	other threads:[~2014-03-07  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 16:17 [PATCH 0/7] intel_audio_dump: add support for Valleyview mengdong.lin
2014-03-04 16:17 ` [PATCH 1/7] intel_audio_dump: support using base address plus an offset to dump registers mengdong.lin
2014-03-04 16:28 ` [PATCH 2/7] intel_audio_dump: move definitions of transcoder/pipe/port/converter earlier mengdong.lin
2014-03-04 16:28 ` [PATCH 3/7] intel_audio_dump: define IS_HASWELL_PLUS to cover Haswell and its successors mengdong.lin
2014-03-04 16:29 ` [PATCH 4/7] intel_audio_dump: define get_num_pipes() to get number of pipes for a device ID mengdong.lin
2014-03-04 16:29 ` [PATCH 5/7] intel_audio_dump: share common audio dump code for Ironlake, Haswell & Broadwell mengdong.lin
2014-03-04 16:29 ` [PATCH 6/7] intel_audio_dump: adjust code alignment mengdong.lin
2014-03-04 16:29 ` [PATCH 7/7] intel_audio_dump: add support for Valleyview mengdong.lin
2014-03-07  8:49 ` Daniel Vetter [this message]

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=20140307084928.GD25837@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mengdong.lin@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