From: Pavel Machek <pavel@ucw.cz>
To: Xing Zhang <Xing.Zhang@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Dan Murphy <dmurphy@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v1] Add support for MediaTek regulator vibrator driver
Date: Thu, 7 May 2020 19:45:19 +0200 [thread overview]
Message-ID: <20200507174519.GD1216@bug> (raw)
In-Reply-To: <20200429081759.26964-1-Xing.Zhang@mediatek.com>
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...
Best regards,
Pavel
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Xing Zhang <Xing.Zhang@mediatek.com>
Cc: linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org, Dan Murphy <dmurphy@ti.com>
Subject: Re: [PATCH v1] Add support for MediaTek regulator vibrator driver
Date: Thu, 7 May 2020 19:45:19 +0200 [thread overview]
Message-ID: <20200507174519.GD1216@bug> (raw)
In-Reply-To: <20200429081759.26964-1-Xing.Zhang@mediatek.com>
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...
Best regards,
Pavel
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Xing Zhang <Xing.Zhang@mediatek.com>
Cc: linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org, Dan Murphy <dmurphy@ti.com>
Subject: Re: [PATCH v1] Add support for MediaTek regulator vibrator driver
Date: Thu, 7 May 2020 19:45:19 +0200 [thread overview]
Message-ID: <20200507174519.GD1216@bug> (raw)
In-Reply-To: <20200429081759.26964-1-Xing.Zhang@mediatek.com>
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...
Best regards,
Pavel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-07 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 8:17 [PATCH v1] Add support for MediaTek regulator vibrator driver Xing Zhang
2020-04-29 8:17 ` [PATCH v1 1/3] dt-bindings: add regulator vibrator documentation Xing Zhang
2020-04-29 8:18 ` [PATCH v1 2/3] arm64: mediatek: Add regulator vibrator support Xing Zhang
2020-04-29 8:18 ` [PATCH v1 3/3] Vibrator: Add regulator vibrator driver Xing Zhang
2020-05-07 17:45 ` Pavel Machek [this message]
2020-05-07 17:45 ` [PATCH v1] Add support for MediaTek " Pavel Machek
2020-05-07 17:45 ` Pavel Machek
2020-05-07 20:45 ` Jacek Anaszewski
2020-05-07 20:45 ` Jacek Anaszewski
2020-05-07 20:45 ` Jacek Anaszewski
2020-05-07 21:09 ` Pavel Machek
2020-05-07 21:09 ` Pavel Machek
2020-05-07 21:09 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200507174519.GD1216@bug \
--to=pavel@ucw.cz \
--cc=Xing.Zhang@mediatek.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.