From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend] rtc: Adding support for spear rtc
Date: Mon, 25 Apr 2011 15:21:17 -0700 [thread overview]
Message-ID: <20110425152117.424cdba1.akpm@linux-foundation.org> (raw)
In-Reply-To: <b5f52fa9b1acd0c524ecb357788b22a1b6d8fa9c.1303730912.git.viresh.kumar@st.com>
On Mon, 25 Apr 2011 17:00:26 +0530
Viresh Kumar <viresh.kumar@st.com> wrote:
> From: Rajeev Kumar <rajeev-dlh.kumar@st.com>
>
> Signed-off-by: Rajeev Kumar <rajeev-dlh.kumar@st.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> ---
> drivers/rtc/Kconfig | 8 +
> drivers/rtc/Makefile | 1 +
> drivers/rtc/rtc-spear.c | 534 +++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 543 insertions(+), 0 deletions(-)
The driver looks nice and clean.
>
> ...
>
> +static void rtc_wait_not_busy(struct spear_rtc_config *config)
> +{
> + int status, count = 0;
> + unsigned long flags;
> +
> + /* Assuming BUSY may stay active for 80 msec) */
> + for (count = 0; count < 80; count++) {
> + spin_lock_irqsave(&config->lock, flags);
> + status = readl(config->ioaddr + STATUS_REG);
> + spin_unlock_irqrestore(&config->lock, flags);
> + if ((status & STATUS_BUSY) == 0)
> + break;
> + /* check status busy, after each msec */
> + msleep(1);
> + }
> +}
Question. What activity causes STATUS_BUSY to become set?
>
> ...
>
> +static int spear_rtc_read_time(struct device *dev, struct rtc_time *tm)
> +{
> + struct platform_device *pdev = to_platform_device(dev);
> + struct rtc_device *rtc = platform_get_drvdata(pdev);
> + struct spear_rtc_config *config = dev_get_drvdata(&rtc->dev);
> + unsigned int time, date;
> +
> + /* we don't report wday/yday/isdst ... */
> + rtc_wait_not_busy(config);
Because here, we've waited for STATUS_BUSY to clear, but we don't
appear to have taken any steps to prevent it from getting set again
while these steps:
> + time = readl(config->ioaddr + TIME_REG);
> + date = readl(config->ioaddr + DATE_REG);
> + tm->tm_sec = (time >> SECOND_SHIFT) & SECOND_MASK;
> + tm->tm_min = (time >> MINUTE_SHIFT) & MIN_MASK;
> + tm->tm_hour = (time >> HOUR_SHIFT) & HOUR_MASK;
> + tm->tm_mday = (date >> MDAY_SHIFT) & DAY_MASK;
> + tm->tm_mon = (date >> MONTH_SHIFT) & MONTH_MASK;
> + tm->tm_year = (date >> YEAR_SHIFT) & YEAR_MASK;
are in progress?
> + bcd2tm(tm);
> + return 0;
> +}
>
> ...
>
next prev parent reply other threads:[~2011-04-25 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 11:30 [PATCH resend] rtc: Adding support for spear rtc Viresh Kumar
2011-04-25 22:21 ` Andrew Morton [this message]
2011-04-28 5:41 ` rajeev
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=20110425152117.424cdba1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.