summaryrefslogtreecommitdiff
path: root/drivers/net/can/peak_canfd
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@armlinux.org.uk>2017-09-24 11:32:52 +0100
committerRussell King (Oracle) <rmk+kernel@armlinux.org.uk>2025-04-04 15:20:00 +0100
commitcd8d54831870500bbbfe8436e59cee5ec4765a8b (patch)
tree41d23525eca4d6db51c9bb97114715155e25f542 /drivers/net/can/peak_canfd
parent8f71d18db68bc53cef19ca5ecc9f2cd6671a8b8b (diff)
rtc: pcf8523: provide set_offset_nsec
When we set the time, we set the STOP bit, set the time, and then clear the STOP bit. Concerning the timing, the PCF8523 data sheet says: "The first increment of the time circuits is between 0.499878s and 0.500000s after STOP is released." However, practical measurement shows this is not the case - with the I2C bus speed at 100kHz on iMX6, it takes about 5ms for the rtclib call for setting the time to complete. However, reading back when the second actually flips shows that there's an additional 10ms which can't be accounted for by the read - a read of the RTC takes 1.7 to 1.8 ms. Practical measurement shows that the first increment occurs about 515ms after the write, which means we need to set the current second 485ms after it has started. Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Diffstat (limited to 'drivers/net/can/peak_canfd')
0 files changed, 0 insertions, 0 deletions