From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Sergei Ianovich <ynvich@gmail.com>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@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>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:REAL TIME CLOCK RTC SUBSYSTEM"
<rtc-linux@googlegroups.com>
Subject: Re: [PATCH v7] rtc: rewrite DS1302 using SPI
Date: Mon, 28 Mar 2016 22:57:13 +0200 [thread overview]
Message-ID: <20160328205713.GA2346@piout.net> (raw)
In-Reply-To: <1456224900-4877-1-git-send-email-ynvich@gmail.com>
On 23/02/2016 at 13:54:57 +0300, Sergei Ianovich wrote :
> DS1302 is half-duplex SPI device. The driver respects this fact now.
>
> Pin configurations should be implemented using SPI subsystem.
>
> Signed-off-by: Sergei Ianovich <ynvich@gmail.com>
> CC: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> CC: Rob Herring <robh@kernel.org>
>
> v6..v7
> * change binding and doc file names
>
> v5..v6
> * rewrite the driver as an SPI slave device
> * use "maxim" for vendor name per Kconfig
> * stop changing device RAM in device presence test
> * only return time from device if valid
> * use burst mode for reading/writing time
> * dropped charging control. I cannot test it, and it looks broken
>
> v4..v5
> * drop THIS_MODULE from struct platform driver
> * use "dallas" for vendor name per vendor-prefixes.txt
>
> v3..v4
> * move DTS bindings to a different patch
>
> v2..v3
> * use usleep_range instead of custom nsleep
> * number change (07/16 -> 09/21)
>
> v0..v2
> * use device tree
> * use devm helpers where possible
> ---
> .../devicetree/bindings/rtc/maxim-ds1302.txt | 46 +++
> drivers/rtc/Kconfig | 15 +-
> drivers/rtc/rtc-ds1302.c | 348 ++++++++++-----------
> 3 files changed, 212 insertions(+), 197 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/rtc/maxim-ds1302.txt
>
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-28 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <397668667-27328-3-git-send-email-ynvich@gmail.com>
2015-12-15 17:45 ` [rtc-linux] [PATCH v5] rtc: support DS1302 RTC on ICP DAS LP-8x4x Sergei Ianovich
2015-12-20 3:38 ` [rtc-linux] " Rob Herring
2015-12-20 12:14 ` Sergei Ianovich
2015-12-22 18:16 ` Rob Herring
2015-12-24 11:04 ` Alexandre Belloni
2015-12-24 11:07 ` Sergei Ianovich
2016-02-22 1:41 ` [rtc-linux] [PATCH v6] rtc: rewrite DS1302 using SPI Sergei Ianovich
2016-02-22 18:45 ` [rtc-linux] " Rob Herring
2016-02-23 10:54 ` [PATCH v7] " Sergei Ianovich
2016-02-23 23:29 ` Rob Herring
2016-03-15 0:18 ` Alexandre Belloni
2016-03-18 10:38 ` Sergei Ianovich
2016-03-28 20:57 ` Alexandre Belloni [this message]
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=20160328205713.GA2346@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--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=robh@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=ynvich@gmail.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