From: Jean Delvare <khali@linux-fr.org>
To: Alex Rio <scasbyte@gmail.com>
Cc: guenter.roeck@ericsson.com, linux-kernel@vger.kernel.org,
Rodolfo Giometti <giometti@linux.it>
Subject: Re: [RFC][PATCH 2/2] hwmon: (w83627ehf) Add GPIO port 3 functionality
Date: Sat, 14 Jan 2012 21:18:56 +0100 [thread overview]
Message-ID: <20120114211856.7e1b816d@endymion.delvare> (raw)
In-Reply-To: <CAPbJ=B=_Xubsni7R00kSotDQ9AE9jmhmyRV0gPkXGqAPGrNaXg@mail.gmail.com>
On Fri, 13 Jan 2012 19:39:56 -0600, Alex Rio wrote:
> The w83627ehf chip has 5 GPIO ports, currently none of them is supported.
> This patch adds the GPIO port 3 driver with the following functions:
> set/get pin values, direction_in/out, set_debounce.
> The values are also available to the userspace (if requiered)
> in the path /sys/class/gpio by using the export/unexport functions.
> Please look at the REVISIT comment, this is the main reason of the RFC,
> suggestions will be highly appreciated.
>
> Signed-off-by: Alex Rio <scasbyte@gmail.com>
> ---
> drivers/hwmon/w83627ehf.c | 188 +++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 188 insertions(+), 0 deletions(-)
This is calling for a MFD driver for these chips. This was proposed in
the past, BTW, but never followed up:
http://lists.lm-sensors.org/pipermail/lm-sensors/2010-February/027795.html
Putting everything in the current driver is not going to be accepted.
It certainly looks pleasant because it's a more simple approach, but
the result would be a complex and unmaintainable driver.
--
Jean Delvare
next prev parent reply other threads:[~2012-01-14 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 1:39 Alex Rio
2012-01-14 17:54 ` Guenter Roeck
2012-01-14 20:18 ` Jean Delvare [this message]
2012-01-14 22:15 ` Alejandro
2012-01-15 8:15 ` Jean Delvare
2012-01-15 10:53 ` Rodolfo Giometti
2012-01-16 9:42 ` Alejandro del Rio
2012-01-16 16:18 ` 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=20120114211856.7e1b816d@endymion.delvare \
--to=khali@linux-fr.org \
--cc=giometti@linux.it \
--cc=guenter.roeck@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scasbyte@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
all inboxes | Powered by JetHome®