From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Jonas Mark (ST-FIR/ENG1)" <Mark.Jonas@de.bosch.com>
Cc: Heiko Schocher <hs@denx.de>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"GUAN Ben (ST-FIR/ENG1-Zhu)" <Ben.Guan@cn.bosch.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Rob Herring <robh+dt@kernel.org>,
Manfred Schlaegl <manfred.schlaegl@gmx.at>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL
Date: Mon, 13 Feb 2017 20:27:48 -0800 [thread overview]
Message-ID: <20170214042748.GC19688@dtor-ws> (raw)
In-Reply-To: <850c2508720a41b3bfb95cd7093433a4@SI-MBX1030.de.bosch.com>
On Wed, Feb 08, 2017 at 10:11:21AM +0000, Jonas Mark (ST-FIR/ENG1) wrote:
> Hello Dmitry,
>
> > > extend the pwm-beeper driver to support customized frequency
> > > for SND_BELL from device tree.
> >
> > No, SND_BELL is literally SND_TONE @1000Hz. There should be no
> > customizing. If applications want to use different frequency then should
> > be using SND_TONE.
>
> We are not aiming for an application shortcut here. Instead, changing
> the bell frequency shall be a system setting. That is, every
> application which wants to make a bell sound shall use the alternative
> frequency.
>
> The reason why we are deviating from the default 1000 Hz is that on
> our hardware we are using a loudspeaker which is rated for 2.7 kHz.
> That is, it will only sound at the specified volume and frequency if
> you feed it with a 2.7 kHz square wave. If you deviate from it, e.g.
> by using 1000 Hz, the output will be dim and squeaky. Worst case,
> SND_BELL would be completely silent on our system. So the only bell
> sound we can reliably generate on our system has 2.7 kHz.
OK, fair enough. Please address Rob's comments on binding and resend.
Also I am not sure why you needed to change the switch statement around,
you only need to replace 1000 with value from the attribute.
Oh, and please use device_property_*() API instead of of_*().
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-02-14 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 5:21 [PATCH] Input: pwm-beeper: support customized freq for SND_BELL Heiko Schocher
[not found] ` <1486444894-18321-1-git-send-email-hs-ynQEQJNshbs@public.gmane.org>
2017-02-07 18:13 ` Dmitry Torokhov
2017-02-08 10:11 ` AW: " Jonas Mark (ST-FIR/ENG1)
2017-02-14 4:27 ` Dmitry Torokhov [this message]
2017-02-14 5:02 ` Heiko Schocher
2017-02-10 15:48 ` Rob Herring
2017-02-13 6:12 ` Heiko Schocher
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=20170214042748.GC19688@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Ben.Guan@cn.bosch.com \
--cc=Mark.Jonas@de.bosch.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred.schlaegl@gmx.at \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).