From: Hans de Goede <hdegoede@redhat.com>
To: John Garry <john.garry@huawei.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Darren Hart <dvhart@infradead.org>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3 4/4] i2c: Add multi-instantiate pseudo driver
Date: Wed, 8 Aug 2018 10:08:03 +0200 [thread overview]
Message-ID: <594d2c14-6f93-98cb-100d-9cc307d1cee4@redhat.com> (raw)
In-Reply-To: <7e68276c-2211-85d3-3e1f-2bc4b2d9f7d5@huawei.com>
Hi,
On 07-08-18 14:46, John Garry wrote:
> On 07/08/2018 09:05, Hans de Goede wrote:
>> 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().
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> MAINTAINERS | 6 +
>> drivers/platform/x86/Kconfig | 11 ++
>> drivers/platform/x86/Makefile | 1 +
>> drivers/platform/x86/i2c-multi-instantiate.c | 131 +++++++++++++++++++
>> 4 files changed, 149 insertions(+)
>> create mode 100644 drivers/platform/x86/i2c-multi-instantiate.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 9b377508f24f..09e16d76cab7 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -6657,6 +6657,12 @@ F: drivers/i2c/i2c-mux.c
>> F: drivers/i2c/muxes/
>> F: include/linux/i2c-mux.h
>>
>> +I2C MULTI INSTANTIATE DRIVER
>> +M: Hans de Goede <hdegoede@redhat.com>
>> +L: linux-i2c@vger.kernel.org
>> +S: Maintained
>> +F: drivers/drivers/platform/x86/i2c-multi-instantiate.c
>
> This path looks incorrect
>
>> +
>> I2C MV64XXX MARVELL AND ALLWINNER DRIVER
>> M: Gregory CLEMENT <gregory.clement@bootlin.com>
>> L: linux-i2c@vger.kernel.org
>> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
>> index 85a93453237c..8256629f58f7 100644
>> --- a/drivers/platform/x86/Kconfig
>> +++ b/drivers/platform/x86/Kconfig
>> @@ -1219,6 +1219,17 @@ config INTEL_CHTDC_TI_PWRBTN
>> To compile this driver as a module, choose M here: the module
>> will be called intel_chtdc_ti_pwrbtn.
>>
>> +config I2C_MULTI_INSTANTIATE
>> + tristate "I2C multi instantiate pseudo device driver"
>> + depends on I2C && ACPI
>> + help
>> + Some ACPI bases systems list multiple i2c-devices in a single ACPI
>
> I guess that this should be "Some ACPI-based systems"
Thanks, both fixed for v4 of the patchset.
Regards,
Hans
>
>> + firmware-node. This driver will instantiate separate i2c-clients
>> + for each device in the firmware-node.
>> +
>> + To compile this driver as a module, choose M here: the module
>> + will be called i2c-multi-instantiate.
>> +
>
> Thanks,
> John
>
prev parent reply other threads:[~2018-08-08 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 8:05 [PATCH v3 0/4] ACPI bugfix + i2c-multi-instantiate pseudo driver Hans de Goede
2018-08-07 8:05 ` [PATCH v3 1/4] ACPI / scan: Fix acpi_is_indirect_io_slave() always returning false Hans de Goede
2018-08-07 10:05 ` John Garry
2018-08-07 10:41 ` Hans de Goede
2018-08-07 8:05 ` [PATCH v3 2/4] ACPI / scan: Create platform device for fwnodes with multiple i2c devices Hans de Goede
2018-08-07 11:19 ` Andy Shevchenko
2018-08-07 11:29 ` Hans de Goede
2018-08-07 11:49 ` Andy Shevchenko
2018-08-08 8:07 ` Hans de Goede
2018-08-07 8:05 ` [PATCH v3 3/4] ACPI / x86-utils: Remove status workaround from acpi_device_always_present() Hans de Goede
2018-08-07 8:05 ` [PATCH v3 4/4] i2c: Add multi-instantiate pseudo driver Hans de Goede
2018-08-07 11:27 ` Wolfram Sang
2018-08-07 11:33 ` Hans de Goede
2018-08-07 11:45 ` Andy Shevchenko
2018-08-08 8:05 ` Hans de Goede
2018-08-07 12:46 ` John Garry
2018-08-08 8:08 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=594d2c14-6f93-98cb-100d-9cc307d1cee4@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox