From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Olof Johansson <olof@lixom.net>, Lee Jones <lee.jones@linaro.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Stephen Barber <smbarber@chromium.org>
Subject: Re: [PATCH 3/4] rtc: cros-ec: add cros-ec-rtc driver.
Date: Wed, 18 Jan 2017 03:00:21 +0100 [thread overview]
Message-ID: <20170118020021.rnfchgbmtnrbljck@piout.net> (raw)
In-Reply-To: <20170111165221.17337-3-enric.balletbo@collabora.com>
Hi,
This seems mostly good to me.
On 11/01/2017 at 17:52:20 +0100, Enric Balletbo i Serra wrote :
> From: Stephen Barber <smbarber@chromium.org>
>
> On platforms with a Chrome OS EC, the EC can function as a simple RTC.
> Add a basic driver with this functionality.
>
> Signed-off-by: Stephen Barber <smbarber@chromium.org>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> drivers/rtc/Kconfig | 10 ++
> drivers/rtc/Makefile | 1 +
> drivers/rtc/rtc-cros-ec.c | 416 ++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 427 insertions(+)
> create mode 100644 drivers/rtc/rtc-cros-ec.c
>
> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> index c93c5a8..b58ce06 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -207,6 +207,16 @@ config RTC_DRV_AS3722
> This driver can also be built as a module. If so, the module
> will be called rtc-as3722.
>
> +config RTC_DRV_CROS_EC
> + tristate "Chrome OS EC RTC driver"
> + depends on MFD_CROS_EC
> + help
> + If you say yes here you will get support for the
> + Chrome OS Embedded Controller's RTC.
> +
> + This driver can also be built as a module. If so, the module
> + will be called rtc-cros-ec.
> +
This doesn't look like and i2c RTC, you probably want to put that block
somewhere after "Platform RTC drivers"
> config RTC_DRV_DS1307
> tristate "Dallas/Maxim DS1307/37/38/39/40, ST M41T00, EPSON RX-8025, ISL12057"
> help
> + ret = rtc_valid_tm(&tm);
> + if (ret)
> + dev_err(&pdev->dev, "invalid date/time\n");
> +
nitpick: I'm not sure this is useful. You'll probably know soon enough
that it is invalid as I'm pretty sure something will read the date at
boot time.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-18 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 16:52 [PATCH 1/4] mfd: cros_ec: Add helper for event notifier Enric Balletbo i Serra
2017-01-11 16:52 ` [PATCH 2/4] mfd: cros_ec: Introduce RTC commands and events definitions Enric Balletbo i Serra
2017-01-13 13:23 ` Lee Jones
2017-01-11 16:52 ` [PATCH 3/4] rtc: cros-ec: add cros-ec-rtc driver Enric Balletbo i Serra
2017-01-18 2:00 ` Alexandre Belloni [this message]
2017-01-11 16:52 ` [PATCH 4/4] mfd: cros_ec: add RTC as mfd subdevice Enric Balletbo i Serra
2017-01-18 2:01 ` Alexandre Belloni
2017-01-18 9:13 ` Lee Jones
2017-01-13 13:22 ` [PATCH 1/4] mfd: cros_ec: Add helper for event notifier Lee Jones
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=20170118020021.rnfchgbmtnrbljck@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=enric.balletbo@collabora.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rtc-linux@googlegroups.com \
--cc=smbarber@chromium.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
all inboxes | Powered by JetHome®