public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mzxreary@0pointer.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] acpi,backlight: MSI S270 laptop support - driver
Date: Thu, 10 Aug 2006 13:46:47 +0200	[thread overview]
Message-ID: <20060810114647.GA18242@tango.0pointer.de> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB60133D741@hdsmsx411.amr.corp.intel.com>

On Thu, 10.08.06 05:36, Brown, Len (len.brown@intel.com) wrote:

> Lennart,

Hi!

> 
> Your s270 platform driver needs a different home in the source tree
> outside of drivers/acpi/, and the patch that adds it must add an entry
> to MAINTAINERS.

If you look closely you'll see that the patch already adds a new
entry to MAINTAINERS.

I put the the driver in drivers/acpi/ because it relies heavily on the
ACPI EC stuff. But OK, what is a better place for the driver? 

drivers/char/ 
  It doesn't even register any character device.

drivers/video/backlight/
  It doesn't just do backlight control.

drivers/misc/
  Seems to be the last resort for everything that doesn't fit it
  otherwise.

Unless anyone has a better idea I will move it to drivers/misc/, then.

> lcd brightness platform support should talk to the existing
> backlight stuff under sysfs.

It already does exactly that, you can find the backlight class driver
in /sys/class/backlight/s270/.

I cannot map the "automatic brightness control" feature to the
backlight class driver, that's why I duplicated the brightness stuff
in /proc/acpi/s270/.

> wlan and bluetooth indicators/controls need to appear under
> generic places under sysfs -- not under platform specific
> files under /proc/acpi.

What are those "generic" places? I cannot think of any besides a
"platform" device.

> Yes, the existing platform specific drivers such as asus, toshiba, and
> ibm
> are bad examples.

Ok, I will move the /proc/acpi/s270/ stuff to a sysfs platform device,
then. I will cook up another patch shortly.

Any ideas on that ec_transaction() patch I sent earlier?

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/

  reply	other threads:[~2006-08-10 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  9:36 [PATCH 2/2] acpi,backlight: MSI S270 laptop support - driver Brown, Len
2006-08-10 11:46 ` Lennart Poettering [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10 16:15 Brown, Len
2006-08-10 16:48 ` Lennart Poettering
2006-08-10  1:05 Lennart Poettering
2006-08-15 12:42 ` Thomas Renninger
2006-08-15 13:47   ` Lennart Poettering

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=20060810114647.GA18242@tango.0pointer.de \
    --to=mzxreary@0pointer.de \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox