If snvs_rtc_enable() happens to be descheduled for a period longer
than the timout period, a timeout may be indicated even if the RTC
status has changed meanwhile. Force a status read at the end of the
timeout period to prevent bogus timeout errors.
Signed-off-by: Lothar Wa?mann <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)
Compile tested only due to lack of HW.
On Sat, Aug 18, 2012 at 10:10:08AM +0200, Lothar Wa?mann wrote:
If snvs_rtc_enable() happens to be descheduled for a period longer
than the timout period, a timeout may be indicated even if the RTC
status has changed meanwhile. Force a status read at the end of the
timeout period to prevent bogus timeout errors.
Signed-off-by: Lothar Wa?mann <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)
Compile tested only due to lack of HW.
Tested-by: Shawn Guo <redacted>
A small nitpick below.
On Sat, Aug 18, 2012 at 10:10:08AM +0200, Lothar Wa?mann wrote:
quoted
If snvs_rtc_enable() happens to be descheduled for a period longer
than the timout period, a timeout may be indicated even if the RTC
status has changed meanwhile. Force a status read at the end of the
timeout period to prevent bogus timeout errors.
Signed-off-by: Lothar Wa?mann <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)
Compile tested only due to lack of HW.
Tested-by: Shawn Guo <redacted>
A small nitpick below.
Can we rename parameter "addr" to "ioaddr" and put it before "enable",
also change "enable" to bool?
OK. The resulting assembler code of the patch below is identical to
the previous version of this patch.
Signed-off-by: Lothar Wa?mann <redacted>
Tested-by: Shawn Guo <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)
On Sat, 18 Aug 2012 10:10:08 +0200
Lothar Wa__mann [off-list ref] wrote:
If snvs_rtc_enable() happens to be descheduled for a period longer
than the timout period, a timeout may be indicated even if the RTC
status has changed meanwhile. Force a status read at the end of the
timeout period to prevent bogus timeout errors.
Hi Shawn, Lothar,
On 18/08/2012 at 15:14:04 +0200, Lothar Wa?mann wrote :
Shawn Guo writes:
quoted
On Sat, Aug 18, 2012 at 10:10:08AM +0200, Lothar Wa?mann wrote:
quoted
If snvs_rtc_enable() happens to be descheduled for a period longer
than the timout period, a timeout may be indicated even if the RTC
status has changed meanwhile. Force a status read at the end of the
timeout period to prevent bogus timeout errors.
Signed-off-by: Lothar Wa?mann <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)
Compile tested only due to lack of HW.
Tested-by: Shawn Guo <redacted>
It seems that patch never made it mainline. Can you check if it is still
needed?
Can we rename parameter "addr" to "ioaddr" and put it before "enable",
also change "enable" to bool?
OK. The resulting assembler code of the patch below is identical to
the previous version of this patch.
Signed-off-by: Lothar Wa?mann <redacted>
Tested-by: Shawn Guo <redacted>
---
drivers/rtc/rtc-snvs.c | 22 +++++++++++++---------
1 files changed, 13 insertions(+), 9 deletions(-)