linux-kernel - AW: [PATCH] Input: pwm-beeper: support customized freq for SND

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <850c2508720a41b3bfb95cd7093433a4@SI-MBX1030.de.bosch.com>
Date:   Wed, 8 Feb 2017 10:11:21 +0000
From:   "Jonas Mark (ST-FIR/ENG1)" <Mark.Jonas@...bosch.com>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Heiko Schocher <hs@...x.de>
CC:     "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
        "GUAN Ben (ST-FIR/ENG1-Zhu)" <Ben.Guan@...bosch.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Thierry Reding <thierry.reding@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Boris Brezillon" <boris.brezillon@...e-electrons.com>,
        Rob Herring <robh+dt@...nel.org>,
        Manfred Schlaegl <manfred.schlaegl@....at>,
        "Mark Rutland" <mark.rutland@....com>,
        "Jonas Mark (ST-FIR/ENG1)" <Mark.Jonas@...bosch.com>
Subject: AW: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL

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.

The good news for everybody else's systems is that the patch does not change the default behavior. If not specified in the DT, the frequency will still be 1000 Hz. But other systems which are similarly challenged could now offer a reasonable bell sound, too.

Can you point me to a specification or standard which defines that SND_BELL has to be 1000 Hz without any exception?

I did some research on that topic and was not able to discover such a specification or standard. What I did find though was that the ASCII or Unicode BEL character is most likely very closely related to SND_BELL. And for BEL there is no frequency specified. Historically it once was a real bell which was rung. The intention was to notify the human on the other end of a teletype to have a look at it. And that is guaranteed with 1000 Hz as well as with 2.7 kHz as long as the sound is perceptible to the human ear.

https://en.wikipedia.org/wiki/Bell_character

Regards,
Mark