From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: swarren@wwwdotorg.org, balbi@kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-usb@vger.kernel.org, thierry.reding@gmail.com,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V3 3/4] usb: dwc3: of-simple: Add support to get resets for the device
Date: Wed, 19 Apr 2017 17:32:47 +0530 [thread overview]
Message-ID: <5a165379-1e33-1010-f502-8b4697150391@codeaurora.org> (raw)
In-Reply-To: <1492597929.2970.66.camel@pengutronix.de>
On 04/19/2017 04:02 PM, Philipp Zabel wrote:
> On Tue, 2017-04-18 at 16:51 +0530, Vivek Gautam wrote:
>> Add support to get a list of resets available for the device.
>> These resets must be kept de-asserted until the device is
>> in use.
>>
>> Cc: Felipe Balbi <balbi@kernel.org>
>> Cc: Philipp Zabel <p.zabel@pengutronix.de>
>> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
>> ---
>> drivers/usb/dwc3/dwc3-of-simple.c | 36 ++++++++++++++++++++++++++++++++++++
>> 1 file changed, 36 insertions(+)
>>
>> diff --git a/drivers/usb/dwc3/dwc3-of-simple.c b/drivers/usb/dwc3/dwc3-of-simple.c
>> index fe414e7a9c78..9116df649f0b 100644
>> --- a/drivers/usb/dwc3/dwc3-of-simple.c
>> +++ b/drivers/usb/dwc3/dwc3-of-simple.c
>> @@ -29,13 +29,39 @@
>> #include <linux/of.h>
>> #include <linux/of_platform.h>
>> #include <linux/pm_runtime.h>
>> +#include <linux/reset.h>
>>
>> struct dwc3_of_simple {
>> struct device *dev;
>> struct clk **clks;
>> int num_clocks;
>> + struct reset_control_array *resets;
>> };
>>
>> +static int dwc3_of_simple_reset_init(struct dwc3_of_simple *simple)
>> +{
>> + struct device *dev = simple->dev;
>> + int ret;
>> +
>> + simple->resets = of_reset_control_array_get_exclusive(dev->of_node);
>> + if (IS_ERR(simple->resets)) {
>> + ret = PTR_ERR(simple->resets);
>> + if (ret == -ENOENT)
>> + /* not all controllers required resets */
>> + return 0;
> If you use the of_reset_control_array_get_optional_exclusive variant,
> you can remove the three lines directly above.
No, it's a little tricky here.
of_reset_control_get_count() returns an error code, that we then return from
of_reset_control_array_get().
This is something that tegra/pmc driver required (return errorno in case
count
of reset controls is zero.
So we handle that error separately here.
>
>> + dev_err(dev, "failed to get device resets\n");
> It would be nice to print the error code here.
Sure.
>
>> + return ret;
>> + }
>> +
>> + ret = reset_control_array_deassert(simple->resets);
>> + if (ret) {
>> + reset_control_array_put(simple->resets);
>> + return ret;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> static int dwc3_of_simple_clk_init(struct dwc3_of_simple *simple, int count)
>> {
>> struct device *dev = simple->dev;
>> @@ -100,6 +126,10 @@ static int dwc3_of_simple_probe(struct platform_device *pdev)
>> if (ret)
>> return ret;
>>
>> + ret = dwc3_of_simple_reset_init(simple);
>> + if (ret)
>> + return ret;
>> +
> I would just move the contents of dwc3_of_simple_reset_init here and add
> a goto error path at the end of dwc3_of_simple_clk_init to handle the
> reset control cleanup as needed.
Okay, i can restructure it.
>
>> ret = of_platform_populate(np, NULL, NULL, dev);
>> if (ret) {
>> for (i = 0; i < simple->num_clocks; i++) {
>> @@ -107,6 +137,9 @@ static int dwc3_of_simple_probe(struct platform_device *pdev)
>> clk_put(simple->clks[i]);
>> }
>>
>> + reset_control_array_assert(simple->resets);
>> + reset_control_array_put(simple->resets);
>> +
>> return ret;
>> }
>>
>> @@ -128,6 +161,9 @@ static int dwc3_of_simple_remove(struct platform_device *pdev)
>> clk_put(simple->clks[i]);
>> }
>>
>> + reset_control_array_assert(simple->resets);
>> + reset_control_array_put(simple->resets);
>> +
> Must the reset be asserted before of_platform_depopulate?
Right, the order must be taken care of here. Will change this.
>
>> of_platform_depopulate(dev);
> Given the order above, I'd expect the reset cleanup here.
Sure.
>
>> pm_runtime_put_sync(dev);
> regards
> Philipp
Thanks for reviewing.
Best Regards
Vivek
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-04-19 12:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 11:21 [PATCH V3 0/4] reset: APIs to manage a list of resets Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 1/4] reset: Add API to count number of reset available with device Vivek Gautam
2017-04-19 10:25 ` Philipp Zabel
2017-04-19 11:49 ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 2/4] reset: Add APIs to manage array of resets Vivek Gautam
2017-04-19 10:31 ` Philipp Zabel
2017-04-19 11:55 ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 3/4] usb: dwc3: of-simple: Add support to get resets for the device Vivek Gautam
2017-04-19 10:32 ` Philipp Zabel
2017-04-19 12:02 ` Vivek Gautam [this message]
2017-04-18 11:21 ` [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Vivek Gautam
2017-04-19 10:40 ` Philipp Zabel
2017-04-24 12:45 ` Jon Hunter
2017-04-25 4:15 ` Vivek Gautam
2017-04-25 10:05 ` Jon Hunter
2017-04-25 10:33 ` Philipp Zabel
2017-04-25 10:54 ` Jon Hunter
2017-04-25 11:06 ` Vivek Gautam
2017-04-25 11:11 ` Jon Hunter
2017-04-25 17:50 ` Vivek Gautam
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=5a165379-1e33-1010-f502-8b4697150391@codeaurora.org \
--to=vivek.gautam@codeaurora.org \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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®