From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] [PATCH v3 2/3] rtc: mediatek: Add MT6397 RTC driver
Date: Tue, 5 May 2015 22:00:10 +0200 [thread overview]
Message-ID: <20150505200010.GP4276@piout.net> (raw)
In-Reply-To: <1430206556-18254-3-git-send-email-eddie.huang@mediatek.com>
Hi,
This looks mostly good. Could you align the wrapped function parameters
to the open parenthesis (use checkpatch --strict)?
On 28/04/2015 at 15:35:55 +0800, Eddie Huang wrote :
> +static int mtk_rtc_write_trigger(struct mt6397_rtc *rtc)
> +{
> + unsigned long timeout = jiffies + HZ;
> + int ret;
> + u32 data;
> +
> + ret = regmap_write(rtc->regmap, rtc->addr_base + RTC_WRTGR, 1);
> + if (ret < 0)
> + return ret;
> +
> + do {
> + cpu_relax();
> + ret = regmap_read(rtc->regmap, rtc->addr_base + RTC_BBPU,
> + &data);
> + if (ret < 0)
> + goto exit;
> + } while ((data & RTC_BBPU_CBUSY) && time_after(timeout, jiffies));
> +
Shouldn't you return -ETIMEDOUT if the loop breaks because of time_after?
Thanks,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-05 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:35 [PATCH v3 0/3] Add Mediatek SoC RTC driver Eddie Huang
2015-04-28 7:35 ` [PATCH v3 1/3] mfd: provide RTC resource in MT6397 MFD Eddie Huang
2015-04-28 7:45 ` Uwe Kleine-König
2015-04-28 10:07 ` Lee Jones
2015-04-28 7:35 ` [PATCH v3 2/3] rtc: mediatek: Add MT6397 RTC driver Eddie Huang
2015-05-05 20:00 ` Alexandre Belloni [this message]
2015-05-05 20:44 ` [rtc-linux] " Joe Perches
2015-05-05 21:01 ` Alexandre Belloni
2015-05-06 3:32 ` Eddie Huang
2015-04-28 7:35 ` [PATCH v3 3/3] MAINTAINERS: add Mediatek " Eddie Huang
2015-05-05 20:03 ` [rtc-linux] " Alexandre Belloni
2015-05-06 3:36 ` Eddie Huang
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=20150505200010.GP4276@piout.net \
--to=alexandre.belloni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).