linux-toradex.git/drivers/rtc/rtc-pcf85063.c, branch v4.10

rtc: pcf85063: do not register a RTC device if chip is not present

2016-11-04T22:08:59+00:00

Add a sanity check to see if chip is present. If we can not communicate
with the chip there is no point in registering a RTC device.

Signed-off-by: Mirza Krak 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: Add support for the PCF85063A device

2016-07-19T17:11:54+00:00

The current rtc-pcf85063 driver only supports the PCF85063TP device.
Using the existing driver on a PCF85063A will result in the time being
set correctly into the RTC, but the RTC is held in the stopped state.
Therefore, the time will no longer advance and no error is indicated.

The PCF85063A device has a bigger memory map than the PCF85063TP.
The existing driver make use of an address rollover condition,
but the rollover point is different in the two devices.

Signed-off-by: Chris DeBruin 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: fix year range

2016-07-19T17:11:12+00:00

The year range is not validated properly

As the driver has been mainlined in 2014, it is not an issue to stop
handling dates between 1970 and 2000 with the benefit of handling dates up
to 2100.

Signed-off-by: Alexandre Belloni

rtc: pcf85063: remove struct pcf85063

2016-03-14T16:08:30+00:00

No members of struct pcf85063 are used anymore, remove the whole structure.

Reviewed-by: Juergen Borleis 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: remove useless DRV_VERSION

2016-03-14T16:08:29+00:00

Since the driver is mainlined there is no use for a separate version
number.

Signed-off-by: Alexandre Belloni

rtc: pcf85063: remove useless century handling

2016-03-14T16:08:26+00:00

pcf85063_get_datetime() tries to handle a century bit but that bit is not
documented and the final value is never used anywhere else in the kernel.

Reviewed-by: Juergen Borleis 
Tested-by: Ulrich Ölmann 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: fix time/date setting

2016-03-14T16:08:17+00:00

When setting a new time/date the RTC's clock must be stopped first, in
order to write the time/date registers in an atomic manner.
So, this change stops the clock first and then writes the time/date
registers and the clock control register (to re-enable the clock) in one
turn.

Signed-off-by: Juergen Borleis 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: fix time/date reading

2016-03-14T16:08:17+00:00

Check if the RTC signals an invalid time/date (due to a battery power loss
for example). In this case ignore the time/date until it is really set again.

Signed-off-by: Juergen Borleis 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: simplify code to read the current time

2016-03-14T16:08:17+00:00

By using i2c_smbus_read_i2c_block_data() the code is now much simpler.

While at it: when reading the RTC's seconds register, all time/date registers
are frozen until the RTC's year register is read. So it is important to read
all time/date registers in one turn to not lose a second event. Make it more
clear why the read must happen in this way.

Signed-off-by: Juergen Borleis 
Signed-off-by: Alexandre Belloni

rtc: pcf85063: return an error when date is invalid

2015-11-08T13:12:26+00:00

Return an error when the date is invalid as the policy should be
implemented there.

Signed-off-by: Alexandre Belloni