From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
guillaume ligneul <guillaume.ligneul@oselis.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Guenter Roeck <guenter.roeck@ericsson.com>,
Jean Delvare <khali@linux-fr.org>,
Wim Van Sebroeck <wim@iguana.be>,
Denis Turischev <denis@compulab.co.il>,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [RFC] IT87xx GPIO and other drivers
Date: Tue, 17 Apr 2012 07:51:17 -0700 [thread overview]
Message-ID: <4F8D8365.3020002@flameeyes.eu> (raw)
In-Reply-To: <CACRpkdaOSSA8PuTSQ4utp9JHKbBiz+iWfuPn=2WyojZxsR5a3A@mail.gmail.com>
Il 16/04/2012 23:47, Linus Walleij ha scritto:
> I would suggest merging gpio-it87 and pinctrl-it87 into one driver
> in drivers/pinctrl-it87.c. I don't know for sure however, since it depends
> on hardware: usually these is a tight dependence between GPIO and
> pinctrl (IIRC this was the case with SuperIO), and then it often makes
> a lot of sense to create a composite driver, in order to just have one
> state container (cookie) to pass around in the functions, and to remap
> a register range only once.
So you mean having the MFD actually handle most of the work, and that's
it? If I did read the source correctly, that might actually work well,
as hwmon/it87 is only using the SuperIO for detection (which MFD can
take care of), while the others would be using the same functions to
read/write to the SuperIO registers.
Does that mean that when the user enables the MFD, they get gpio,
pinctrl and watchdog at once, or should it still have multiple Kconfig
entries which select it?
> The concept is explained in my pinctrl talk on a high level:
> http://www.df.lth.se/~triad/papers/pincontrol.pdf
Okay will read through it, thanks!
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
next prev parent reply other threads:[~2012-04-17 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 19:51 [RFC] IT87xx GPIO and other drivers Diego Elio Pettenò
2012-04-16 19:59 ` Guenter Roeck
2012-04-17 6:47 ` Linus Walleij
2012-04-17 14:51 ` Diego Elio Pettenò [this message]
2012-04-17 19:31 ` Linus Walleij
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=4F8D8365.3020002@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--cc=denis@compulab.co.il \
--cc=grant.likely@secretlab.ca \
--cc=guenter.roeck@ericsson.com \
--cc=guillaume.ligneul@oselis.com \
--cc=khali@linux-fr.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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