Re: [PATCH] mfd: Add TWL4030 PWM driver

Arnd Bergmann
2012-03-21T10:03:46Z

On Wednesday 21 March 2012, Thierry Reding wrote:
> * Arnd Bergmann wrote:
> > On Wednesday 21 March 2012, Bernhard Walle wrote:
> > > Am 20.03.12 23:02, schrieb Arnd Bergmann:
> > > > On Tuesday 20 March 2012, Bernhard Walle wrote:
> > > >>
> > > >> This PWM driver uses the PWM of the TWL4030. The driver for the TWL6030
> > > >> PWM has been used as mode, but the PWM registers are different.
> > > >>
> > > >> The driver can be used and has been tested in conjunction with
> > > >> pwm-backlight to control a backlight LED of a LCD touch screen.
> > > >>
> > > >> Signed-off-by: Bernhard Walle <walle@corscience.de>
> > > >
> > > > Since it's too late for v3.4 now and we will get a new pwm
> > > > subsystem in v3.5, I suggest you change the driver to work
> > > > register with that subsystem instead of just using the old
> > > > header file. Note that drivers/mfd is not really the right
> > > > place anyway, because this is not a multifunction driver but
> > > > just one device driver that happens to be a slave of an mfd.
> > >
> > > Does that new subsystem already exist in some tree?
> >
> > Thierry Reding has been busily posting patches, so he probably has
> > one that you can use, but I couldn't find it now.
>
> I don't have a public tree anywhere. Does anyone have a recommendation where
> I could set one up? github or gitorious are the first to come to my mind.

They both work fine and are easy to set up, at least as a temporary location.

If you want to have something more official in the long run, you could
either set up your own git server on your employer's domain or if that
is impractical, get an account on kernel.org or linaro.org. Both of those
try to limit the amount of accounts they hand out to external people, but
since you are going to be a subsystem maintainer, I don't see it as a
problem.

Arnd