Messages in this thread | | | Date | Thu, 26 Oct 2017 22:29:27 +0200 | From | Wolfram Sang <> | Subject | Re: [PATCH resend v5 1/3] i2c: Allow overriding dev_name through board_info |
| |
On Wed, Oct 11, 2017 at 11:41:19AM +0200, Hans de Goede wrote: > For devices not instantiated through ACPI the i2c-client's device-name > gets set to <busnr>-<addr> by default, e.g. "0-0022" this means that > the device-name is dependent on the order in which the i2c-busses are > enumerated. > > In some cases having a predictable constant device-name is desirable, > for example on non device-tree platforms the link between a regulator > and its consumers is specified by the platform code by setting > regulator_init_data.consumers. This array identifies the regulator's > consumers by dev_name and supply(-name). Which requires a constant > dev_name. > > This commit adds a dev_name field to i2c_board_info allowing > platform code to set a contstant dev_name so that the device can > be identified by its dev_name in other platform code. > > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
So, the live discussion at ELCE17 between broonie, Andy, and me came to a good end for you ;)
Applied to for-next, thanks!
[unhandled content-type:application/pgp-signature] | |