linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-kernel@vger.kernel.org
Cc: Chris Eastwood <chris2027@gmail.com>, gregkh@linuxfoundation.org
Subject: Re: support for Intel Atom based QNAP LEDs/buttons/buzzer in Linux?
Date: Sun, 13 Oct 2013 18:19:35 -0700	[thread overview]
Message-ID: <525B46A7.8000605@roeck-us.net> (raw)
In-Reply-To: <1381707976.3914.22.camel@heisenberg.scientia.net>

On 10/13/2013 04:46 PM, Christoph Anton Mitterer wrote:
> Hi Greg, Guenter and Chris.
>
> Coming back to the stuff discussed previously[0].
>
> Chris Eastwood has made most of these (i.e. LEDs and buttons, the
> buzzers may work on at least some of the devices via some other serial
> device) working (AFAIU based on the previously mentioned code at
> Github[1]), he told me in several iterations of private mail.
>
> I'm not sure now, whether anything based on this code would be
> appropriate for the mainline kernel, since Guenter mentioned he'd prefer
> a mfd core driver for all that... OTOH, the later may probably never
> happen, and Chris' work seems to already do the job.
>
> I don't know however, whether he needs to patch any other places in the
> kernel, but I'm sure he can show his work (and ask questions) better
> than I, thereby inviting him to do so.
> Greg you had mentioned before that you might be able to spend some time
> on this, so if you could help Chris, that would be great.
>
>
You really have two options - either an mfd driver with client drivers
for hwmon, gpio, watchdog (and possibly others), or a gpio driver which
shares access to the superio control registers. Both the it87 hwmon driver
and the it87 watchdog driver support the latter mechanism already, so that
would be the (much) simpler option. To control the LEDs you would then
simply use the leds-gpio driver. Input would need something similar -
no idea if there is a generic input-gpio driver; if not it might make sense
to write one. Another option there would be to have a platform driver which
would tie into the gpio driver and pass the gpio pin status to the input
subsystem.

I had a look at Chris' driver, but in my opinion it is simply too hardware
specific to be acceptable as-is. Of course, I would not make the call,
so that is just my persional opinion.

Thanks,
Guenter


  reply	other threads:[~2013-10-14  1:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 23:46 support for Intel Atom based QNAP LEDs/buttons/buzzer in Linux? Christoph Anton Mitterer
2013-10-14  1:19 ` Guenter Roeck [this message]
     [not found]   ` <CAO69nHLG6dY+x9TdkrO2neXUwv60j6sV0TfeTf9GwYyyyp+fZg@mail.gmail.com>
2013-10-14 15:15     ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2013-06-15  1:31 Christoph Anton Mitterer
2013-06-20  0:14 ` Christoph Anton Mitterer
2013-06-20  2:59   ` Greg KH
2013-06-20 21:28     ` Christoph Anton Mitterer
2013-06-20 21:42       ` Greg KH
2013-06-20 21:56         ` Christoph Anton Mitterer
2013-06-24 22:36           ` Greg KH
2013-06-20 22:18         ` Christoph Anton Mitterer
2013-06-21 20:45         ` Guenter Roeck

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=525B46A7.8000605@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=calestyo@scientia.net \
    --cc=chris2027@gmail.com \
    --cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).