[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F45880696056844FA6A73F415B568C695B0EA11A90@EXDCVYMBSTM006.EQ1STM.local>
Date: Mon, 3 Sep 2012 13:28:44 +0200
From: Arun MURTHY <arun.murthy@...ricsson.com>
To: Linus Walleij <linus.walleij@...aro.org>,
Thierry Reding <thierry.reding@...onic-design.de>,
Srinidhi KASAGAR <srinidhi.kasagar@...ricsson.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Lee Jones <lee.jones@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] pwm: Move AB8500 PWM driver to PWM framework
> On Sun, Sep 2, 2012 at 12:30 PM, Thierry Reding <thierry.reding@...onic-
> design.de> wrote:
>
> > This commit moves the driver to drivers/pwm and converts it to the new
> > PWM framework.
> >
> > Signed-off-by: Thierry Reding <thierry.reding@...onic-design.de>
> > ---
> > Note: I'll take this through the PWM tree, but I'd like to have it
> > acknowledged by a few people who know the hardware and can actually
> > test whether this still works.
>
> Pls include Arun on these patches, he'll know best if it'll work or not.
>
> I have one generic question: will this alter the layout of sysfs so we need to
> change userspace? I had such issues before when moving drivers to new
> busses...
>
Since this pwm framework is still a set of exported functions in a header file,
the file architecture doesn't really matter.
Using this driver, either leds-pwm and backlight-pwm is used to register and
this is where actual registration happens(sysfs entry is created).
Thanks and Regards,
Arun R Murthy
------------------
--
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