lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 3 Apr 2014 11:25:34 +0000
From:	"Pallala, Ramakrishna" <>
To:	"" <>
CC:	"" <>,
	"" <>,
	"" <>
Subject: RE: How to pass I2C platform_data under ACPI

>> 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 }
	{ },

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists