linux/drivers/fsi
Joel Stanley 496f8931b6 fsi: core: register with postcore_initcall
When testing an i2c driver that is a fsi bus driver, I saw the following
oops:

 kernel BUG at drivers/base/driver.c:153!
 Internal error: Oops - BUG: 0 [#1] ARM

 [<8027cb1c>] (driver_register) from [<80344e88>] (fsi_driver_register+0x2c/0x38)
 [<80344e88>] (fsi_driver_register) from [<805f5ebc>] (fsi_i2c_driver_init+0x1c/0x24)
 [<805f5ebc>] (fsi_i2c_driver_init) from [<805d1f14>] (do_one_initcall+0xb4/0x170)
 [<805d1f14>] (do_one_initcall) from [<805d20f0>] (kernel_init_freeable+0x120/0x1dc)
 [<805d20f0>] (kernel_init_freeable) from [<8043f4a8>] (kernel_init+0x18/0x104)
 [<8043f4a8>] (kernel_init) from [<8000a5e8>] (ret_from_fork+0x14/0x2c)

This is because the fsi bus had not been registered. This fix registers the bus
with postcore_initcall instead, to ensure it is registered earlier on.

When the fsi core is used as a module this should not be a problem as the fsi
driver will depend on the fsi bus type symbol, and will therefore load the core
before the driver.

Fixes: 0508ad1fff ("drivers/fsi: Add empty fsi bus definitions")
Signed-off-by: Joel Stanley <joel@jms.id.au>
Acked-by: Jeremy Kerr <jk@ozlabs.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-07-17 16:13:54 +02:00
..
fsi-core.c fsi: core: register with postcore_initcall 2017-07-17 16:13:54 +02:00
fsi-master-gpio.c drivers/fsi: Use asynchronous slave mode 2017-06-09 11:52:09 +02:00
fsi-master-hub.c drivers/fsi: Add hub master support 2017-06-09 11:52:09 +02:00
fsi-master.h drivers/fsi: Use asynchronous slave mode 2017-06-09 11:52:09 +02:00
fsi-scom.c drivers/fsi: Add SCOM FSI client device driver 2017-06-09 11:52:09 +02:00
Kconfig drivers/fsi: Add hub master support 2017-06-09 11:52:09 +02:00
Makefile drivers/fsi: Add hub master support 2017-06-09 11:52:09 +02:00