From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Sergei Ianovich <ynvich@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>
Subject: [rtc-linux] Re: [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer
Date: Mon, 27 Jun 2016 14:45:20 +0200 [thread overview]
Message-ID: <20160627124520.GJ29249@piout.net> (raw)
In-Reply-To: <20160627124432.GI29249@piout.net>
Forgot to add Mark in Cc:
On 27/06/2016 at 14:44:32 +0200, Alexandre Belloni wrote :
> On 27/06/2016 at 14:50:49 +0300, Sergei Ianovich wrote :
> > On Mon, 2016-06-27 at 20:19 +0900, Akinobu Mita wrote:
> > > The rtc-ds1302 driver now implemented using SPI 3wire mode.
> > > But I would like to access it with using three wires connected to
> > > GPIO
> > > lines.
> > >=20
> > > This adds abstraction layer for DS1302 register access in order to
> > > prepare to support for using GPIO lines.=C2=A0=C2=A0This enables to s=
hare
> > > common
> > > code between SPI driver and GPIO driver.
> >=20
> > I don't think this is the right way. DS-1302 is an SPI device, not a
> > GPIO one. It can be connected to a hardware SPI controller or a
> > software one (on top of GPIO or memory).
> >=20
> > Your patch re-adds Microwire SPI control logic to RTC subsystem, which
> > was cleared by my rewrite of drivers/rtc/rtc-ds1302.c. The logic is
> > already present in=C2=A0bitbang_txrx_be_cpha0_lsb() in=C2=A0drivers/spi=
/spi-
> > lp8841-rtc.c.
> >=20
> > I still think you need to implement=C2=A0spi-gpio-3wire with LSB-first
> > support in SPI subsystem instead. It wasn't done when I was adding
> > LP8841 support, because LP8841 was the only use case of Microwire SPI
> > control logic. If you add it, drivers/spi/spi-lp8841-rtc.c can be
> > removed and replaced by a GPIO driver to host a new spi-gpio-3wire
> > device.
>=20
> Well, back in April, we concluded it was not easily doable after
> discussing with Mark and there was still issues after implementing it in
> spi-gpio.
>=20
> My understanding is that while microwire seems compatible with SPI mode
> 0, it actually isn't and this should be treated as a different mode.
> If we want to do something generic, I think we should have a
> microwire-gpio driver. Maybe in the SPI subsystem?
>=20
> How do yo currently select microwire mode for PX270?
>=20
> --=20
> Alexandre Belloni, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
--=20
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--=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-06-27 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:19 [rtc-linux] [PATCH v2 0/2] support control with using GPIO lines Akinobu Mita
2016-06-27 11:19 ` [rtc-linux] [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer Akinobu Mita
2016-06-27 11:50 ` [rtc-linux] " Sergei Ianovich
2016-06-27 12:44 ` Alexandre Belloni
2016-06-27 12:45 ` Alexandre Belloni [this message]
2016-06-27 15:15 ` Sergei Ianovich
2016-07-19 15:13 ` Alexandre Belloni
2016-07-27 18:47 ` Mark Brown
2016-06-27 11:19 ` [rtc-linux] [PATCH v2 2/2] rtc: ds1302: support control with using GPIO lines Akinobu Mita
2016-06-28 20:57 ` [rtc-linux] " Rob Herring
2016-07-08 14:28 ` 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=20160627124520.GJ29249@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=akinobu.mita@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.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