[Question] RTC probe isn't called

[Question] RTC probe isn't called

[Kuninori Morimoto]

Dear all

Now I'm creating SuperH board code.
and I2C-RTC driver probe function isn't called in boot.

other I2C devices (I2C-camera) works well for me.
my I2C busses is i2c-sh_mobile.c
I would like to use r2025sd RTC which is attached
to I2C1 on my board.

What should I do ?
where should I check ?
Now I'm doing...

***************************
* on platform code
***************************

/* I2C device */
static struct i2c_board_info i2c1_devices[] = {
	{
		I2C_BOARD_INFO("r2025sd", 0x32),
	},
};
...

static int __init devices_setup(void)
{
        ...
	/* enable I2C1 device */
	i2c_register_board_info(1, i2c1_devices,
				ARRAY_SIZE(i2c1_devices));
	...
}
device_initcall(devices_setup);

************************
*  my .config
************************
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y

...
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
...

CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
...

CONFIG_RTC_DRV_RS5C372=y
...

*************************
I tried add debug printk
*************************
--- a/drivers/rtc/rtc-rs5c372.c
+++ b/drivers/rtc/rtc-rs5c372.c
@@ -721,6 +721,7 @@ static struct i2c_driver rs5c372_driver = {

 static __init int rs5c372_init(void)
 {
+	printk("***** rs5c372_init\n");
 	return i2c_add_driver(&rs5c372_driver);
 }

**********************
     the log is
**********************
....
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
***** rs5c372_init
i2c /dev entries driver
Linux video capture interface: v2.00
camera 0-0: SuperH Mobile CEU driver attached to camera 0
...
---------------------

Re: [Question] RTC probe isn't called

[Kuninori Morimoto]

Dear all

> Now I'm creating SuperH board code.
> and I2C-RTC driver probe function isn't called in boot.

Thank you
Now I could solve this problem.
The criminal was "device_initcall".
how stupid am I ...

Best regards
--
Kuninori Morimoto