From: Keerthy <j-keerthy@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, <bhelgaas@google.com>
Cc: <t-kristo@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks
Date: Wed, 6 Sep 2017 18:29:32 +0530 [thread overview]
Message-ID: <02d56b4e-f1d0-e062-1833-28b9f4131622@ti.com> (raw)
In-Reply-To: <f0ffc120-c655-70ec-3b79-5bccbd98f169@ti.com>
On Wednesday 06 September 2017 04:26 PM, Kishon Vijay Abraham I wrote:
>
>
> On Wednesday 06 September 2017 04:23 PM, Kishon Vijay Abraham I wrote:
>> Keerthy,
>>
>> On Wednesday 06 September 2017 04:09 PM, Keerthy wrote:
>>> Add shutdown handler to cleanly turn off clocks.
>>
>> one minor comment below.. with that fixed you can add my
>>
>> Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>
>>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>>> ---
>>> drivers/pci/dwc/pci-dra7xx.c | 14 ++++++++++++++
>>> 1 file changed, 14 insertions(+)
>>>
>>> diff --git a/drivers/pci/dwc/pci-dra7xx.c b/drivers/pci/dwc/pci-dra7xx.c
>>> index d4e98f3..66d1cfe 100644
>>> --- a/drivers/pci/dwc/pci-dra7xx.c
>>> +++ b/drivers/pci/dwc/pci-dra7xx.c
>>> @@ -874,6 +874,19 @@ static int dra7xx_pcie_suspend_noirq(struct device *dev)
>>> return 0;
>>> }
>>>
>>> +void dra7xx_pcie_shutdown(struct platform_device *pdev)
>>> +{
>>> + struct dra7xx_pcie *dra7xx = dev_get_drvdata(&pdev->dev);
>>
>> Use struct device *dev = &pdev->dev, instead of de-referencing device pointer
>> multiple times.
>
> You might also have to dra7xx_pcie_stop_link() before disabling the clocks.
Thanks for the quick review. I will incorporate the above comments and
post v2.
Regards,
Keerthy
>
> Thanks
> Kishon
>
prev parent reply other threads:[~2017-09-06 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 10:39 Keerthy
2017-09-06 10:53 ` Kishon Vijay Abraham I
2017-09-06 10:56 ` Kishon Vijay Abraham I
2017-09-06 12:59 ` Keerthy [this message]
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=02d56b4e-f1d0-e062-1833-28b9f4131622@ti.com \
--to=j-keerthy@ti.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=t-kristo@ti.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®