From: Stefan Agner <stefan@agner.ch>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: Sanchayan Maity <maitysanchayan@gmail.com>,
kernel@pengutronix.de, a.zummo@towertech.it,
b35083@freescale.com, rtc-linux@googlegroups.com,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] drivers/rtc/rtc-snvs: Add clock support
Date: Mon, 29 Sep 2014 14:57:28 +0200 [thread overview]
Message-ID: <ff3b3c43678ba2e4c35b667af1d6bf20@agner.ch> (raw)
In-Reply-To: <20140928035631.GF12999@dragon>
Am 2014-09-28 05:56, schrieb Shawn Guo:
> On Fri, Sep 26, 2014 at 06:44:01PM +0530, Sanchayan Maity wrote:
>> This patch adds clock enable and disable support
>> for the SNVS peripheral which is required by the
>> SNVS RTC.
>>
>> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
>> ---
>> drivers/rtc/rtc-snvs.c | 48 +++++++++++++++++++++++++++++++++++++++---------
>> 1 file changed, 39 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/rtc/rtc-snvs.c b/drivers/rtc/rtc-snvs.c
>> index fa384fe..f3e8f05 100644
>> --- a/drivers/rtc/rtc-snvs.c
>> +++ b/drivers/rtc/rtc-snvs.c
>> @@ -17,6 +17,7 @@
>> #include <linux/of_device.h>
>> #include <linux/platform_device.h>
>> #include <linux/rtc.h>
>> +#include <linux/clk.h>
>>
>> /* These register offsets are relative to LP (Low Power) range */
>> #define SNVS_LPCR 0x04
>> @@ -39,6 +40,7 @@ struct snvs_rtc_data {
>> void __iomem *ioaddr;
>> int irq;
>> spinlock_t lock;
>> + struct clk *clk;
>> };
>>
>> static u32 rtc_read_lp_counter(void __iomem *ioaddr)
>> @@ -260,8 +262,31 @@ static int snvs_rtc_probe(struct platform_device *pdev)
>> if (data->irq < 0)
>> return data->irq;
>>
>> + ret = devm_request_irq(&pdev->dev, data->irq, snvs_rtc_irq_handler,
>> + IRQF_SHARED, "rtc alarm", &pdev->dev);
>> + if (ret) {
>> + dev_err(&pdev->dev, "failed to request irq %d: %d\n",
>> + data->irq, ret);
>> + return ret;
>> + }
>> +
>> + data->clk = devm_clk_get(&pdev->dev, "snvs");
>> + if (IS_ERR(data->clk)) {
>> + dev_err(&pdev->dev, "failed getting clock, err = %ld\n",
>> + PTR_ERR(data->clk));
>> + ret = PTR_ERR(data->clk);
>> + return ret;
>> + }
>
> No. This will break all i.MX6 devices running a DTB without clock
> definition.
>
Shawn, do you know how this works in i.MX6? Is there no clock gating for
that module or is that clock just missing as of now?
But then, I guess even there is a clock on i.MX6 too, we would still
need to make the clock optional.
--
Stefan
>> +
>> platform_set_drvdata(pdev, data);
>>
>> + ret = clk_prepare_enable(data->clk);
>> + if (ret) {
>> + dev_err(&pdev->dev,
>> + "Could not prepare or enable the snvs clock\n");
>> + return ret;
>> + }
>> +
>> spin_lock_init(&data->lock);
>>
>> /* Initialize glitch detect */
>> @@ -275,23 +300,20 @@ static int snvs_rtc_probe(struct platform_device *pdev)
>>
>> device_init_wakeup(&pdev->dev, true);
>>
>> - ret = devm_request_irq(&pdev->dev, data->irq, snvs_rtc_irq_handler,
>> - IRQF_SHARED, "rtc alarm", &pdev->dev);
>> - if (ret) {
>> - dev_err(&pdev->dev, "failed to request irq %d: %d\n",
>> - data->irq, ret);
>> - return ret;
>> - }
>> -
>> data->rtc = devm_rtc_device_register(&pdev->dev, pdev->name,
>> &snvs_rtc_ops, THIS_MODULE);
>> if (IS_ERR(data->rtc)) {
>> ret = PTR_ERR(data->rtc);
>> dev_err(&pdev->dev, "failed to register rtc: %d\n", ret);
>> - return ret;
>> + goto error_rtc_device_register;
>> }
>>
>> return 0;
>> +
>> +error_rtc_device_register:
>> + clk_disable_unprepare(data->clk);
>> +
>> + return ret;
>> }
>>
>> #ifdef CONFIG_PM_SLEEP
>> @@ -302,16 +324,24 @@ static int snvs_rtc_suspend(struct device *dev)
>> if (device_may_wakeup(dev))
>> enable_irq_wake(data->irq);
>>
>> + clk_disable_unprepare(data->clk);
>> +
>> return 0;
>> }
>>
>> static int snvs_rtc_resume(struct device *dev)
>> {
>> + int ret;
>> +
>> struct snvs_rtc_data *data = dev_get_drvdata(dev);
>>
>> if (device_may_wakeup(dev))
>> disable_irq_wake(data->irq);
>>
>> + ret = clk_prepare_enable(data->clk);
>> + if (ret)
>> + return ret;
>> +
>> return 0;
>> }
>> #endif
>> --
>> 1.7.9.5
>>
next prev parent reply other threads:[~2014-09-29 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 13:13 [PATCH 0/3] Add SNVS clock gating and clock support to rtc-snvs driver Sanchayan Maity
2014-09-26 13:13 ` [PATCH 1/3] ARM: imx: clk-vf610: Add SNVS clock Sanchayan Maity
2014-09-26 13:14 ` [PATCH 2/3] ARM: dts: vf610: Add SNVS node Sanchayan Maity
2014-09-28 4:02 ` Shawn Guo
2014-09-26 13:14 ` [PATCH 3/3] drivers/rtc/rtc-snvs: Add clock support Sanchayan Maity
2014-09-28 3:56 ` Shawn Guo
2014-09-29 12:57 ` Stefan Agner [this message]
2014-09-29 13:05 ` Stefan Agner
2014-09-30 4:57 ` Sanchayan Maity
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=ff3b3c43678ba2e4c35b667af1d6bf20@agner.ch \
--to=stefan@agner.ch \
--cc=a.zummo@towertech.it \
--cc=b35083@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maitysanchayan@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@freescale.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
Powered by JetHome