From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Antti Koskipaa <antti.koskipaa@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v7] drm/i915: Reorganize display pipe register accesses
Date: Tue, 4 Feb 2014 20:20:31 +0200 [thread overview]
Message-ID: <20140204182031.GI3891@intel.com> (raw)
In-Reply-To: <1391516544-2033-1-git-send-email-antti.koskipaa@linux.intel.com>
On Tue, Feb 04, 2014 at 02:22:24PM +0200, Antti Koskipaa wrote:
> RFCv2: Reorganize array indexing so that full offsets can be used as
> is. It makes grepping for registers in i915_reg.h much easier. Also
> move offset arrays to intel_device_info.
>
> v1: Fixed offsets for VLV, proper eDP handling
>
> v2: Fixed BCLRPAT, PIPESRC, PIPECONF and DSP* macros.
>
> v3: Added EDP pipe comment, removed redundant offset arrays for
> MSA_MISC and DDI_FUNC_CTL.
>
> v4: Rename patch and report object size increase.
>
> v5: Change location of commas, add PIPE_EDP into enum pipe
>
> v6: Insert PIPE_EDP_OFFSET into pipe offset array
>
> v7: Set I915_MAX_PIPES back to 3, change more registers accessors
> to use the new macros, get rid of _PIPE_INC and add dev_priv
> as a parameter where required by the new macros.
>
> Upcoming hardware will not have the various display pipe register
> ranges evenly spaced in memory. Change register address calculations
> into array lookups.
>
> Tested on SNB, VLV, IVB, Gen2 and HSW w/eDP.
>
> I left the UMS cruft untouched.
>
> Size differences:
> text data bss dec hex filename
> 596431 4634 56 601121 92c21 i915.ko (new)
> 593199 4634 56 597889 91f81 i915.ko (old)
>
> Signed-off-by: Antti Koskipaa <antti.koskipaa@linux.intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
To elaborate a bit, I fired this up on HSW ULT w/ eDP, IVB w/ HDMI, and
855GM w/ LVDS. I think I also tried HSW and IVB with a another HDMI
monitor plugged in, and the 855GM w/ VGA plugged in.
As added insurance I enabled the reg_rw tracepoint and traced all the
register access we do when loading the driver (w/ fbcon enabled to get
some modesets in the trace). I compared traces between patched and
unpatched kernels and tried to see if there were any significant
differences. Couldn't spot anything apart from a few small differences
in the order of register accesses due parallel activity.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-02-04 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 12:22 [PATCH v7] drm/i915: Reorganize display pipe register accesses Antti Koskipaa
2014-02-04 18:20 ` Ville Syrjälä [this message]
2014-02-04 23:46 ` 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=20140204182031.GI3891@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=antti.koskipaa@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox