Additionally I'm curious if this could somehow be modified to make the
changes for the uio adc deceive. I do not understand device tree files all
that well. Well, more correctly I get the addresses, etc for the various
hardware modules, but I do not understand a lot of the device tree specific
keywords( I guess they are ). So as an example fragment@0{...} All inside
that set of brackets I do not "get". Although I do understand the
adc-channels<. . .> part well enough I suppose. That just enabling channels
0-6, and channel 8(0x7) is setup as a touchscreen channel.
__fixups__ {
tscadc = "/fragment@0:target:0";
};
NO idea what this does . . . Anyway, below is just the basic BBB-ADC
overlay provided from the bb.org-overlay git. Atleast, I do not think I've
modified it any . . .
/dts-v1/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black",
"ti,beaglebone-green";
part-number = "BB-ADC";
version = "00A0";
exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33", "P9.36",
"P9.35", "tscadc";
fragment@0 {
target = <0xdeadbeef>;
__overlay__ {
status = "okay";
adc {
ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6>;
};
};
};
__fixups__ {
tscadc = "/fragment@0:target:0";
};
};
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
