diff for duplicates of <1467040517.3182.34.camel@gmail.com> diff --git a/a/1.txt b/N1/1.txt index 2d51b83..ede9312 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,20 +4,19 @@ On Mon, 2016-06-27 at 14:44 +0200, Alexandre Belloni wrote: > > 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- +> > already present in bitbang_txrx_be_cpha0_lsb() in drivers/spi/spi- > > lp8841-rtc.c. -> >=20 -> > I still think you need to implement=C2=A0spi-gpio-3wire with LSB-first +> > +> > 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. ->=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. @@ -30,7 +29,7 @@ On Mon, 2016-06-27 at 14:44 +0200, Alexandre Belloni wrote: I've seen Akinobu Mita report that he added support for 3wire to spi- gpio, and it didn't work. That's not a big difference from where we are now, when there is just no support for 3wire. Adding a working support -for 3wire to spi-gpio needs 2^4 - 2^2 =3D 12 new bitbang functions to +for 3wire to spi-gpio needs 2^4 - 2^2 = 12 new bitbang functions to handle 3wire and lsb-first modes. It is a bit difficult to test all of them. I don't have enough hardware for example. In addition, it is unlikely that a 3wire GPIO SPI master would host more than a single @@ -47,16 +46,14 @@ transfer. This is an example of a pretty sophisticated hardware controller. I actually use a simple software controller in LP8841. The driver is -in=C2=A0drivers/spi/spi-lp8841-rtc.c. +in drivers/spi/spi-lp8841-rtc.c. ---=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. +--- +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. diff --git a/a/content_digest b/N1/content_digest index 3511cb7..0758abf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,14 +2,15 @@ "ref\01467026362-29446-2-git-send-email-akinobu.mita@gmail.com\0" "ref\01467028249.3182.11.camel@gmail.com\0" "ref\020160627124432.GI29249@piout.net\0" - "From\0Sergei Ianovich <ynvich@gmail.com>\0" - "Subject\0[rtc-linux] Re: [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer\0" + "ref\020160627124432.GI29249-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org\0" + "From\0Sergei Ianovich <ynvich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" + "Subject\0Re: [PATCH v2 1/2] rtc: ds1302: add register access abstraction layer\0" "Date\0Mon, 27 Jun 2016 18:15:17 +0300\0" - "To\0Alexandre Belloni <alexandre.belloni@free-electrons.com>\0" - "Cc\0Akinobu Mita <akinobu.mita@gmail.com>" - rtc-linux@googlegroups.com - devicetree@vger.kernel.org - " Alessandro Zummo <a.zummo@towertech.it>\0" + "To\0Alexandre Belloni <alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>\0" + "Cc\0Akinobu Mita <akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>" + rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + " Alessandro Zummo <a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>\0" "\00:1\0" "b\0" "On Mon, 2016-06-27 at 14:44 +0200, Alexandre Belloni wrote:\n" @@ -18,20 +19,19 @@ "> > a\n" "> > GPIO one. It can be connected to a hardware SPI controller or a\n" "> > software one (on top of GPIO or memory).\n" - "> >=20\n" + "> > \n" "> > Your patch re-adds Microwire SPI control logic to RTC subsystem, which\n" "> > was cleared by my rewrite of drivers/rtc/rtc-ds1302.c. The logic is\n" - "> > already present in=C2=A0bitbang_txrx_be_cpha0_lsb() in=C2=A0drivers/spi=\n" - "/spi-\n" + "> > already present in\302\240bitbang_txrx_be_cpha0_lsb() in\302\240drivers/spi/spi-\n" "> > lp8841-rtc.c.\n" - "> >=20\n" - "> > I still think you need to implement=C2=A0spi-gpio-3wire with LSB-first\n" + "> > \n" + "> > I still think you need to implement\302\240spi-gpio-3wire with LSB-first\n" "> > support in SPI subsystem instead. It wasn't done when I was adding\n" "> > LP8841 support, because LP8841 was the only use case of Microwire SPI\n" "> > control logic. If you add it, drivers/spi/spi-lp8841-rtc.c can be\n" "> > removed and replaced by a GPIO driver to host a new spi-gpio-3wire\n" "> > device.\n" - ">=20\n" + "> \n" "> Well, back in April, we concluded it was not easily doable after\n" "> discussing with Mark and there was still issues after implementing it in\n" "> spi-gpio.\n" @@ -44,7 +44,7 @@ "I've seen Akinobu Mita report that he added support for 3wire to spi-\n" "gpio, and it didn't work. That's not a big difference from where we are\n" "now, when there is just no support for 3wire. Adding a working support\n" - "for 3wire to spi-gpio needs 2^4 - 2^2 =3D 12 new bitbang functions to\n" + "for 3wire to spi-gpio needs 2^4 - 2^2 = 12 new bitbang functions to\n" "handle 3wire and lsb-first modes. It is a bit difficult to test all of\n" "them. I don't have enough hardware for example. In addition, it is\n" "unlikely that a 3wire GPIO SPI master would host more than a single\n" @@ -61,18 +61,16 @@ "controller.\n" "\n" "I actually use a simple software controller in LP8841. The driver is\n" - "in=C2=A0drivers/spi/spi-lp8841-rtc.c.\n" + "in\302\240drivers/spi/spi-lp8841-rtc.c.\n" "\n" - "--=20\n" + "-- \n" "You received this message because you are subscribed to \"rtc-linux\".\n" "Membership options at http://groups.google.com/group/rtc-linux .\n" "Please read http://groups.google.com/group/rtc-linux/web/checklist\n" "before submitting a driver.\n" - "---=20\n" - "You received this message because you are subscribed to the Google Groups \"=\n" - "rtc-linux\" group.\n" - "To unsubscribe from this group and stop receiving emails from it, send an e=\n" - "mail to rtc-linux+unsubscribe@googlegroups.com.\n" + "--- \n" + "You received this message because you are subscribed to the Google Groups \"rtc-linux\" group.\n" + "To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org\n" For more options, visit https://groups.google.com/d/optout. -f4af83cea85cc39b4939d6e89735e125e41d4d2f1fedd042d6a1b6cbf676394a +6160b94c2e3355ba397ed436e4d56ab25725c4aa65418df3437cc4af2f97f725
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.