Hi All,
I am trying to enable a i2c client driver under ACPI. The device is being enumerated behind adapter device and I am getting IRQ resource as well.
The problem I have now is, how do I pass the platform data to driver?
struct i2c_board_info { char type[I2C_NAME_SIZE]; unsigned short flags; unsigned short addr; void *platform_data; ===========> how can I initialize this filed. struct dev_archdata *archdata; struct device_node *of_node; struct acpi_dev_node acpi_node; int irq; };
In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
Thanks, Ram
On Thu, Apr 03, 2014 at 08:10:40AM +0000, Pallala, Ramakrishna wrote:
Hi All,
I am trying to enable a i2c client driver under ACPI. The device is being enumerated behind adapter device and I am getting IRQ resource as well.
The problem I have now is, how do I pass the platform data to driver?
struct i2c_board_info { char type[I2C_NAME_SIZE]; unsigned short flags; unsigned short addr; void *platform_data; ===========> how can I initialize this filed. struct dev_archdata *archdata; struct device_node *of_node; struct acpi_dev_node acpi_node; int irq; }; In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
If you can't extract that information from ACPI namespace, then one option is to pass platform data along with the device ACPI ID:
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data } ... { }, };
static struct i2c_driver i2c_hid_driver = { .driver = { ... .acpi_match_table = ACPI_PTR(my_acpi_match), }, ...
In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
If you can't extract that information from ACPI namespace, then one option is to pass platform data along with the device ACPI ID:
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data } ... { }, };
Thanks for the Quick reply.
So If I want to use different platform_data for different boards can I do something like below? And initialize the platform data in either driver or in separate module which gets compiled along with driver?
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data1 } { "MYID0002", (kernel_ulong_t)&my_platform_data2 } ... { },
Thanks, Ram
On Thu, Apr 03, 2014 at 11:25:34AM +0000, Pallala, Ramakrishna wrote:
In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
If you can't extract that information from ACPI namespace, then one option is to pass platform data along with the device ACPI ID:
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data } ... { }, };
Thanks for the Quick reply.
So If I want to use different platform_data for different boards can I do something like below?
Exactly.
And initialize the platform data in either driver or in separate module which gets compiled along with driver?
Typically it has been done in the same driver but I don't see any problems having a separate module as well.
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data1 } { "MYID0002", (kernel_ulong_t)&my_platform_data2 } ... { },
Thanks, Ram
On Thursday 03 April 2014 14:38:33 mika.westerberg@linux.intel.com wrote:
On Thu, Apr 03, 2014 at 11:25:34AM +0000, Pallala, Ramakrishna wrote:
In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
If you can't extract that information from ACPI namespace, then one option is to pass platform data along with the device ACPI ID:
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data } ... { }, };
Thanks for the Quick reply.
So If I want to use different platform_data for different boards can I do something like below?
Exactly.
And initialize the platform data in either driver or in separate module which gets compiled along with driver?
Typically it has been done in the same driver but I don't see any problems having a separate module as well.
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data1 } { "MYID0002", (kernel_ulong_t)&my_platform_data2 } ... { },
We definitely don't want per-board match entries, that does not scale. The driver should be reasonably generic and get all the necessary data out of well-defined tables. You can have different IDs when there are only a few cases that are actually relevant, but it has to be conceivable that the same driver get used on future hardware without changes.
Arnd
On Thu, Apr 03, 2014 at 03:34:30PM +0200, Arnd Bergmann wrote:
On Thursday 03 April 2014 14:38:33 mika.westerberg@linux.intel.com wrote:
On Thu, Apr 03, 2014 at 11:25:34AM +0000, Pallala, Ramakrishna wrote:
In non ACPI environment I used to initialize the platform_data under board or platforms files. Under ACPI how do I do that?
If you can't extract that information from ACPI namespace, then one option is to pass platform data along with the device ACPI ID:
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data } ... { }, };
Thanks for the Quick reply.
So If I want to use different platform_data for different boards can I do something like below?
Exactly.
And initialize the platform data in either driver or in separate module which gets compiled along with driver?
Typically it has been done in the same driver but I don't see any problems having a separate module as well.
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data1 } { "MYID0002", (kernel_ulong_t)&my_platform_data2 } ... { },
We definitely don't want per-board match entries, that does not scale. The driver should be reasonably generic and get all the necessary data out of well-defined tables. You can have different IDs when there are only a few cases that are actually relevant, but it has to be conceivable that the same driver get used on future hardware without changes.
Yes, I meant that when the platform data information is not available in ACPI namespace, then (and only then) pass the data by means of different IDs.
Preferably this information is included in the ACPI namespace.
And initialize the platform data in either driver or in separate module which gets compiled along with driver?
Typically it has been done in the same driver but I don't see any problems having a separate module as well.
static const struct acpi_device_id my_acpi_match[] = { { "MYID0001", (kernel_ulong_t)&my_platform_data1 } { "MYID0002", (kernel_ulong_t)&my_platform_data2 } ... { },
We definitely don't want per-board match entries, that does not scale. The driver should be reasonably generic and get all the necessary data out of well-defined tables. You can have different IDs when there are only a few cases that are actually relevant, but it has to be conceivable that the same driver get used on future hardware without changes.
Yes, I meant that when the platform data information is not available in ACPI namespace, then (and only then) pass the data by means of different IDs.
Preferably this information is included in the ACPI namespace.
The idea is use the single platform_data struct and initiaze it accordingly from the driver's __init call based on the board/platform.
Thanks for your inputs. Ram.
On Thursday 03 April 2014 13:59:18 Pallala, Ramakrishna wrote:
We definitely don't want per-board match entries, that does not scale. The driver should be reasonably generic and get all the necessary data out of well-defined tables. You can have different IDs when there are only a few cases that are actually relevant, but it has to be conceivable that the same driver get used on future hardware without changes.
Yes, I meant that when the platform data information is not available in ACPI namespace, then (and only then) pass the data by means of different IDs.
Preferably this information is included in the ACPI namespace.
The idea is use the single platform_data struct and initiaze it accordingly from the driver's __init call based on the board/platform.
In general, you should think of it as being isolated from the board or platform question, and not rely on an an initcall to do this for you. A device driver, in particular for a device on something like an i2c bus, should be able to figure out all the dependencies in its own probe() function, without code on the platform side or in a specific driver initcall.
What information it needs of course depends on the specific device, but if you boot using FDT or ACPI, all the information you need should be encoded in the data passed from the boot loader in a generic and documented fashion. What data specifically do you want to pass here that was previously encoded in platform data?
Arnd
-
Arnd Bergmann -
mika.westerberg＠linux.intel.com -
Pallala, Ramakrishna