From: "Antti Koskipää" <antti.koskipaa@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Clean up display pipe register accesses
Date: Mon, 27 Jan 2014 14:51:53 +0200 [thread overview]
Message-ID: <52E65669.7070105@linux.intel.com> (raw)
In-Reply-To: <20140127112139.GA2508@nuc-i3427.alporthouse.com>
On 01/27/14 13:21, Chris Wilson wrote:
> On Mon, Jan 27, 2014 at 01:17:25PM +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.
>>
>> PATCHv1: Fixed offsets for VLV
>>
>> Upcoming hardware will not have the various display pipe register
>> ranges evenly spaced in memory. Change register address calculations
>> into array lookups.
>>
>> Tested on SandyBridge and Valleyview
>
> Please also report changes in object size. If we have people complaining
> that i915.ko is too big, it helps to point why.
> -Chris
Do you want this to be reported in the commit message, or where?
bloat-o-meter says:
add/remove: 0/0 grow/shrink: 88/10 up/down: 3326/-518 (2808)
--
- Antti
next prev parent reply other threads:[~2014-01-27 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 11:17 [PATCH] drm/i915: Clean up display pipe register accesses Antti Koskipaa
2014-01-27 11:20 ` Antti Koskipää
2014-01-27 11:21 ` Chris Wilson
2014-01-27 12:51 ` Antti Koskipää [this message]
2014-01-27 12:54 ` Chris Wilson
2014-01-27 11:22 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 12:25 Antti Koskipaa
2014-01-22 6:50 ` Barbalho, Rafael
2014-01-24 12:13 ` Antti Koskipää
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=52E65669.7070105@linux.intel.com \
--to=antti.koskipaa@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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