[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfY4CXOmvT5y2NucKLDvdt4i2LhW5rthke1pdvuAVm7gA@mail.gmail.com>
Date: Fri, 6 Jan 2017 19:28:37 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: David Lechner <david@...hnology.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-input <linux-input@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] Input: pwm-beeper: add optional enable gpio
On Fri, Jan 6, 2017 at 4:43 AM, David Lechner <david@...hnology.com> wrote:
> This adds an optional enable gpio to the pwm-beeper device. This gpio is
> used in cases where the beeper needs to be switched on before using it.
Isn't it a property of pin muxing?
> For
> example, there may be an amplifier that is not always powered on.
This looks like GPIO based fixed voltage regulator.
>
> Tested on LEGO MINDSTORMS EV3, which has a speaker connected to PWM through
> an amplifier. The amplifier has an enable pin that is connected to a gpio.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists