From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Schrempf Frieder
<frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
Cc: "dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"pawel.moll-5wv7dgnIgG8@public.gmane.org"
<pawel.moll-5wv7dgnIgG8@public.gmane.org>,
"ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org"
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
"galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
<galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"luis-HiykPkW1eAzzDCI4PIEvbQC/G2K4zDHf@public.gmane.org"
<luis-HiykPkW1eAzzDCI4PIEvbQC/G2K4zDHf@public.gmane.org>,
"linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/1] input: pwm-beeper: add feature to set volume via sysfs
Date: Mon, 11 Apr 2016 10:21:54 -0500 [thread overview]
Message-ID: <20160411152154.GA9736@rob-hp-laptop> (raw)
In-Reply-To: <1460044644-12419-1-git-send-email-frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
On Thu, Apr 07, 2016 at 03:58:40PM +0000, Schrempf Frieder wrote:
> Make the driver accept different volume levels via sysfs.
> This can be helpful if the beep/bell sound intensity needs
> to be adapted to the environment of the device.
It is preferred that bindings be a separate patch. Also, this is 2
independent features: the sysfs interface and DT properties. So that is
probably 3 patches.
Also, sysfs interfaces are supposed to be documented.
>
> The number of volume levels available and their values can
> be specified via device tree (similar to pwm-backlight).
>
> This patch was tested with linux-imx 3.10.17 and was
> applied to current mainline without any changes.
You need to test with something not 3 years old...
>
> Signed-off-by: Frieder Schrempf <frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
> ---
> .../devicetree/bindings/input/pwm-beeper.txt | 20 ++++
> drivers/input/misc/pwm-beeper.c | 109 ++++++++++++++++++-
> 2 files changed, 126 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/pwm-beeper.txt b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> index be332ae..153cd3f 100644
> --- a/Documentation/devicetree/bindings/input/pwm-beeper.txt
> +++ b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> @@ -5,3 +5,23 @@ Registers a PWM device as beeper.
> Required properties:
> - compatible: should be "pwm-beeper"
> - pwms: phandle to the physical PWM device
> +- volume-levels: Array of distinct volume levels. These need to be in the
> + range of 0 to 500, while 0 means 0% duty cycle (mute) and 500 means
> + 50% duty cycle (max volume).
Where does the scale of 0-500 come from? It is tenth of a percent?
How many array entries?
> + Please note that the actual volume of most beepers is highly
> + non-linear, which means that low volume levels are probably somewhere
> + in the range of 1 to 30 (0.1-3% duty cycle).
> +- default-volume-level: the default volume level (index into the
> + array defined by the "volume-levels" property)
> +
> +The volume level can be set via sysfs under /sys/class/input/inputX/volume.
> +The maximum volume level index can be read from /sys/class/input/inputX/max_volume_level.
> +
> +Example:
> +
> + pwm-beeper {
> + compatible = "pwm-beeper";
> + pwms = <&pwm4 0 5000>;
> + volume-levels = <0 8 20 40 500>;
> + default-volume-level = <4>;
> + };
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Schrempf Frieder <frieder.schrempf@exceet.de>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"luis@debethencourt.com" <luis@debethencourt.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] input: pwm-beeper: add feature to set volume via sysfs
Date: Mon, 11 Apr 2016 10:21:54 -0500 [thread overview]
Message-ID: <20160411152154.GA9736@rob-hp-laptop> (raw)
In-Reply-To: <1460044644-12419-1-git-send-email-frieder.schrempf@exceet.de>
On Thu, Apr 07, 2016 at 03:58:40PM +0000, Schrempf Frieder wrote:
> Make the driver accept different volume levels via sysfs.
> This can be helpful if the beep/bell sound intensity needs
> to be adapted to the environment of the device.
It is preferred that bindings be a separate patch. Also, this is 2
independent features: the sysfs interface and DT properties. So that is
probably 3 patches.
Also, sysfs interfaces are supposed to be documented.
>
> The number of volume levels available and their values can
> be specified via device tree (similar to pwm-backlight).
>
> This patch was tested with linux-imx 3.10.17 and was
> applied to current mainline without any changes.
You need to test with something not 3 years old...
>
> Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de>
> ---
> .../devicetree/bindings/input/pwm-beeper.txt | 20 ++++
> drivers/input/misc/pwm-beeper.c | 109 ++++++++++++++++++-
> 2 files changed, 126 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/input/pwm-beeper.txt b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> index be332ae..153cd3f 100644
> --- a/Documentation/devicetree/bindings/input/pwm-beeper.txt
> +++ b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> @@ -5,3 +5,23 @@ Registers a PWM device as beeper.
> Required properties:
> - compatible: should be "pwm-beeper"
> - pwms: phandle to the physical PWM device
> +- volume-levels: Array of distinct volume levels. These need to be in the
> + range of 0 to 500, while 0 means 0% duty cycle (mute) and 500 means
> + 50% duty cycle (max volume).
Where does the scale of 0-500 come from? It is tenth of a percent?
How many array entries?
> + Please note that the actual volume of most beepers is highly
> + non-linear, which means that low volume levels are probably somewhere
> + in the range of 1 to 30 (0.1-3% duty cycle).
> +- default-volume-level: the default volume level (index into the
> + array defined by the "volume-levels" property)
> +
> +The volume level can be set via sysfs under /sys/class/input/inputX/volume.
> +The maximum volume level index can be read from /sys/class/input/inputX/max_volume_level.
> +
> +Example:
> +
> + pwm-beeper {
> + compatible = "pwm-beeper";
> + pwms = <&pwm4 0 5000>;
> + volume-levels = <0 8 20 40 500>;
> + default-volume-level = <4>;
> + };
next prev parent reply other threads:[~2016-04-11 15:21 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:58 [PATCH 1/1] input: pwm-beeper: add feature to set volume via sysfs Schrempf Frieder
2016-04-07 15:58 ` Schrempf Frieder
[not found] ` <1460044644-12419-1-git-send-email-frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2016-04-11 15:21 ` Rob Herring [this message]
2016-04-11 15:21 ` Rob Herring
2016-10-07 9:00 ` Schrempf Frieder
2016-10-07 9:00 ` Schrempf Frieder
2016-10-07 9:08 ` [PATCH v2 0/3] input: pwm-beeper: add feature to set volume level Schrempf Frieder
2016-10-07 9:08 ` [PATCH v2 1/3] input: pwm-beeper: add feature to set volume via sysfs Schrempf Frieder
[not found] ` <1475831223-6006-1-git-send-email-frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2016-10-07 9:08 ` [PATCH v2 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Schrempf Frieder
2016-10-07 9:08 ` Schrempf Frieder
[not found] ` <1475831223-6006-3-git-send-email-frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2016-10-10 15:20 ` Rob Herring
2016-10-10 15:20 ` Rob Herring
2016-10-11 8:17 ` Schrempf Frieder
2016-10-11 8:17 ` Schrempf Frieder
2016-10-11 13:39 ` Rob Herring
2017-01-19 14:40 ` Frieder Schrempf
2017-01-19 15:24 ` [PATCH v3 0/3] input: pwm-beeper: add feature to set volume level Frieder Schrempf
2017-01-19 15:24 ` Frieder Schrempf
[not found] ` <cover.1484838551.git.frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-01-19 15:24 ` [PATCH v3 1/3] input: pwm-beeper: add feature to set volume via sysfs Frieder Schrempf
2017-01-19 15:24 ` Frieder Schrempf
[not found] ` <49b6d7788399142ecd01f4f5dcf263ce96eb13f1.1484838551.git.frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-01-19 21:29 ` Dmitry Torokhov
2017-01-19 21:29 ` Dmitry Torokhov
2017-02-16 20:37 ` Frieder Schrempf
2017-02-16 20:37 ` Frieder Schrempf
2017-02-16 21:08 ` [PATCH v4 0/3] input: pwm-beeper: add feature to set volume level Frieder Schrempf
2017-02-16 21:08 ` Frieder Schrempf
[not found] ` <cover.1487278130.git.frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-02-16 21:08 ` [PATCH v4 1/3] input: pwm-beeper: add feature to set volume via sysfs Frieder Schrempf
2017-02-16 21:08 ` Frieder Schrempf
2017-02-16 21:08 ` [PATCH v4 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Frieder Schrempf
2017-02-16 21:08 ` Frieder Schrempf
2017-02-16 21:08 ` [PATCH v4 3/3] input: pwm-beeper: add devicetree bindings to set volume levels Frieder Schrempf
2017-02-16 21:08 ` Frieder Schrempf
[not found] ` <bd85ff40e5c06a3404e3bc400762ee5ee1f1dedd.1487278130.git.frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-02-16 23:07 ` kbuild test robot
2017-02-16 23:07 ` kbuild test robot
2017-02-17 0:14 ` kbuild test robot
2017-02-17 0:14 ` kbuild test robot
2017-02-17 9:54 ` [PATCH v5 0/3] input: pwm-beeper: add feature to set volume level Frieder Schrempf
2017-02-17 9:54 ` Frieder Schrempf
2017-02-17 9:54 ` [PATCH v5 1/3] input: pwm-beeper: add feature to set volume via sysfs Frieder Schrempf
2017-02-17 9:54 ` Frieder Schrempf
2017-02-17 9:54 ` [PATCH v5 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Frieder Schrempf
2017-02-17 9:54 ` Frieder Schrempf
2017-02-17 9:54 ` [PATCH v5 3/3] input: pwm-beeper: add devicetree bindings to set volume levels Frieder Schrempf
2017-02-17 9:54 ` Frieder Schrempf
2017-01-19 15:24 ` [PATCH v3 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Frieder Schrempf
2017-01-19 15:24 ` Frieder Schrempf
[not found] ` <48a18fbdabcce57ee8efa57b9b6033d1462ab492.1484838551.git.frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-01-23 14:40 ` Rob Herring
2017-01-23 14:40 ` Rob Herring
2017-01-19 15:24 ` [PATCH v3 3/3] input: pwm-beeper: add devicetree bindings to set volume levels Frieder Schrempf
2017-01-19 15:24 ` Frieder Schrempf
2017-01-19 21:30 ` Dmitry Torokhov
2017-02-16 20:40 ` Frieder Schrempf
2017-02-16 20:40 ` Frieder Schrempf
2017-01-19 21:37 ` [PATCH v3 0/3] input: pwm-beeper: add feature to set volume level Dmitry Torokhov
2017-01-20 19:11 ` David Lechner
2017-02-16 21:15 ` Frieder Schrempf
2017-02-16 21:15 ` Frieder Schrempf
[not found] ` <fddaa3de-81a3-1078-65ac-29503419f1e6-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org>
2017-02-16 21:44 ` David Lechner
2017-02-16 21:44 ` David Lechner
[not found] ` <5fc04e9d-7a92-2a34-e9cc-679106481e32-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-02-17 10:01 ` Frieder Schrempf
2017-02-17 10:01 ` Frieder Schrempf
2016-10-07 9:08 ` [PATCH v2 3/3] input: pwm-beeper: add devicetree bindings to set volume levels Schrempf Frieder
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=20160411152154.GA9736@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=frieder.schrempf-wPoT/lNZgHizQB+pC5nmwQ@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luis-HiykPkW1eAzzDCI4PIEvbQC/G2K4zDHf@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
/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.