From: Anisse Astier <anisse@astier.eu>
To: Alan Cox <alan@linux.intel.com>
Cc: Josh Boyer <jwboyer@redhat.com>,
kernel-team@fedoraproject.org, Dave Airlie <airlied@redhat.com>,
dkline@redhat.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: gma500 opregion/power init order backtrace
Date: Fri, 20 Jul 2012 17:20:44 +0200 [thread overview]
Message-ID: <20120720172044.5ad38413@destiny.ordissimo> (raw)
In-Reply-To: <20120720163247.19578db4@destiny.ordissimo>
On Fri, 20 Jul 2012 16:32:47 +0200, Anisse Astier <anisse@astier.eu> wrote :
> On Tue, 17 Jul 2012 22:12:42 +0100, Alan Cox <alan@linux.intel.com> wrote :
>
> > > I'm wondering if the gma_power_init call can be moved up before
> > > chip_setup is called. Seems so, but I thought I would ping you to see
> > > if you've seen this already.
> >
> > Fixed in the patches that went to Linus.
> Thanks for this ! I was having this 100 scale brightness issue on anther
> hardware.
>
> >
> > I don't have the ACPI backlight working on a lot of systems and don't
> > know why to be honest but the native backlight should work. Of course if
> > the acpi keys are plumbed into the ACPI backlight it's less useful 8)
>
> Can't we just "wire" this to psb-bl in the driver ? There are a few
> drivers in drivers/platform/x86 already sending KEY_BRIGHTNESS{UP,DOWN}
> keycodes.
What I meant is: although these keycodes are already sent by acpi driver
code, is it up to userspace to figure out which backlight driver to use,
or should the kernel modify brightness in psb-bl directly ?
Anisse
next prev parent reply other threads:[~2012-07-20 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 19:26 gma500 opregion/power init order backtrace Josh Boyer
2012-07-17 21:12 ` Alan Cox
2012-07-20 14:32 ` Anisse Astier
2012-07-20 15:20 ` Anisse Astier [this message]
2012-07-23 10:37 ` Alan Cox
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=20120720172044.5ad38413@destiny.ordissimo \
--to=anisse@astier.eu \
--cc=airlied@redhat.com \
--cc=alan@linux.intel.com \
--cc=dkline@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.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.