On 26/07/16 20:07, Rob Herring wrote: > On Sun, Jul 24, 2016 at 12:17:14PM +0200, Linus Walleij wrote: >> The mounting matrix for sensors was introduced in >> commit dfc57732ad38 ("iio:core: mounting matrix support") >> >> However the device tree bindings are very terse and since this is >> a widely applicable property, we need a proper binding for it >> that the other bindings can reference. This will also be useful >> for other operating systems and sensor engineering at large. >> >> I think all 3D sensors should support it, the current situation >> is probably that the mounting information is confined in magic >> userspace components rather than using the mounting matrix, which >> is not good for portability and reuse. >> >> Cc: Gregor Boirie <gregor.boirie@xxxxxxxxxx> >> Cc: Sebastian Reichel <sre@xxxxxxxxxx> >> Cc: Samu Onkalo <samu.onkalo@xxxxxxxxx> >> Cc: devicetree@xxxxxxxxxxxxxxx >> Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> >> --- >> Please help out to get this right, I think this could be confusing >> to users unless documented properly. I think the doc has some rough >> edges since I'm not the smartest in physics nor english at all times. >> --- > > I can at least say I understand how it's supposed to work better now. > > Acked-by: Rob Herring <robh@xxxxxxxxxx> > > On the duplication topic, of course I agree that sysfs docs should refer > to DT and not vice-versa. I'd be tempted to keep a 'full' documentation of all the relevant aspects in each place, but make sure there is a cross reference from the sysfs ABI docs to the device tree ones as has been suggested. (rather than converting the sysfs docs just a cross reference + note on how the bindings and attribute are related). > > Rob > -- > 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 > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html