Hey!
/* Addresses to scan: none
* This chip cannot be reliably autodetected. An empty eeprom
* located at 0x51 will pass the validation routine due to
* the way the registers are implemented.
*/
static unsigned short normal_i2c[] = { I2C_CLIENT_END };
This explains all...
And, in http://projects.qi-hardware.com/index.php/p/qi-kernel/source/tree/master/drivers/rtc/rtc-pcf8563.c
(version 0.4.3) all calls to attach() have been removed.
Here is a workaround:
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=65576
static int pcf8563_attach(struct i2c_adapter *adapter)
{
//return i2c_probe(adapter, &addr_data, pcf8563_probe);
// OVERRIDE probing
return pcf8563_probe(adapter, 0x51, 0);
}
With this patch, I now get a /dev/rtc0 as expected and the hctosys
error in dmesg has disappeared!
I just have a read error when trying to access the clock. This may
indeed be an I2C communication error (since i2cdetect also fails).
Nikolaus
Am 04.05.2010 um 13:34 schrieb Dr. H. Nikolaus Schaller:
I have now traced down things a little more.
i2c-core.c/i2c_register_driver() is called
rtc-pcf8563.c/pcf8563_attach() is called
i2c-core.c/i2c-probe() is called
i2c-core.c/i2c_probe_address() is NOT called
therefore,
rtc-pcf8563.c/pcf8563_proble() is NOT called
rtc_device_register() is NOT called
So it looks to me as if the PCF is not configured correctly - or
some of the config macros don't do what the are expected to do...
Nikolaus
_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
