To support this multiple device thingy and avoid the single device limit, I plan to do something like this,
The ST driver would be platform_device - as it is already. ST's probe would do the ldisc registration, and also do the dev_set_drvdata of all the internal data (Tx queues, locks, list of protocols) on this device.
Apart from this the BT, FM and GPS would also further be platform devices, and then,
In the dev.platform_data of each of these BT, FM and GPS devices, I will enter the "parent ST device", these protocols want to attach themselves to.
And in probe of the driver for each of these BT, FM and GPS devices, I will do the same "st_register" where in now I can access the ST related data by retrieving the internal using the parent device.
Examples:
Here are the 2 ST platform devices,
struct platform_device st_device_0 = {
.name = "ST_DEV_0",
.id = -1,
.dev.platform_data = &array,
.dev.release = any_device_release,
};
struct platform_device st_device_1 = {
.name = "ST_DEV_1",
.id = -1,
.dev.platform_data = &array,
.dev.release = any_device_release,
};
BT attaching itself to ST_DEV_0,
static struct protocol_platform_data bt_data = {
.parent_dev = &st_device_0,
.name = "BT",
};
static struct platform_device bt_device = {
.name = "BT",
.id = -1,
.dev.platform_data = &bt_data,
.dev.release = bt_device_release,
};
And FM attaching itself to - ST_DEV_1,
static struct protocol_platform_data fm_data = {
.parent_dev = &st_device_1,
.name = "FM",
};
static struct platform_device fm_device = {
.name = "FM",
.id = -1,
.dev.platform_data = &fm_data,
.dev.release = fm_device_release,
};
My "ST_REGISTER" would now look like,
int st_register(struct protocol_platform_data *data)
{
struct st_data_s *st_data;
struct platform_device *parent = data->parent_dev;
st_data = ...
