From: Greg KH <greg@kroah.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Jakub Schmidtke <sjakub@gmail.com>,
acpi4asus-user@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Cleaning asus_oled
Date: Tue, 4 Aug 2009 13:35:49 -0700 [thread overview]
Message-ID: <20090804203549.GA25332@kroah.com> (raw)
In-Reply-To: <71cd59b00908041140j7bd814d2u90585864fe00415e@mail.gmail.com>
On Tue, Aug 04, 2009 at 08:40:10PM +0200, Corentin Chary wrote:
> Hi,
> I'm trying to clean the asus_oled driver, here is my git tree with
> some trivial patchs.
> http://git.iksaif.net/?p=acpi4asus.git;a=shortlog;h=refs/heads/asus_oled
That's great! But note, I need patches in email form, so you are going
to use git format-patch to dig them out for me, right? :)
> Before working deeper, I wanted to discuss about the userspace interface:
>
> > TODO:
> > [...]
> > - audit the userspace interface
> > - sysfs vs. char?
>
> First, should we move asus_oled functionalities in asus-laptop ?
> Then the interface would be in sysfs under
> /sys/devices/platform/asus-laptop/{picture|enable} ?
Is that the way that other drivers of this kind of functionality work
today? If so, yes, that would be good.
> Else we can use /dev/asus_oled, with an ioctl (or a zero-size image)
> to switch the OLED off.
> But I don't think /sys/class/oled is a good place to be, because
> /sys/class is for generic things.
Like /sys/class/video_output? There's got to be some other generic
backlight driver class already, oh, hey, look at /sys/class/backlight!
So, why not just use the backlight interface instead, that way you don't
have to write custom userspace code for this specific platform?
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-04 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 18:40 Cleaning asus_oled Corentin Chary
2009-08-04 20:35 ` Greg KH [this message]
2009-08-05 7:54 ` Corentin Chary
2009-08-06 20:01 ` Greg KH
2009-09-08 21:39 ` Corentin Chary
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=20090804203549.GA25332@kroah.com \
--to=greg@kroah.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjakub@gmail.com \
/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