[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbsQqyA53RGs2m36Y=dh7yaXuwU8yJs=y2Dt52Pih_iLg@mail.gmail.com>
Date: Sat, 20 Jul 2013 22:09:32 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: "Kim, Milo" <Milo.Kim@...com>
Cc: "sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pwm@...r.kernel.org" <linux-pwm@...r.kernel.org>
Subject: Re: [PATCH 0/3] LP3943 MFD driver for a GPIO expander and a PWM generator
On Sat, Jul 20, 2013 at 10:04 PM, Linus Walleij
<linus.walleij@...aro.org> wrote:
> Do you have use cases not using it for LEDs but other thing or why
> do you want to model the 16 LED lines as GPIO lines?
> Why can't you just have a drivers/leds/* as for any other LED
> chip?
Bah forget this. Now I saw that application note in the GPIO
portion patch.
But don't you want a drivers/leds/* driver for this as well?
I imagine the MFD core should send a mask to GPIO and
LEDs drivers stating which lines can be used for GPIO and
which lines can be used for LEDs.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists