summaryrefslogtreecommitdiffstats
path: root/drivers/nvme
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2018-08-09 13:40:46 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-08-09 13:58:21 +0200
commite64e84987de5486839afaccd191df71012ac1800 (patch)
tree9b7084df64757285e1d5c2ad6fb7180a4513ab74 /drivers/nvme
parentACPI / x86: utils: Remove status workaround from acpi_device_always_present() (diff)
downloadlinux-e64e84987de5486839afaccd191df71012ac1800.tar.xz
linux-e64e84987de5486839afaccd191df71012ac1800.zip
platform/x86: Add ACPI i2c-multi-instantiate pseudo driver
On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1 i2c-device. But in some rare cases the manufacturer has decided to describe multiple i2c-devices in a single ACPI fwnode with multiple I2cSerialBus resources. An earlier attempt to fix this in the i2c-core resulted in a lot of extra code to support this corner-case. This commit introduces a new i2c-multi-instantiate driver which fixes this in a different way. This new driver can be built as a module which will only loaded on affected systems. This driver will instantiate a new i2c-client per I2cSerialBus resource, using the driver_data from the acpi_device_id it is binding to to tell it which chip-type (and optional irq-resource) to use when instantiating. Note this driver depends on a platform device being instantiated for the ACPI fwnode, see the i2c_multi_instantiate_ids list of ACPI device-ids in drivers/acpi/scan.c: acpi_device_enumeration_by_parent(). Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Acked-by: Wolfram Sang <wsa@the-dreams.de> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/nvme')
0 files changed, 0 insertions, 0 deletions