From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Frieder Schrempf <frieder.schrempf@exceet.de>
Cc: robh@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
luis@debethencourt.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] input: pwm-beeper: add feature to set volume via sysfs
Date: Thu, 19 Jan 2017 13:29:23 -0800 [thread overview]
Message-ID: <20170119212923.GA13542@dtor-ws> (raw)
In-Reply-To: <49b6d7788399142ecd01f4f5dcf263ce96eb13f1.1484838551.git.frieder.schrempf@exceet.de>
Hi Frieder,
On Thu, Jan 19, 2017 at 04:24:08PM +0100, Frieder Schrempf wrote:
> Make the driver accept switching volume levels via sysfs.
> This can be helpful if the beep/bell sound intensity needs
> to be adapted to the environment of the device.
>
> The volume adjustment is done by changing the duty cycle of
> the pwm signal.
>
> This patch adds the sysfs interface with 5 default volume
> levels (0 - mute, 4 - max. volume).
>
> Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de>
> ---
> Changes in v3:
> - update date
>
> .../ABI/testing/sysfs-class-input-pwm-beeper | 17 ++++++
> drivers/input/misc/pwm-beeper.c | 71 +++++++++++++++++++++-
> 2 files changed, 87 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/ABI/testing/sysfs-class-input-pwm-beeper
>
> diff --git a/Documentation/ABI/testing/sysfs-class-input-pwm-beeper b/Documentation/ABI/testing/sysfs-class-input-pwm-beeper
> new file mode 100644
> index 0000000..c878a1d
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-input-pwm-beeper
> @@ -0,0 +1,17 @@
> +What: /sys/class/input/input(x)/volume
Only generic (i.e. applicable to all input devices) attributes can be
present in /sys/class/input/input(x)/, and volume certainly isn't such
attribute. Please move them to the pwm-beeper platform device itself.
> +Date: January 2017
> +KernelVersion:
> +Contact: Frieder Schrempf <frieder.schrempf@exceet.de>
> +Description:
> + Control the volume of this pwm-beeper. Values
> + are between 0 and max_volume_level. This file will also
> + show the current volume level stored in the driver.
> +
> +What: /sys/class/input/input(x)/max_volume_level
> +Date: January 2017
> +KernelVersion:
> +Contact: Frieder Schrempf <frieder.schrempf@exceet.de>
> +Description:
> + This file shows the maximum volume level that can be
> + assigned to volume.
> +
> diff --git a/drivers/input/misc/pwm-beeper.c b/drivers/input/misc/pwm-beeper.c
> index 5f9655d..3ed21da 100644
> --- a/drivers/input/misc/pwm-beeper.c
> +++ b/drivers/input/misc/pwm-beeper.c
> @@ -1,5 +1,9 @@
> /*
> * Copyright (C) 2010, Lars-Peter Clausen <lars@metafoo.de>
> + *
> + * Copyright (C) 2016, Frieder Schrempf <frieder.schrempf@exceet.de>
> + * (volume support)
> + *
> * PWM beeper driver
> *
> * This program is free software; you can redistribute it and/or modify it
> @@ -27,16 +31,77 @@ struct pwm_beeper {
> struct pwm_device *pwm;
> struct work_struct work;
> unsigned long period;
> + unsigned int volume;
> + unsigned int volume_levels[] = {0, 8, 20, 40, 500};
Does this actually work? Anyway, you are not allowing to set differentr
values in for different beepers, so take the array out of the structure.
> + unsigned int max_volume_level;
> };
>
> #define HZ_TO_NANOSECONDS(x) (1000000000UL/(x))
>
> +static ssize_t beeper_show_volume(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct pwm_beeper *beeper = dev_get_drvdata(dev);
> +
> + return sprintf(buf, "%d\n", beeper->volume);
> +}
> +
> +static ssize_t beeper_show_max_volume_level(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct pwm_beeper *beeper = dev_get_drvdata(dev);
> +
> + return sprintf(buf, "%d\n", beeper->max_volume_level);
> +}
> +
> +static ssize_t beeper_store_volume(struct device *dev,
> + struct device_attribute *attr, const char *buf, size_t count)
> +{
> + int rc;
> + struct pwm_beeper *beeper = dev_get_drvdata(dev);
> + unsigned int volume;
> +
> + rc = kstrtouint(buf, 0, &volume);
> + if (rc)
> + return rc;
> +
> + rc = -ENXIO;
Why? There are no failures below.
> + if (volume > beeper->max_volume_level)
> + volume = beeper->max_volume_level;
Return -EINVAL maybe?
> + pr_debug("set volume to %u\n", volume);
> + if (beeper->volume != volume)
> + beeper->volume = volume;
Why?
> + rc = count;
> +
> + return rc;
> +}
> +
> +static DEVICE_ATTR(volume, 0644, beeper_show_volume, beeper_store_volume);
> +static DEVICE_ATTR(max_volume_level, 0644, beeper_show_max_volume_level, NULL);
Drop "level", it is cleaner.
> +
> +static struct attribute *bp_device_attributes[] = {
pwm_beeper_atttributes
> + &dev_attr_volume.attr,
> + &dev_attr_max_volume_level.attr,
> + NULL,
> +};
> +
> +static struct attribute_group bp_device_attr_group = {
pwm_beeper_attribute_group
> + .attrs = bp_device_attributes,
> +};
> +
> +static const struct attribute_group *bp_device_attr_groups[] = {
> + &bp_device_attr_group,
> + NULL,
> +};
> +
> static void __pwm_beeper_set(struct pwm_beeper *beeper)
> {
> unsigned long period = beeper->period;
>
> if (period) {
> - pwm_config(beeper->pwm, period / 2, period);
> + pwm_config(beeper->pwm,
> + period / 1000 * beeper->volume_levels[beeper->volume],
> + period);
> pwm_enable(beeper->pwm);
> } else
> pwm_disable(beeper->pwm);
> @@ -123,6 +188,8 @@ static int pwm_beeper_probe(struct platform_device *pdev)
>
> INIT_WORK(&beeper->work, pwm_beeper_work);
>
> + beeper->max_volume_level = ARRAY_SIZE(beeper->volume_levels) - 1;
> +
> beeper->input = input_allocate_device();
> if (!beeper->input) {
> dev_err(&pdev->dev, "Failed to allocate input device\n");
> @@ -146,6 +213,8 @@ static int pwm_beeper_probe(struct platform_device *pdev)
>
> input_set_drvdata(beeper->input, beeper);
>
> + beeper->input->dev.groups = bp_device_attr_groups;
> +
> error = input_register_device(beeper->input);
> if (error) {
> dev_err(&pdev->dev, "Failed to register input device: %d\n", error);
> --
> 2.7.4
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-01-19 21:29 UTC|newest]
Thread overview: 35+ 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-11 15:21 ` Rob Herring
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
2016-10-07 9:08 ` [PATCH v2 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Schrempf Frieder
2016-10-10 15:20 ` Rob Herring
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 ` [PATCH v3 1/3] input: pwm-beeper: add feature to set volume via sysfs Frieder Schrempf
2017-01-19 21:29 ` Dmitry Torokhov [this message]
2017-02-16 20:37 ` Frieder Schrempf
2017-01-19 15:24 ` [PATCH v3 2/3] input: pwm-beeper: add documentation for volume devicetree bindings Frieder Schrempf
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 21:30 ` Dmitry Torokhov
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:44 ` David Lechner
2017-02-17 10:01 ` Frieder Schrempf
2017-02-16 21:08 ` [PATCH v4 " Frieder Schrempf
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 ` [PATCH v4 2/3] input: pwm-beeper: add documentation for volume devicetree bindings 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 23:07 ` 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 ` [PATCH v5 1/3] input: pwm-beeper: add feature to set volume via sysfs 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 ` [PATCH v5 3/3] input: pwm-beeper: add devicetree bindings to set volume levels Frieder Schrempf
2016-10-07 9:08 ` [PATCH v2 " 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=20170119212923.GA13542@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frieder.schrempf@exceet.de \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@debethencourt.com \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.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 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).