From: Sergei Ianovich <ynvich@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Akinobu Mita <akinobu.mita@gmail.com>
Cc: rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>
Subject: [rtc-linux] Re: [PATCH 0/4] support control with using GPIO lines
Date: Sun, 10 Apr 2016 18:23:01 +0300 [thread overview]
Message-ID: <1460301781.17404.171.camel@gmail.com> (raw)
In-Reply-To: <20160410151237.GD5377@piout.net>
On Sun, 2016-04-10 at 17:12 +0200, Alexandre Belloni wrote:
> Hi,
>=20
> On 10/04/2016 at 23:59:22 +0900, Akinobu Mita wrote :
> >=20
> > This series adds support access to DS1302 with GPIO lines.
> >=20
> > Recently rtc-ds1302 is rewritten using SPI 3wire mode.=C2=A0=C2=A0This =
adds
> > another platform driver using GPIO while supporting both modes.
> >=20
> > Thie series first fixes two problems I found while tesing, secondly
> > introduces the abstraction layer for the register access which
> > enables
> > to share the most code between spi and platform driver, and adds
> > the platform driver using GPIO.
> >=20
> Well, isn't spi-gpio fitting for that use case? I'd like to avoid
> open
> coding gpio bitbanging in the driver.
No, unfortunately. I've investigated this possibility for my platform.
spi-gpio doesn't support LSB-first and 3-wire options. Adding support
there is a very big change. The best way to add GPIO support is to
create spi-gpio-3wire with LSB-first support.
--=20
--=20
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.
---=20
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 e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-04-10 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 14:59 [rtc-linux] [PATCH 0/4] support control with using GPIO lines Akinobu Mita
2016-04-10 14:59 ` [rtc-linux] [PATCH 1/4] rtc: ds1302: fix error check in set_time Akinobu Mita
2016-04-10 15:17 ` [rtc-linux] " Alexandre Belloni
2016-04-10 14:59 ` [rtc-linux] [PATCH 2/4] rtc: ds1302: fix write value for day of week register Akinobu Mita
2016-04-10 15:17 ` [rtc-linux] " Alexandre Belloni
2016-04-10 14:59 ` [rtc-linux] [PATCH 3/4] rtc: ds1302: add register access abstraction layer Akinobu Mita
2016-04-10 14:59 ` [rtc-linux] [PATCH 4/4] rtc: ds1302: support control with using GPIO lines Akinobu Mita
2016-04-10 15:12 ` [rtc-linux] Re: [PATCH 0/4] " Alexandre Belloni
2016-04-10 15:23 ` Sergei Ianovich [this message]
2016-04-10 15:38 ` Alexandre Belloni
2016-04-12 1:25 ` Mark Brown
2016-04-26 19:53 ` Akinobu Mita
2016-04-27 13:50 ` Mark Brown
2016-04-27 14:03 ` Sergei Ianovich
2016-04-29 5:40 ` Akinobu Mita
2016-06-26 0:55 ` Alexandre Belloni
2016-06-27 10:23 ` Akinobu Mita
2016-04-11 19:46 ` Rob Herring
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=1460301781.17404.171.camel@gmail.com \
--to=ynvich@gmail.com \
--cc=a.zummo@towertech.it \
--cc=akinobu.mita@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox