All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <5538EF8D.5050209@ti.com>

diff --git a/a/1.txt b/N1/1.txt
index e014415..7bf701e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -60,42 +60,42 @@ On 04/23/2015 05:17 AM, Grygorii.Strashko@linaro.org wrote:
 >> 2.    Write 0x47 to the Alarm0 Minutes register
 >> [0x0B].
 >> 3.    Write 0x71 to the Alarm0 Hours register [0x0C]
->> – 11 hours in 12-hour format.
->> 4.    Write 0x72 to the Alarm0 Day register [0x0D] –
+>> =E2=80=93 11 hours in 12-hour format.
+>> 4.    Write 0x72 to the Alarm0 Day register [0x0D] =E2=80=93
 >> Tuesday + Alarm Polarity Low + Match on all.
 >> The Alarm0 Interrupt Flag is also cleared.
 >> 5.    Write 0x14 to the Alarm0 Date register [0x0E].
 >> 6.    Write 0x08 to the Alarm0 Month register [0x0F].
 >> With all the Alarm0 registers set we can now activate
 >> the Alarm0 on the Control register.
->> 7.    Write 0x10 to the Control register [0x07] –
+>> 7.    Write 0x10 to the Control register [0x07] =E2=80=93
 >> Alarm0 enabled no CLKOUT, Alarm1 disabled
 >>
 >> before this patch we do ( http://pastebin.ubuntu.com/10863880/)
->> 	CONTROL r[7] = 0x90 (OUT=1, ALM0EN=1)
->> 	OSCTRIM r[8] = 0x00
->> 	EEUNLOCK r[9] = 0x00
->> 	ALM0SEC r[A] = 0x01
->> 	ALM0MIN r[B] = 0x45
->> 	ALM0HOUR r[C] = 0x23
->> 	ALM0WKDAY r[D] = 0x75 <-ALMOIF is cleared
->> 	ALM0DATE r[E] = 0x09
->> 	ALM0MTH r[F] = 0x04
->> 	RSRVED r[10] = 0x01
+>> 	CONTROL r[7] =3D 0x90 (OUT=3D1, ALM0EN=3D1)
+>> 	OSCTRIM r[8] =3D 0x00
+>> 	EEUNLOCK r[9] =3D 0x00
+>> 	ALM0SEC r[A] =3D 0x01
+>> 	ALM0MIN r[B] =3D 0x45
+>> 	ALM0HOUR r[C] =3D 0x23
+>> 	ALM0WKDAY r[D] =3D 0x75 <-ALMOIF is cleared
+>> 	ALM0DATE r[E] =3D 0x09
+>> 	ALM0MTH r[F] =3D 0x04
+>> 	RSRVED r[10] =3D 0x01
 >>
 >> with this patch, we do:
->> burst(	CONTROL r[7] = 0x80 (OUT=1)
->> 	OSCTRIM r[8] = 0x00
->> 	EEUNLOCK r[9] = 0x00
->> 	ALM0SEC r[A] = 0x01
->> 	ALM0MIN r[B] = 0x45
->> 	ALM0HOUR r[C] = 0x23
->> 	ALM0WKDAY r[D] = 0x75 <-ALMOIF is cleared
->> 	ALM0DATE r[E] = 0x09
->> 	ALM0MTH r[F] = 0x04
->> 	RSRVED r[10] = 0x01
+>> burst(	CONTROL r[7] =3D 0x80 (OUT=3D1)
+>> 	OSCTRIM r[8] =3D 0x00
+>> 	EEUNLOCK r[9] =3D 0x00
+>> 	ALM0SEC r[A] =3D 0x01
+>> 	ALM0MIN r[B] =3D 0x45
+>> 	ALM0HOUR r[C] =3D 0x23
+>> 	ALM0WKDAY r[D] =3D 0x75 <-ALMOIF is cleared
+>> 	ALM0DATE r[E] =3D 0x09
+>> 	ALM0MTH r[F] =3D 0x04
+>> 	RSRVED r[10] =3D 0x01
 >> )
->> 	CONTROL r[7] = 0x90 (OUT=1, ALM0EN=1)
+>> 	CONTROL r[7] =3D 0x90 (OUT=3D1, ALM0EN=3D1)
 >>
 >> Which is slightly unoptimal way of what the app note recommends. - as
 >> I mentioned earlier in this thread, I will try and do optimizations in
@@ -104,13 +104,26 @@ On 04/23/2015 05:17 AM, Grygorii.Strashko@linaro.org wrote:
 >> Given that Andrew had picked up this patch, I dont see a reason to
 >> respin this yet. but will include the app note for future patches -
 >> thanks for pointing it out to me.
-> 
+>=20
 > ^^ Up to you. Np, Always yours!
 
 Considering the narrow focus of the current patch (which does fix an
 issue that it attempts to), can I get an Ack?
 
 
--- 
+--=20
 Regards,
 Nishanth Menon
+
+--=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.
diff --git a/a/content_digest b/N1/content_digest
index 7ff2e94..bd72236 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,14 +3,14 @@
  "ref\055383625.3070108@ti.com\0"
  "ref\05538C6C2.5010508@linaro.org\0"
  "From\0Nishanth Menon <nm@ti.com>\0"
- "Subject\0Re: [PATCH V2] drivers/rtc/rtc-ds1307.c: Enable the mcp794xx alarm after programming time\0"
+ "Subject\0[rtc-linux] Re: [PATCH V2] drivers/rtc/rtc-ds1307.c: Enable the mcp794xx alarm after programming time\0"
  "Date\0Thu, 23 Apr 2015 08:11:41 -0500\0"
  "To\0Grygorii.Strashko@linaro.org <grygorii.strashko@linaro.org>"
   Alexandre Belloni <alexandre.belloni@free-electrons.com>
  " Alessandro Zummo <a.zummo@towertech.it>\0"
- "Cc\0linux-omap@vger.kernel.org"
-  linux-kernel@vger.kernel.org
- " rtc-linux@googlegroups.com\0"
+ "Cc\0<linux-omap@vger.kernel.org>"
+  <linux-kernel@vger.kernel.org>
+ " <rtc-linux@googlegroups.com>\0"
  "\00:1\0"
  "b\0"
  "On 04/23/2015 05:17 AM, Grygorii.Strashko@linaro.org wrote:\n"
@@ -75,42 +75,42 @@
  ">> 2.    Write 0x47 to the Alarm0 Minutes register\n"
  ">> [0x0B].\n"
  ">> 3.    Write 0x71 to the Alarm0 Hours register [0x0C]\n"
- ">> \342\200\223 11 hours in 12-hour format.\n"
- ">> 4.    Write 0x72 to the Alarm0 Day register [0x0D] \342\200\223\n"
+ ">> =E2=80=93 11 hours in 12-hour format.\n"
+ ">> 4.    Write 0x72 to the Alarm0 Day register [0x0D] =E2=80=93\n"
  ">> Tuesday + Alarm Polarity Low + Match on all.\n"
  ">> The Alarm0 Interrupt Flag is also cleared.\n"
  ">> 5.    Write 0x14 to the Alarm0 Date register [0x0E].\n"
  ">> 6.    Write 0x08 to the Alarm0 Month register [0x0F].\n"
  ">> With all the Alarm0 registers set we can now activate\n"
  ">> the Alarm0 on the Control register.\n"
- ">> 7.    Write 0x10 to the Control register [0x07] \342\200\223\n"
+ ">> 7.    Write 0x10 to the Control register [0x07] =E2=80=93\n"
  ">> Alarm0 enabled no CLKOUT, Alarm1 disabled\n"
  ">>\n"
  ">> before this patch we do ( http://pastebin.ubuntu.com/10863880/)\n"
- ">> \tCONTROL r[7] = 0x90 (OUT=1, ALM0EN=1)\n"
- ">> \tOSCTRIM r[8] = 0x00\n"
- ">> \tEEUNLOCK r[9] = 0x00\n"
- ">> \tALM0SEC r[A] = 0x01\n"
- ">> \tALM0MIN r[B] = 0x45\n"
- ">> \tALM0HOUR r[C] = 0x23\n"
- ">> \tALM0WKDAY r[D] = 0x75 <-ALMOIF is cleared\n"
- ">> \tALM0DATE r[E] = 0x09\n"
- ">> \tALM0MTH r[F] = 0x04\n"
- ">> \tRSRVED r[10] = 0x01\n"
+ ">> \tCONTROL r[7] =3D 0x90 (OUT=3D1, ALM0EN=3D1)\n"
+ ">> \tOSCTRIM r[8] =3D 0x00\n"
+ ">> \tEEUNLOCK r[9] =3D 0x00\n"
+ ">> \tALM0SEC r[A] =3D 0x01\n"
+ ">> \tALM0MIN r[B] =3D 0x45\n"
+ ">> \tALM0HOUR r[C] =3D 0x23\n"
+ ">> \tALM0WKDAY r[D] =3D 0x75 <-ALMOIF is cleared\n"
+ ">> \tALM0DATE r[E] =3D 0x09\n"
+ ">> \tALM0MTH r[F] =3D 0x04\n"
+ ">> \tRSRVED r[10] =3D 0x01\n"
  ">>\n"
  ">> with this patch, we do:\n"
- ">> burst(\tCONTROL r[7] = 0x80 (OUT=1)\n"
- ">> \tOSCTRIM r[8] = 0x00\n"
- ">> \tEEUNLOCK r[9] = 0x00\n"
- ">> \tALM0SEC r[A] = 0x01\n"
- ">> \tALM0MIN r[B] = 0x45\n"
- ">> \tALM0HOUR r[C] = 0x23\n"
- ">> \tALM0WKDAY r[D] = 0x75 <-ALMOIF is cleared\n"
- ">> \tALM0DATE r[E] = 0x09\n"
- ">> \tALM0MTH r[F] = 0x04\n"
- ">> \tRSRVED r[10] = 0x01\n"
+ ">> burst(\tCONTROL r[7] =3D 0x80 (OUT=3D1)\n"
+ ">> \tOSCTRIM r[8] =3D 0x00\n"
+ ">> \tEEUNLOCK r[9] =3D 0x00\n"
+ ">> \tALM0SEC r[A] =3D 0x01\n"
+ ">> \tALM0MIN r[B] =3D 0x45\n"
+ ">> \tALM0HOUR r[C] =3D 0x23\n"
+ ">> \tALM0WKDAY r[D] =3D 0x75 <-ALMOIF is cleared\n"
+ ">> \tALM0DATE r[E] =3D 0x09\n"
+ ">> \tALM0MTH r[F] =3D 0x04\n"
+ ">> \tRSRVED r[10] =3D 0x01\n"
  ">> )\n"
- ">> \tCONTROL r[7] = 0x90 (OUT=1, ALM0EN=1)\n"
+ ">> \tCONTROL r[7] =3D 0x90 (OUT=3D1, ALM0EN=3D1)\n"
  ">>\n"
  ">> Which is slightly unoptimal way of what the app note recommends. - as\n"
  ">> I mentioned earlier in this thread, I will try and do optimizations in\n"
@@ -119,15 +119,28 @@
  ">> Given that Andrew had picked up this patch, I dont see a reason to\n"
  ">> respin this yet. but will include the app note for future patches -\n"
  ">> thanks for pointing it out to me.\n"
- "> \n"
+ ">=20\n"
  "> ^^ Up to you. Np, Always yours!\n"
  "\n"
  "Considering the narrow focus of the current patch (which does fix an\n"
  "issue that it attempts to), can I get an Ack?\n"
  "\n"
  "\n"
- "-- \n"
+ "--=20\n"
  "Regards,\n"
- Nishanth Menon
+ "Nishanth Menon\n"
+ "\n"
+ "--=20\n"
+ "--=20\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"
+ For more options, visit https://groups.google.com/d/optout.
 
-c2022dcffa6496e26b14097108c76f463288f15074cd554d86677774182bb80a
+8b6e6d744e085665a205140fdd40ee326be998b49d48a434136017883875dba0

diff --git a/a/content_digest b/N2/content_digest
index 7ff2e94..4fec4b1 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -8,9 +8,9 @@
  "To\0Grygorii.Strashko@linaro.org <grygorii.strashko@linaro.org>"
   Alexandre Belloni <alexandre.belloni@free-electrons.com>
  " Alessandro Zummo <a.zummo@towertech.it>\0"
- "Cc\0linux-omap@vger.kernel.org"
-  linux-kernel@vger.kernel.org
- " rtc-linux@googlegroups.com\0"
+ "Cc\0<linux-omap@vger.kernel.org>"
+  <linux-kernel@vger.kernel.org>
+ " <rtc-linux@googlegroups.com>\0"
  "\00:1\0"
  "b\0"
  "On 04/23/2015 05:17 AM, Grygorii.Strashko@linaro.org wrote:\n"
@@ -130,4 +130,4 @@
  "Regards,\n"
  Nishanth Menon
 
-c2022dcffa6496e26b14097108c76f463288f15074cd554d86677774182bb80a
+ff4b5569790dfe7e9b1001914f27d2d170a9c35bf4d8cba5b3a18007a99657fa

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.