From: Rob Herring <robherring2@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
kernel@pengutronix.de
Subject: Re: [PATCH] input: pwm-beeper: Add devicetree probing support
Date: Mon, 24 Sep 2012 07:55:38 -0500 [thread overview]
Message-ID: <5060584A.80305@gmail.com> (raw)
In-Reply-To: <1348472258-31519-1-git-send-email-s.hauer@pengutronix.de>
On 09/24/2012 02:37 AM, Sascha Hauer wrote:
> A very simple binding, the only property is the phandle to the PWM.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Acked-by: Rob Herring <rob.herring@calxeda.com>
> ---
> Documentation/devicetree/bindings/input/pwm-beeper.txt | 7 +++++++
> drivers/input/misc/pwm-beeper.c | 11 ++++++++++-
> 2 files changed, 17 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/input/pwm-beeper.txt
>
> diff --git a/Documentation/devicetree/bindings/input/pwm-beeper.txt b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> new file mode 100644
> index 0000000..7388b82
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/pwm-beeper.txt
> @@ -0,0 +1,7 @@
> +* PWM beeper device tree bindings
> +
> +Registers a PWM device as beeper.
> +
> +Required properties:
> +- compatible: should be "pwm-beeper"
> +- pwms: phandle to the physical pwm device
> diff --git a/drivers/input/misc/pwm-beeper.c b/drivers/input/misc/pwm-beeper.c
> index fc84c8a..a6aa48c 100644
> --- a/drivers/input/misc/pwm-beeper.c
> +++ b/drivers/input/misc/pwm-beeper.c
> @@ -75,7 +75,10 @@ static int __devinit pwm_beeper_probe(struct platform_device *pdev)
> if (!beeper)
> return -ENOMEM;
>
> - beeper->pwm = pwm_request(pwm_id, "pwm beeper");
> + if (pdev->dev.platform_data)
> + beeper->pwm = pwm_request(pwm_id, "pwm beeper");
> + else
> + beeper->pwm = pwm_get(&pdev->dev, NULL);
>
> if (IS_ERR(beeper->pwm)) {
> error = PTR_ERR(beeper->pwm);
> @@ -171,6 +174,11 @@ static SIMPLE_DEV_PM_OPS(pwm_beeper_pm_ops,
> #define PWM_BEEPER_PM_OPS NULL
> #endif
>
> +static const struct of_device_id pwm_beeper_match[] = {
> + { .compatible = "pwm-beeper", },
> + { },
> +};
> +
> static struct platform_driver pwm_beeper_driver = {
> .probe = pwm_beeper_probe,
> .remove = __devexit_p(pwm_beeper_remove),
> @@ -178,6 +186,7 @@ static struct platform_driver pwm_beeper_driver = {
> .name = "pwm-beeper",
> .owner = THIS_MODULE,
> .pm = PWM_BEEPER_PM_OPS,
> + .of_match_table = pwm_beeper_match,
> },
> };
> module_platform_driver(pwm_beeper_driver);
>
next prev parent reply other threads:[~2012-09-24 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 7:37 [PATCH] input: pwm-beeper: Add devicetree probing support Sascha Hauer
2012-09-24 12:55 ` Rob Herring [this message]
2012-09-24 15:56 ` Dmitry Torokhov
2012-09-24 16:22 ` Lars-Peter Clausen
2012-09-24 18:49 ` Sascha Hauer
2012-09-24 19:05 ` Lars-Peter Clausen
2012-09-24 19:19 ` Sascha Hauer
2012-09-24 19:42 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2012-09-25 7:15 Sascha Hauer
2012-09-27 19:39 ` Thierry Reding
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=5060584A.80305@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-input@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).