[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbh3coAedusUHgEZQu=3WkVyS4JW6=jUWAtbSxgUVhNiw@mail.gmail.com>
Date: Wed, 10 Feb 2016 15:21:14 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: "Andrew F. Davis" <afd@...com>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
Richard Purdie <rpurdie@...ys.net>,
Jacek Anaszewski <j.anaszewski@...sung.com>,
Alexandre Courbot <gnurou@...il.com>,
Javier Martinez Canillas <javier@...hile0.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] gpio: Add driver for TI TPIC2810
On Sun, Jan 31, 2016 at 11:52 PM, Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> It reminds me how 12 channel PWM chip is used on Intel Galileo Gen 2.
> Half pins are PWM, the other half is GPIO used for discrete based pin
> muxing and control. Nevertheless I think it's a userspace issue for
> now, otherwise we have to provide some 'semi-virtual' way of
> presenting pins as GPIO lines.
That sounds like an MFD spawning a GPIO and a PWM cell.
That it is called "a PWM chip" is no big deal, it should be
modeled according to what it is, not what it claims to be.
(Which makes me wanna merge this present patch as a GPIO
driver since it claims to be a LED driver but is a GPO.)
See the ST Multipurpose Expander for an example
drivers/mfd/stmpe.c
drivers/gpio/gpio-stmpe.c
drivers/input/keyboard/stmpe-keypad.c
Yours,
Linus Walleij
Powered by blists - more mailing lists