diff for duplicates of <20160721111008.GE4446@piout.net> diff --git a/a/1.txt b/N1/1.txt index 1defa40..782c48d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,35 +1,22 @@ -On 21/07/2016 at 12:41:30 +0200, Beno=C3=AEt Th=C3=A9baudeau wrote : -> The I=C2=B2C NACK issue of the RV-8803 may occur after any I=C2=B2C START +On 21/07/2016 at 12:41:30 +0200, Benoît Thébaudeau wrote : +> The I²C NACK issue of the RV-8803 may occur after any I²C START > condition, depending on the timings. Consequently, the workaround must -> be applied for all the I=C2=B2C transfers. ->=20 -> This commit abstracts the I=C2=B2C transfer code into register access -> functions. This avoids duplicating the I=C2=B2C workaround everywhere. Th= -is +> be applied for all the I²C transfers. +> +> This commit abstracts the I²C transfer code into register access +> functions. This avoids duplicating the I²C workaround everywhere. This > also avoids the duplication of the code handling the return value of > i2c_smbus_read_i2c_block_data(). Error messages are issued in case of > definitive register access failures (if the workaround fails). This -> change also makes the I=C2=B2C transfer return value checks consistent. ->=20 +> change also makes the I²C transfer return value checks consistent. +> Well, my initial idea was that the workaround is actually needed only for operations that are not restartable from userspace. Did you it that bug? On which RTC? ---=20 +-- Alexandre Belloni, Free Electrons Embedded Linux and Kernel 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. diff --git a/a/content_digest b/N1/content_digest index aac0318..84455a7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,7 +1,7 @@ "ref\01469097692-103146-1-git-send-email-benoit@wsystem.com\0" "ref\01469097692-103146-4-git-send-email-benoit@wsystem.com\0" "From\0Alexandre Belloni <alexandre.belloni@free-electrons.com>\0" - "Subject\0[rtc-linux] Re: [PATCH 4/6] rtc: rv8803: Always apply the I\302\262C workaround\0" + "Subject\0Re: [PATCH 4/6] rtc: rv8803: Always apply the I\302\262C workaround\0" "Date\0Thu, 21 Jul 2016 13:10:08 +0200\0" "To\0Beno\303\256t Th\303\251baudeau <benoit@wsystem.com>\0" "Cc\0rtc-linux@googlegroups.com" @@ -9,40 +9,27 @@ " Alessandro Zummo <a.zummo@towertech.it>\0" "\00:1\0" "b\0" - "On 21/07/2016 at 12:41:30 +0200, Beno=C3=AEt Th=C3=A9baudeau wrote :\n" - "> The I=C2=B2C NACK issue of the RV-8803 may occur after any I=C2=B2C START\n" + "On 21/07/2016 at 12:41:30 +0200, Beno\303\256t Th\303\251baudeau wrote :\n" + "> The I\302\262C NACK issue of the RV-8803 may occur after any I\302\262C START\n" "> condition, depending on the timings. Consequently, the workaround must\n" - "> be applied for all the I=C2=B2C transfers.\n" - ">=20\n" - "> This commit abstracts the I=C2=B2C transfer code into register access\n" - "> functions. This avoids duplicating the I=C2=B2C workaround everywhere. Th=\n" - "is\n" + "> be applied for all the I\302\262C transfers.\n" + "> \n" + "> This commit abstracts the I\302\262C transfer code into register access\n" + "> functions. This avoids duplicating the I\302\262C workaround everywhere. This\n" "> also avoids the duplication of the code handling the return value of\n" "> i2c_smbus_read_i2c_block_data(). Error messages are issued in case of\n" "> definitive register access failures (if the workaround fails). This\n" - "> change also makes the I=C2=B2C transfer return value checks consistent.\n" - ">=20\n" + "> change also makes the I\302\262C transfer return value checks consistent.\n" + "> \n" "\n" "Well, my initial idea was that the workaround is actually needed only\n" "for operations that are not restartable from userspace.\n" "\n" "Did you it that bug? On which RTC?\n" "\n" - "--=20\n" + "-- \n" "Alexandre Belloni, Free Electrons\n" "Embedded Linux and Kernel engineering\n" - "http://free-electrons.com\n" - "\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. + http://free-electrons.com -c854a243995c21e7158acc9bbb716a65cf58b17efe49f98d1cf02964a4bac7d7 +1b391a5b54aa237265df1c18ffa0acfb0a3c70bddd902f78022d26a16ce14519
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.