From: Keerthy <a0393675@ti.com>
To: Lee Jones <lee.jones@linaro.org>, Keerthy <j-keerthy@ti.com>
Cc: dmitry.torokhov@gmail.com, linus.walleij@linaro.org,
gnurou@gmail.com, broonie@kernel.org, tony@atomide.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-input@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 06/10] gpio: tps65218: Remove the compatible
Date: Tue, 28 Jun 2016 12:29:58 +0530 [thread overview]
Message-ID: <5772206E.7020509@ti.com> (raw)
In-Reply-To: <20160628065235.GC6720@dell>
On Tuesday 28 June 2016 12:22 PM, Lee Jones wrote:
> On Tue, 28 Jun 2016, Keerthy wrote:
>
>> Remove the individual compatible for the gpio module.
>> Introduce id_table and update the driver accordingly
>> to parse device tree nodes by just using the mfd compatible.
>
> Aren't there any OF calls in this driver?
>
There is one assignment.
ps65218_gpio->gpio_chip.of_node = pdev->dev.of_node;
> You can use the MFD API to pass through compatible strings in order to
> interrogate the DT in the normal way. There isn't usually a reason to
> remove DT support just because you start using the MFD API.
Okay. I will do it the way i am doing for tps65218-pwrbutton.
Thanks for the review.
>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>> drivers/gpio/gpio-tps65218.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-tps65218.c b/drivers/gpio/gpio-tps65218.c
>> index 0f9d9bd..06fd61f 100644
>> --- a/drivers/gpio/gpio-tps65218.c
>> +++ b/drivers/gpio/gpio-tps65218.c
>> @@ -225,19 +225,19 @@ static int tps65218_gpio_remove(struct platform_device *pdev)
>> return 0;
>> }
>>
>> -static const struct of_device_id tps65218_dt_match[] = {
>> - { .compatible = "ti,tps65218-gpio" },
>> - { }
>> +static const struct platform_device_id tps65218_gpio_id_table[] = {
>> + { "tps65218-gpio", },
>> + { /* sentinel */ }
>> };
>> -MODULE_DEVICE_TABLE(of, tps65218_dt_match);
>> +MODULE_DEVICE_TABLE(platform, tps65218_gpio_id_table);
>>
>> static struct platform_driver tps65218_gpio_driver = {
>> .driver = {
>> .name = "tps65218-gpio",
>> - .of_match_table = of_match_ptr(tps65218_dt_match)
>> },
>> .probe = tps65218_gpio_probe,
>> .remove = tps65218_gpio_remove,
>> + .id_table = tps65218_gpio_id_table,
>> };
>>
>> module_platform_driver(tps65218_gpio_driver);
>
next prev parent reply other threads:[~2016-06-28 6:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 6:06 [PATCH v3 00/10] mfd: tps65218: Clean ups Keerthy
2016-06-28 6:06 ` [PATCH v3 01/10] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-06-28 7:00 ` Lee Jones
2016-06-28 7:01 ` Keerthy
2016-06-28 6:06 ` [PATCH v3 02/10] Documentation: regulator: tps65218: Update examples Keerthy
2016-06-28 6:59 ` Lee Jones
2016-06-28 7:45 ` Keerthy
2016-06-28 6:06 ` [PATCH v3 03/10] input: tps65218-pwrbutton: Add platform_device_id table Keerthy
[not found] ` <1467093980-11458-4-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-06-28 6:25 ` kbuild test robot
2016-06-28 6:33 ` kbuild test robot
2016-06-28 6:49 ` Lee Jones
2016-06-28 6:55 ` Keerthy
2016-06-28 7:41 ` Lee Jones
2016-06-28 7:43 ` Keerthy
2016-06-28 6:06 ` [PATCH v3 04/10] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-28 6:54 ` Lee Jones
2016-06-28 6:06 ` [PATCH v3 05/10] regulator: tps65218: Remove all the compatibles Keerthy
2016-06-28 6:06 ` [PATCH v3 06/10] gpio: tps65218: Remove the compatible Keerthy
2016-06-28 6:52 ` Lee Jones
2016-06-28 6:59 ` Keerthy [this message]
2016-06-28 6:06 ` [PATCH v3 07/10] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles Keerthy
2016-06-28 6:06 ` [PATCH v3 08/10] ARM: dts: AM437X-SK-EVM: " Keerthy
2016-06-28 6:06 ` [PATCH v3 09/10] ARM: dts: AM437X-CM-T43: " Keerthy
2016-06-28 6:06 ` [PATCH v3 10/10] ARM: dts: AM43X-EPOS-EVM: " 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=5772206E.7020509@ti.com \
--to=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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).