From: Keerthy <j-keerthy@ti.com>
To: Claudiu Beznea <Claudiu.Beznea@microchip.com>,
<daniel.lezcano@linaro.org>, <tony@atomide.com>,
<aaro.koskinen@iki.fi>, <thierry.reding@gmail.com>
Cc: <linux-pwm@vger.kernel.org>, <grygorii.strashko@ti.com>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<t-kristo@ti.com>, <ladis@linux-mips.org>,
<sebastian.reichel@collabora.co.uk>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 08/10] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops
Date: Mon, 8 Jan 2018 20:03:49 +0530 [thread overview]
Message-ID: <fd544471-63d0-dbf1-cee5-53f05c837cdd@ti.com> (raw)
In-Reply-To: <e9f73341-5262-0d9c-ecb8-f04f18d0bb05@microchip.com>
On Monday 08 January 2018 02:14 PM, Claudiu Beznea wrote:
>
>
> On 02.01.2018 12:09, Keerthy wrote:
>> Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> Tested-by: Ladislav Michl <ladis@linux-mips.org>
>> ---
>> drivers/pwm/pwm-omap-dmtimer.c | 39 ++++++++++++++++++++++-----------------
>> 1 file changed, 22 insertions(+), 17 deletions(-)
>>
>> diff --git a/drivers/pwm/pwm-omap-dmtimer.c b/drivers/pwm/pwm-omap-dmtimer.c
>> index 5ad42f3..3b27aff 100644
>> --- a/drivers/pwm/pwm-omap-dmtimer.c
>> +++ b/drivers/pwm/pwm-omap-dmtimer.c
>> @@ -23,6 +23,7 @@
>> #include <linux/mutex.h>
>> #include <linux/of.h>
>> #include <linux/of_platform.h>
>> +#include <linux/platform_data/dmtimer-omap.h>
>> #include <linux/platform_data/pwm_omap_dmtimer.h>
>> #include <linux/platform_device.h>
>> #include <linux/pm_runtime.h>
>> @@ -37,7 +38,7 @@ struct pwm_omap_dmtimer_chip {
>> struct pwm_chip chip;
>> struct mutex mutex;
>> pwm_omap_dmtimer *dm_timer;
>> - struct pwm_omap_dmtimer_pdata *pdata;
>> + struct omap_dm_timer_ops *pdata;
>> struct platform_device *dm_timer_pdev;
>> };
>>
>> @@ -242,19 +243,33 @@ static int pwm_omap_dmtimer_probe(struct platform_device *pdev)
>> {
>> struct device_node *np = pdev->dev.of_node;
>> struct device_node *timer;
>> + struct platform_device *timer_pdev;
>> struct pwm_omap_dmtimer_chip *omap;
>> - struct pwm_omap_dmtimer_pdata *pdata;
>> + struct dmtimer_platform_data *timer_pdata;
>> + struct omap_dm_timer_ops *pdata;
>> pwm_omap_dmtimer *dm_timer;
>> u32 v;
>> int status;
>>
>> - pdata = dev_get_platdata(&pdev->dev);
>> - if (!pdata) {
>> - dev_err(&pdev->dev, "Missing dmtimer platform data\n");
>> + timer = of_parse_phandle(np, "ti,timers", 0);
> of_node_put() should be called when done with device_node pointer returned
> by of_parse_phandle() (you may want to check the return ERROR cases below
> regarding this statement):
>> + if (!timer)
>> + return -ENODEV;
>> +
>> + timer_pdev = of_find_device_by_node(timer);
>> + if (!timer_pdev) {
>> + dev_err(&pdev->dev, "Unable to find Timer pdev\n");
> here
>> + return -ENODEV;
>> + }
>> +
>> + timer_pdata = dev_get_platdata(&timer_pdev->dev);
>> + if (!timer_pdata) {
>> + dev_err(&pdev->dev, "dmtimer pdata structure NULL\n");
> here
>> return -EINVAL;
>> }
>>
>> - if (!pdata->request_by_node ||
>> + pdata = timer_pdata->timer_ops;
>> +
>> + if (!pdata || !pdata->request_by_node ||
>> !pdata->free ||
>> !pdata->enable ||
>> !pdata->disable ||
>> @@ -270,10 +285,6 @@ static int pwm_omap_dmtimer_probe(struct platform_device *pdev)
>> return -EINVAL;
>> }
>>
>> - timer = of_parse_phandle(np, "ti,timers", 0);
>> - if (!timer)
>> - return -ENODEV;
>> -
>> if (!of_get_property(timer, "ti,timer-pwm", NULL)) {
> here
>> dev_err(&pdev->dev, "Missing ti,timer-pwm capability\n");
>> return -ENODEV;
>> @@ -291,13 +302,7 @@ static int pwm_omap_dmtimer_probe(struct platform_device *pdev)
>>
>> omap->pdata = pdata;
>> omap->dm_timer = dm_timer;
>> -
>> - omap->dm_timer_pdev = of_find_device_by_node(timer);
>> - if (!omap->dm_timer_pdev) {
>> - dev_err(&pdev->dev, "Unable to find timer pdev\n");
>> - omap->pdata->free(dm_timer);
>> - return -EINVAL;
>> - }
>> + omap->dm_timer_pdev = timer_pdev;
>>
>> /*
>> * Ensure that the timer is stopped before we allow PWM core to call
>>
> And all the other return instructions from probe function not listed by git diff
Thanks for reviewing. I will add the of_node_put call for all the error
paths.
>
next prev parent reply other threads:[~2018-01-08 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 10:09 [PATCH v6 00/10] omap: dmtimer: Move driver out of plat-omap Keerthy
2018-01-02 10:09 ` [PATCH v6 01/10] clocksource: dmtimer: Remove all the exports Keerthy
2018-01-02 10:09 ` [PATCH v6 02/10] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define Keerthy
2018-01-02 10:09 ` [PATCH v6 03/10] arm: omap: Move dmtimer.h out of plat-omap Keerthy
2018-01-02 10:09 ` [PATCH v6 04/10] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource Keerthy
2018-01-02 10:09 ` [PATCH v6 05/10] dmtimer: Add timer ops to the platform data structure Keerthy
2018-01-02 10:09 ` [PATCH v6 06/10] clocksource: dmtimer: Populate the timer ops to the pdata Keerthy
2018-01-02 10:09 ` [PATCH v6 07/10] clocksource: timer-dm: Hook device platform data if not already assigned Keerthy
2018-01-02 10:09 ` [PATCH v6 08/10] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops Keerthy
2018-01-08 8:44 ` Claudiu Beznea
2018-01-08 14:33 ` Keerthy [this message]
2018-01-08 14:44 ` Neil Armstrong
2018-01-08 14:47 ` Claudiu Beznea
2018-01-08 16:24 ` Keerthy
2018-01-02 10:09 ` [PATCH v6 09/10] arm: omap: pdata-quirks: Remove unused timer pdata Keerthy
2018-01-02 10:09 ` [PATCH v6 10/10] clocksource: timer-dm: Check prescaler value Keerthy
2018-01-04 22:47 ` Ladislav Michl
2018-01-07 15:56 ` Keerthy
2018-01-07 19:26 ` Ladislav Michl
2018-01-07 15:59 ` [PATCH v6 00/10] omap: dmtimer: Move driver out of plat-omap 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=fd544471-63d0-dbf1-cee5-53f05c837cdd@ti.com \
--to=j-keerthy@ti.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=aaro.koskinen@iki.fi \
--cc=daniel.lezcano@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=t-kristo@ti.com \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®