From: Sergei Ianovich <ynvich@gmail.com>
To: Akinobu Mita <akinobu.mita@gmail.com>,
rtc-linux@googlegroups.com, devicetree@vger.kernel.org
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: [rtc-linux] Re: [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer
Date: Mon, 27 Jun 2016 14:50:49 +0300 [thread overview]
Message-ID: <1467028249.3182.11.camel@gmail.com> (raw)
In-Reply-To: <1467026362-29446-2-git-send-email-akinobu.mita@gmail.com>
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 share
> common
> code between SPI driver and GPIO driver.
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).
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.
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
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.
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Ianovich <ynvich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Akinobu Mita
<akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alessandro Zummo
<a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>,
Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer
Date: Mon, 27 Jun 2016 14:50:49 +0300 [thread overview]
Message-ID: <1467028249.3182.11.camel@gmail.com> (raw)
In-Reply-To: <1467026362-29446-2-git-send-email-akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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.
>
> This adds abstraction layer for DS1302 register access in order to
> prepare to support for using GPIO lines. This enables to share
> common
> code between SPI driver and GPIO driver.
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).
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 bitbang_txrx_be_cpha0_lsb() in drivers/spi/spi-
lp8841-rtc.c.
I still think you need to implement spi-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.
--
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.
---
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 email to rtc-linux+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-06-27 11:50 UTC|newest]
Thread overview: 22+ 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 ` 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:19 ` Akinobu Mita
2016-06-27 11:50 ` Sergei Ianovich [this message]
2016-06-27 11:50 ` Sergei Ianovich
2016-06-27 12:44 ` [rtc-linux] " Alexandre Belloni
2016-06-27 12:44 ` Alexandre Belloni
2016-06-27 12:45 ` [rtc-linux] " Alexandre Belloni
2016-06-27 12:45 ` Alexandre Belloni
2016-06-27 15:15 ` [rtc-linux] " Sergei Ianovich
2016-06-27 15:15 ` Sergei Ianovich
2016-07-19 15:13 ` [rtc-linux] " Alexandre Belloni
2016-07-19 15:13 ` Alexandre Belloni
2016-07-27 18:47 ` [rtc-linux] " Mark Brown
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-27 11:19 ` Akinobu Mita
2016-06-28 20:57 ` [rtc-linux] " Rob Herring
2016-06-28 20:57 ` Rob Herring
2016-07-08 14:28 ` [rtc-linux] " Alexandre Belloni
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=1467028249.3182.11.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.