From: Adam Jackson <ajax@redhat.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: marcheu@chromium.org, olofj@chromium.org,
dri-devel@lists.freedesktop.org, mdhayter@chromium.org
Subject: Re: [PATCH] drm: Add downclock quirk for Samsung LTN121AT10-301
Date: Wed, 30 May 2012 10:16:43 -0400 [thread overview]
Message-ID: <4FC62BCB.3000500@redhat.com> (raw)
In-Reply-To: <CAOw6vbJ2+C5X9rtiSkfFbe+jis_ZUvo9kH1jES5d41Jx=airDw@mail.gmail.com>
On 5/30/12 8:05 AM, Sean Paul wrote:
> Yes, definitely. The reason I can't set it via xrandr (easily) is
> because we look for lvds downclock modes (in i915) on the driver init.
> Since the driver initializes way before we have a chance to add a new
> mode via xrandr, the driver won't have a downclock mode.
>
> I suppose the other option is to hack the i915 driver to allow a
> downclocked mode to be added after it's been initialized. I haven't
> looked into this solution, it might be worth investigating.
Just so I'm clear, is what you're looking for "I want this pair of
timings, with the driver magically switching between them"? If all you
wanted was the lower clock speed all the time you could just, you know,
do that, so I assume that's not what you're after.
If binding two timings together like that is what you want, then that
seems like a pretty reasonable device-specific ioctl at first glance. I
think the only thing to be careful of would be copying the slower
timings into the driver private of the faster, rather than keeping a
pointer or copy of the object id, since modes aren't refcounted.
How big of a power savings do you see with this? Wondering if it's
worth trying to make some common tooling for finding downclocked modes,
if it's going to be worthwhile on multiple panels.
- ajax
next prev parent reply other threads:[~2012-05-30 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 15:06 [PATCH] drm: Add downclock quirk for Samsung LTN121AT10-301 Sean Paul
2012-05-28 17:20 ` Sean Paul
2012-05-29 14:43 ` Alex Deucher
2012-05-29 20:33 ` Sean Paul
2012-05-29 21:23 ` Alex Deucher
2012-05-30 0:38 ` Sean Paul
2012-05-30 5:06 ` Rafał Miłecki
2012-05-30 12:05 ` Sean Paul
2012-05-30 14:16 ` Adam Jackson [this message]
2012-05-30 15:21 ` Sean Paul
2012-05-31 7:09 ` Daniel Vetter
2012-05-31 13:24 ` Sean Paul
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=4FC62BCB.3000500@redhat.com \
--to=ajax@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=marcheu@chromium.org \
--cc=mdhayter@chromium.org \
--cc=olofj@chromium.org \
--cc=seanpaul@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.