From: Joshua Henderson <joshua.henderson@microchip.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Alessandro Zummo <a.zummo@towertech.it>,
<rtc-linux@googlegroups.com>
Subject: [rtc-linux] Re: [PATCH v2 2/2] rtc: rtc-pic32: Add PIC32 real time clock driver
Date: Thu, 25 Feb 2016 09:23:55 -0700 [thread overview]
Message-ID: <56CF2A9B.5080005@microchip.com> (raw)
In-Reply-To: <20160224222555.GA12073@piout.net>
On 02/24/2016 03:25 PM, Alexandre Belloni wrote:
> Hi,
>
> On 19/02/2016 at 11:09:45 -0700, Joshua Henderson wrote :
>> +static int pic32_rtc_gettime(struct device *dev, struct rtc_time *rtc_tm)
>> +{
>> + struct pic32_rtc_dev *pdata = dev_get_drvdata(dev);
>> + void __iomem *base = pdata->reg_base;
>> + unsigned int tries = 0;
>> +
>> + clk_enable(pdata->clk);
>> +
>> + do {
>> + rtc_tm->tm_hour = readb(base + PIC32_RTCHOUR);
>> + rtc_tm->tm_min = readb(base + PIC32_RTCMIN);
>> + rtc_tm->tm_mon = readb(base + PIC32_RTCMON);
>> + rtc_tm->tm_mday = readb(base + PIC32_RTCDAY);
>> + rtc_tm->tm_year = readb(base + PIC32_RTCYEAR);
>> + rtc_tm->tm_sec = readb(base + PIC32_RTCSEC);
>> +
>> + /*
>> + * The only way to work out whether the system was mid-update
>> + * when we read it is to check the second counter, and if it
>> + * is zero, then we re-try the entire read.
>> + */
>> + tries = 1;
>> + } while (rtc_tm->tm_sec == 0 && tries < 2);
>> +
>
> This doesn't seem right. It will wait up to a second as tries will
> always be less than 2, this is probably not what you want.
Dang good catch. When fixed, it will work as expected:
# hwclock
tries 1
Sun Oct 17 19:23:59 2010 0.000000 seconds
# hwclock
tries 1
tries 2
Sun Oct 17 19:24:00 2010 0.000000 seconds
# hwclock
tries 1
Sun Oct 17 19:24:01 2010 0.000000 seconds
Josh
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Henderson <joshua.henderson-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
To: Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Alessandro Zummo
<a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH v2 2/2] rtc: rtc-pic32: Add PIC32 real time clock driver
Date: Thu, 25 Feb 2016 09:23:55 -0700 [thread overview]
Message-ID: <56CF2A9B.5080005@microchip.com> (raw)
In-Reply-To: <20160224222555.GA12073-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
On 02/24/2016 03:25 PM, Alexandre Belloni wrote:
> Hi,
>
> On 19/02/2016 at 11:09:45 -0700, Joshua Henderson wrote :
>> +static int pic32_rtc_gettime(struct device *dev, struct rtc_time *rtc_tm)
>> +{
>> + struct pic32_rtc_dev *pdata = dev_get_drvdata(dev);
>> + void __iomem *base = pdata->reg_base;
>> + unsigned int tries = 0;
>> +
>> + clk_enable(pdata->clk);
>> +
>> + do {
>> + rtc_tm->tm_hour = readb(base + PIC32_RTCHOUR);
>> + rtc_tm->tm_min = readb(base + PIC32_RTCMIN);
>> + rtc_tm->tm_mon = readb(base + PIC32_RTCMON);
>> + rtc_tm->tm_mday = readb(base + PIC32_RTCDAY);
>> + rtc_tm->tm_year = readb(base + PIC32_RTCYEAR);
>> + rtc_tm->tm_sec = readb(base + PIC32_RTCSEC);
>> +
>> + /*
>> + * The only way to work out whether the system was mid-update
>> + * when we read it is to check the second counter, and if it
>> + * is zero, then we re-try the entire read.
>> + */
>> + tries = 1;
>> + } while (rtc_tm->tm_sec == 0 && tries < 2);
>> +
>
> This doesn't seem right. It will wait up to a second as tries will
> always be less than 2, this is probably not what you want.
Dang good catch. When fixed, it will work as expected:
# hwclock
tries 1
Sun Oct 17 19:23:59 2010 0.000000 seconds
# hwclock
tries 1
tries 2
Sun Oct 17 19:24:00 2010 0.000000 seconds
# hwclock
tries 1
Sun Oct 17 19:24:01 2010 0.000000 seconds
Josh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Henderson <joshua.henderson@microchip.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Alessandro Zummo <a.zummo@towertech.it>,
<rtc-linux@googlegroups.com>
Subject: Re: [PATCH v2 2/2] rtc: rtc-pic32: Add PIC32 real time clock driver
Date: Thu, 25 Feb 2016 09:23:55 -0700 [thread overview]
Message-ID: <56CF2A9B.5080005@microchip.com> (raw)
In-Reply-To: <20160224222555.GA12073@piout.net>
On 02/24/2016 03:25 PM, Alexandre Belloni wrote:
> Hi,
>
> On 19/02/2016 at 11:09:45 -0700, Joshua Henderson wrote :
>> +static int pic32_rtc_gettime(struct device *dev, struct rtc_time *rtc_tm)
>> +{
>> + struct pic32_rtc_dev *pdata = dev_get_drvdata(dev);
>> + void __iomem *base = pdata->reg_base;
>> + unsigned int tries = 0;
>> +
>> + clk_enable(pdata->clk);
>> +
>> + do {
>> + rtc_tm->tm_hour = readb(base + PIC32_RTCHOUR);
>> + rtc_tm->tm_min = readb(base + PIC32_RTCMIN);
>> + rtc_tm->tm_mon = readb(base + PIC32_RTCMON);
>> + rtc_tm->tm_mday = readb(base + PIC32_RTCDAY);
>> + rtc_tm->tm_year = readb(base + PIC32_RTCYEAR);
>> + rtc_tm->tm_sec = readb(base + PIC32_RTCSEC);
>> +
>> + /*
>> + * The only way to work out whether the system was mid-update
>> + * when we read it is to check the second counter, and if it
>> + * is zero, then we re-try the entire read.
>> + */
>> + tries = 1;
>> + } while (rtc_tm->tm_sec == 0 && tries < 2);
>> +
>
> This doesn't seem right. It will wait up to a second as tries will
> always be less than 2, this is probably not what you want.
Dang good catch. When fixed, it will work as expected:
# hwclock
tries 1
Sun Oct 17 19:23:59 2010 0.000000 seconds
# hwclock
tries 1
tries 2
Sun Oct 17 19:24:00 2010 0.000000 seconds
# hwclock
tries 1
Sun Oct 17 19:24:01 2010 0.000000 seconds
Josh
next prev parent reply other threads:[~2016-02-25 16:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 18:09 [rtc-linux] [PATCH v2 2/2] rtc: rtc-pic32: Add PIC32 real time clock driver Joshua Henderson
2016-02-19 18:09 ` Joshua Henderson
2016-02-19 18:09 ` Joshua Henderson
2016-02-19 18:17 ` [rtc-linux] " Alexandre Belloni
2016-02-19 18:17 ` Alexandre Belloni
2016-02-19 18:17 ` Alexandre Belloni
2016-02-23 17:36 ` [rtc-linux] " Joshua Henderson
2016-02-23 17:36 ` Joshua Henderson
2016-02-23 17:36 ` Joshua Henderson
2016-02-24 22:25 ` [rtc-linux] " Alexandre Belloni
2016-02-24 22:25 ` Alexandre Belloni
2016-02-24 22:25 ` Alexandre Belloni
2016-02-25 16:23 ` Joshua Henderson [this message]
2016-02-25 16:23 ` Joshua Henderson
2016-02-25 16:23 ` Joshua Henderson
2016-02-25 16:54 ` [rtc-linux] " Alexandre Belloni
2016-02-25 16:54 ` Alexandre Belloni
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=56CF2A9B.5080005@microchip.com \
--to=joshua.henderson@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.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 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.