From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Keerthy <j-keerthy@ti.com>
Cc: gnurou@gmail.com, devicetree@vger.kernel.org, tony@atomide.com,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-gpio@vger.kernel.org,
broonie@kernel.org, linux-input@vger.kernel.org,
linux-omap@vger.kernel.org, lee.jones@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/6] input: tps65218-pwrbutton: Add platform_device_id table
Date: Tue, 28 Jun 2016 10:04:41 -0700 [thread overview]
Message-ID: <20160628170441.GA13114@dtor-ws> (raw)
In-Reply-To: <1467117054-12943-4-git-send-email-j-keerthy@ti.com>
On Tue, Jun 28, 2016 at 06:00:51PM +0530, Keerthy wrote:
> platform_device_id table is needed for adding the tps65218-pwrbutton
> module to the mfd_cell array.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> Changes in v4:
>
> * Added the missing ';' for struct platform_device_id.
>
> drivers/input/misc/tps65218-pwrbutton.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/input/misc/tps65218-pwrbutton.c b/drivers/input/misc/tps65218-pwrbutton.c
> index 2bba8de..33d141a 100644
> --- a/drivers/input/misc/tps65218-pwrbutton.c
> +++ b/drivers/input/misc/tps65218-pwrbutton.c
> @@ -113,12 +113,19 @@ static const struct of_device_id of_tps65218_pwr_match[] = {
> };
> MODULE_DEVICE_TABLE(of, of_tps65218_pwr_match);
>
> +static const struct platform_device_id tps65218_pwrbtn_id_table[] = {
> + { "tps65218-pwrbutton", },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(platform, tps65218_pwrbtn_id_table);
> +
> static struct platform_driver tps65218_pwron_driver = {
> .probe = tps65218_pwron_probe,
> .driver = {
> .name = "tps65218_pwrbutton",
> .of_match_table = of_tps65218_pwr_match,
> },
> + .id_table = tps65218_pwrbtn_id_table,
> };
> module_platform_driver(tps65218_pwron_driver);
>
> --
> 1.9.1
>
--
Dmitry
next prev parent reply other threads:[~2016-06-28 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 12:30 [PATCH v6 0/6] mfd: tps65218: Clean ups Keerthy
2016-06-28 12:30 ` [PATCH v6 1/6] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-06-28 12:30 ` [PATCH v6 2/6] Documentation: regulator: tps65218: Update examples Keerthy
2016-06-28 12:30 ` [PATCH v6 3/6] input: tps65218-pwrbutton: Add platform_device_id table Keerthy
2016-06-28 17:04 ` Dmitry Torokhov [this message]
[not found] ` <1467117054-12943-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-06-28 12:30 ` [PATCH v6 4/6] gpio: tps65218-gpio: " Keerthy
2016-06-29 8:56 ` Linus Walleij
2016-06-29 9:32 ` Keerthy
[not found] ` <1467117054-12943-5-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-07-04 9:50 ` Linus Walleij
2016-07-04 9:57 ` Keerthy
2016-06-28 12:30 ` [PATCH v6 5/6] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-28 12:30 ` [PATCH v6 6/6] regulator: tps65218: Remove all the compatibles Keerthy
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=20160628170441.GA13114@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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).