[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200507210954.GB19557@duo.ucw.cz>
Date: Thu, 7 May 2020 23:09:54 +0200
From: Pavel Machek <pavel@....cz>
To: Jacek Anaszewski <jacek.anaszewski@...il.com>
Cc: Xing Zhang <Xing.Zhang@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Dan Murphy <dmurphy@...com>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v1] Add support for MediaTek regulator vibrator driver
On Thu 2020-05-07 22:45:35, Jacek Anaszewski wrote:
> Hi Pavel,
>
> On 5/7/20 7:45 PM, Pavel Machek wrote:
> > Hi!
> >
> > > This patchset add regulator vibrator driver for MTK Soc. The driver
> > > controls vibrator through regulator's enable and disable.
> >
> > We'd prefer not to have vibrators in led subsystem.
> >
> > >
> > > Xing Zhang (3):
> > > dt-bindings: add regulator vibrator documentation
> > > arm64: mediatek: Add regulator vibrator support
> > > Vibrator: Add regulator vibrator driver
> > >
> > > .../bindings/leds/regulator-vibrator.txt | 39 ++
> > > arch/arm64/configs/defconfig | 1 +
> > > drivers/leds/Kconfig | 10 +
> > > drivers/leds/Makefile | 1 +
> > > drivers/leds/regulator-vibrator.c | 450 ++++++++++++++++++
> >
> > OTOH, connecting LED to regulator might make some sense. I can take the driver with
> > vibrator functionality stripped, provided it is named the usual way...
>
> We already had an attempt of solving this in more generic way [0],
> but you opposed then [1]. Just for the record.
That's something different. led-regulator.c might be
acceptable. Special code to support vibrator quirks... not so much.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists