From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
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>,
John Garry <john.garry@huawei.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3 2/4] ACPI / scan: Create platform device for fwnodes with multiple i2c devices
Date: Tue, 7 Aug 2018 13:29:33 +0200 [thread overview]
Message-ID: <13770931-2322-96a3-1667-83c96b25bcfb@redhat.com> (raw)
In-Reply-To: <00e16cb09c171b536449b61124473291f2b30d0b.camel@linux.intel.com>
Hi,
On 07-08-18 13:19, Andy Shevchenko wrote:
> On Tue, 2018-08-07 at 10:05 +0200, Hans de Goede wrote:
>> Some devices have multiple I2cSerialBus resources and for things to
>> work
>> an i2c-client must be instantiated for each, each with its own
>> i2c_device_id.
>>
>> Normally we only instantiate an i2c-client for the first resource,
>> using
>> the ACPI HID as id.
>>
>> This commit adds a list of HIDs of devices, which need multiple i2c-
>> clients
>> instantiated from a single fwnode, to
>> acpi_device_enumeration_by_parent and
>> makes acpi_device_enumeration_by_parent return false for these devices
>> so
>> that a platform device will be instantiated.
>>
>> This allows the drivers/platform/x86/i2c-multi-instantiate.c driver,
>> which
>> knows which i2c_device_id to use for each resource, to bind to the
>> fwnode
>> and initiate an i2c-client for each resource.
>>
>
>> + /*
>> + * These devices have multiple I2cSerialBus resources and an
>> i2c-client
>> + * must be instantiated for each, each with its own
>> i2c_device_id.
>> + * Normally we only instantiate an i2c-client for the first
>> resource,
>> + * using the ACPI HID as id. These special cases are handled by
>> the
>> + * drivers/platform/x86/i2c-multi-instantiate.c driver, which
>> knows
>> + * which i2c_device_id to use for each resource.
>> + */
>> + static const struct acpi_device_id i2c_multi_instantiate_ids[] =
>> {
>> + {"BSG1160", 0},
>> + {"", 0},
>> + };
>
> Style nits:
> - can we move it outside of function?
Sure, but there are 2 existing users of an array of acpi_device_id-s
combined with an acpi_match_device_ids() call and both have the array
inside the function, so for consistency it seems better to keep it
where it is.
> - terminator better without comma
Agreed, will fix for v4.
> - is this existing style in the file and / or files in this folder for
> IDs? (I mean unnecessary 0:s and empty string?
It seems that all variants one can come up with are already used inside
this single file.
I agree that less is more, so I will change this to:
static const struct acpi_device_id i2c_multi_instantiate_ids[] = {
{"BSG1160", },
{}
};
For v4.
Regards,
Hans
next prev parent reply other threads:[~2018-08-07 11:29 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 [this message]
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
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=13770931-2322-96a3-1667-83c96b25bcfb@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;
as well as URLs for NNTP newsgroup(s).