On Tue, Oct 25, 2016 at 11:34:40AM +0200, Linus Walleij wrote: > Good work on this patch, nice that it got merged. > > I was just thinking that as an add-on, you may want to name > the gpio lines so they have meaningful names in userspace > when you use this with the chardev (I have reasons to believe > these GPIOs will be used from userspace, tell me if that > is wrong). > Yeah, they are. > We currently support naming lines for devicetree and > ACPI (in -next). > I'm not sure this would be a good fit for the current use case I've been working on, as I understand there might be an arbitary number of devices plugged in. The same chip may also get used in more than one way (in the current use case, the Vendor/Product IDs actually get get to determine the use case. Originally I did name the GPIO as either SCI or ECI, in the case of the CP2105, being able to distinguish between the two banks can be helpful during debug (but isn't essential and didn't actually seem to help when trying to programatically parse though the available banks of GPIO in user space to find the ones that were interesting). However this doesn't translate so well to the other chips in the CP210x family as the GPIO is implemented differently for the majority of those (they don't mux pins from the serial ports). I have seen such chips actually used inside of units, so being able to name the GPIO would be quite useful there, though that naming would need to only be applied to specific devices and not to other devices plugged in externally. Martyn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
