Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
	Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: Abstract backlight registers a bit
Date: Mon, 21 Oct 2013 15:48:16 -0700	[thread overview]
Message-ID: <20131021224816.GG755@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uFa8q5o4s=kzYr1Z-kap+GPA4JF1xmrA2Cgn95ZSxSFMQ@mail.gmail.com>

On Tue, Oct 22, 2013 at 12:30:11AM +0200, Daniel Vetter wrote:
> On Mon, Oct 21, 2013 at 7:35 PM, Ben Widawsky
> <benjamin.widawsky@intel.com> wrote:
> > Many GENs generally perform the same actions just on different
> > registers. This is true going forward as well. To ease the transition a
> > bit, extract the common code where possible.
> >
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> 
> Imo we should just switch to vtables or something like that, since
> it's not just the register that changes, but also the meaning of the
> different bits in the registers themselves and the logic to drive
> stuff. We've often had regression-galore in this code and strictly
> separating different platforms should help. I hope.
> -Daniel

I do not disagree. I have neither the skill, time, not inclination to do
that properly, and I really only care about patch 2. The cleanup here
makes the next patch slightly nicer, but I can live with whatever.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-10-21 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 17:35 [PATCH 1/2] drm/i915: Abstract backlight registers a bit Ben Widawsky
2013-10-21 22:30 ` Daniel Vetter
2013-10-21 22:48   ` Ben Widawsky [this message]
2013-10-21 23:57     ` 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=20131021224816.GG755@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=benjamin.widawsky@intel.com \
    --cc=daniel@ffwll.ch \
    --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