diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-04-03 14:05:11 (GMT) |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-04-03 21:23:51 (GMT) |
commit | 16ba08d5c9ec44f89ec03c67ecf7a9c5e2d204fd (patch) | |
tree | 7a269ca24db329c53ada5e30fabc872d68c67164 /drivers/acpi | |
parent | 97badf873ab60e841243b66133ff9eff2a46ef29 (diff) | |
download | linux-16ba08d5c9ec44f89ec03c67ecf7a9c5e2d204fd.tar.xz |
device property: Introduce firmware node type for platform data
Introduce data structures and code allowing "built-in" properties
to be associated with devices in such a way that they will be used
by the device_property_* API if no proper firmware node (neither DT
nor ACPI) is present for the given device.
Each property is to be represented by a property_entry structure.
An array of property_entry structures (terminated with a null
entry) can be pointed to by the properties field of struct
property_set that can be added as a firmware node to a struct
device using device_add_property_set(). That will cause the
device_property_* API to use that property_set as the source
of properties if the given device does not have a DT node or
an ACPI companion device object associated with it.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/acpi')
0 files changed, 0 insertions, 0 deletions