Re: [PATCH 1/6] mfd: viperboard: fix platform-device id collision

2014-10-07 Thread Lee Jones
On Fri, 26 Sep 2014, Johan Hovold wrote: > Allow more than one viperboard to be connected by registering with > PLATFORM_DEVID_AUTO instead of PLATFORM_DEVID_NONE. > > The subdevices are currently registered with PLATFORM_DEVID_NONE, which > will cause a name collision on the platform bus when a

Re: [PATCH 1/6] mfd: viperboard: fix platform-device id collision

2014-10-07 Thread Lee Jones
On Fri, 26 Sep 2014, Johan Hovold wrote: Allow more than one viperboard to be connected by registering with PLATFORM_DEVID_AUTO instead of PLATFORM_DEVID_NONE. The subdevices are currently registered with PLATFORM_DEVID_NONE, which will cause a name collision on the platform bus when a

[PATCH 1/6] mfd: viperboard: fix platform-device id collision

2014-09-26 Thread Johan Hovold
Allow more than one viperboard to be connected by registering with PLATFORM_DEVID_AUTO instead of PLATFORM_DEVID_NONE. The subdevices are currently registered with PLATFORM_DEVID_NONE, which will cause a name collision on the platform bus when a second viperboard is plugged in: viperboard

[PATCH 1/6] mfd: viperboard: fix platform-device id collision

2014-09-26 Thread Johan Hovold
Allow more than one viperboard to be connected by registering with PLATFORM_DEVID_AUTO instead of PLATFORM_DEVID_NONE. The subdevices are currently registered with PLATFORM_DEVID_NONE, which will cause a name collision on the platform bus when a second viperboard is plugged in: viperboard