[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaJGwPLzzUuHFZye0N5iAwH2Vn8vbdwz6qv9v4F9bmGbg@mail.gmail.com>
Date: Sat, 20 Jul 2013 22:04:13 +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 Tue, Jul 16, 2013 at 4:38 AM, Kim, Milo <Milo.Kim@...com> wrote:
> LP3943 is an integrated device capable of driving 16 output channels.
> It supports a GPIO expander and a PWM generator.
But actually the data sheet describes it as a LED driver with PWM
chip.
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?
Atleast some good explanation of this needs to be found in the
patch text and also as comments in Kconfig and the code I think.
I'm just fearing that this is some way to satisfy a userspace that
wants to use the sysfs interface to GPIO to control LEDs and these
are much better off using the LED sysfs ABI.
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