Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name

2015-08-24 Thread Dustin Byford
On Mon Aug 17 11:00, Jarkko Nikula wrote: > If I remember correctly ACPI ID should not ever change and instance id :xy > after INTABCD:xy should also be visible and keep the order even if device is > disabled or not plugged. But I'm not absolute sure about this. > > At least on a test platform th

Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name

2015-08-17 Thread Jarkko Nikula
On 15.08.2015 18:13, Guenter Roeck wrote: On Fri, Aug 14, 2015 at 12:37:13PM -0700, Dustin Byford wrote: 70762ab from 11/2014 (i2c: Use stable dev_name for ACPI enumerated I2C slaves) modified the sysfs-visible dev_name() for ACPI enumerated I2C devices. With that change, /sys/bus/i2c/devices/i

Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name

2015-08-15 Thread Guenter Roeck
On Fri, Aug 14, 2015 at 12:37:13PM -0700, Dustin Byford wrote: > 70762ab from 11/2014 (i2c: Use stable dev_name for ACPI enumerated I2C > slaves) modified the sysfs-visible dev_name() for ACPI enumerated I2C > devices. With that change, /sys/bus/i2c/devices/i2c-0-004a, for > example, became /sys/b

[RFC 0/1] i2c: acpi: revert setting a "stable" device name

2015-08-14 Thread Dustin Byford
70762ab from 11/2014 (i2c: Use stable dev_name for ACPI enumerated I2C slaves) modified the sysfs-visible dev_name() for ACPI enumerated I2C devices. With that change, /sys/bus/i2c/devices/i2c-0-004a, for example, became /sys/bus/i2c/devices/i2c-PNP:xx That causes problems for userspace code