From: Frieder Schrempf <frieder.schrempf@exceet.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
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 3/3] input: pwm-beeper: add devicetree bindings to set volume levels
Date: Thu, 16 Feb 2017 21:40:05 +0100 [thread overview]
Message-ID: <4b9aeb6f-185c-5661-62d0-1466d8c9a24c@exceet.de> (raw)
In-Reply-To: <20170119213049.GB13542@dtor-ws>
On 19.01.2017 22:30, Dmitry Torokhov wrote:
> On Thu, Jan 19, 2017 at 04:24:10PM +0100, Frieder Schrempf wrote:
>> This patch adds the devicetree bindings to set the volume levels
>> and the default volume level.
>>
>> Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de>
>> ---
>> Changes in v3:
>> - none
>>
>> drivers/input/misc/pwm-beeper.c | 49 ++++++++++++++++++++++++++++++++++++++---
>> 1 file changed, 46 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/input/misc/pwm-beeper.c b/drivers/input/misc/pwm-beeper.c
>> index 3ed21da..a7f9d70 100644
>> --- a/drivers/input/misc/pwm-beeper.c
>> +++ b/drivers/input/misc/pwm-beeper.c
>> @@ -32,7 +32,7 @@ struct pwm_beeper {
>> struct work_struct work;
>> unsigned long period;
>> unsigned int volume;
>> - unsigned int volume_levels[] = {0, 8, 20, 40, 500};
>> + unsigned int *volume_levels;
>> unsigned int max_volume_level;
>> };
>>
>> @@ -161,8 +161,11 @@ static void pwm_beeper_close(struct input_dev *input)
>> static int pwm_beeper_probe(struct platform_device *pdev)
>> {
>> unsigned long pwm_id = (unsigned long)dev_get_platdata(&pdev->dev);
>> + struct device_node *np = pdev->dev.of_node;
>> struct pwm_beeper *beeper;
>> - int error;
>> + struct property *prop;
>> + int error, length;
>> + u32 value;
>>
>> beeper = kzalloc(sizeof(*beeper), GFP_KERNEL);
>> if (!beeper)
>> @@ -188,7 +191,47 @@ 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;
>> + /* determine the number of volume levels */
>> + prop = of_find_property(np, "volume-levels", &length);
>
> Please use generic device properties, not OF-specific ones.
Ok, I will change this in v4.
>
>> + if (!prop) {
>> + dev_dbg(&pdev->dev, "no volume levels specified, using max volume\n");
>> + beeper->max_volume_level = 1;
>> + } else
>> + beeper->max_volume_level = length / sizeof(u32);
>> +
>> + /* read volume levels from DT property */
>> + if (beeper->max_volume_level > 0) {
>> + size_t size = sizeof(*beeper->volume_levels) *
>> + beeper->max_volume_level;
>> +
>> + beeper->volume_levels = devm_kzalloc(&(pdev->dev), size,
>> + GFP_KERNEL);
>> + if (!beeper->volume_levels)
>> + return -ENOMEM;
>> +
>> + if (prop) {
>> + error = of_property_read_u32_array(np, "volume-levels",
>> + beeper->volume_levels,
>> + beeper->max_volume_level);
>> +
>> + if (error < 0)
>> + return error;
>> +
>> + error = of_property_read_u32(np, "default-volume-level",
>> + &value);
>> +
>> + if (error < 0) {
>> + dev_dbg(&pdev->dev, "no default volume specified, using max volume\n");
>> + value = beeper->max_volume_level - 1;
>> + }
>> + } else {
>> + beeper->volume_levels[0] = 500;
>> + value = 0;
>> + }
>> +
>> + beeper->volume = value;
>> + beeper->max_volume_level--;
>> + }
>>
>> beeper->input = input_allocate_device();
>> if (!beeper->input) {
>> --
>> 2.7.4
>>
>
next prev parent reply other threads:[~2017-02-16 20:40 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
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 [this message]
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=4b9aeb6f-185c-5661-62d0-1466d8c9a24c@exceet.de \
--to=frieder.schrempf@exceet.de \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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).