On 05/23/2015 01:23 PM, Jonathan Cameron wrote:
On 19/05/15 18:53, Lars-Peter Clausen wrote:
On 05/08/2015 12:44 AM, Xander Huff wrote:
To better facilitate user-mode access to optional aux channels, allow
device trees to specify a custom extended name for defined channels.
Hi,
'extend-name' is kind of a IIO specific term. I think a better name in the devicetree context would be 'label'. That's used everywhere else when giving a short description string to a node.
Hi Lars,
What do you think of the general idea? I'm unconvinced we want to do this in channel naming.
Perhaps we want an additional attribute giving access to this sort of 'semantic' information?
I'm not convinced about it either. My gut feeling is that this is not the
right approach, but I don't really have any better ideas at the moment.
Xander can you give a short description of how this information will be used
by an application? Would having a label property for the channel also work
for you (e.g. in_voltage0_label)?
- Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
