Reg:Trying to get the ADC working on the Beaglebone with 3.8 kernel
Vijay S
vijay at mistralsolutions.com
Wed Feb 13 00:19:19 EST 2013
Hi,
Am trying to get the ADC working on the beagle bone. Have cloned/pulled the
latest kernel from the following branch
https://github.com/beagleboard/kernel/tree/3.8 , applied the patches and
built the kernel.
Have included the below structure under the am335x-bone-common.dtsi
(attached herewith is the dts file for your reference)
tscadc at 44e0d000 {
status = "okay";
compatible = "ti,ti-tscadc";
reg = <0x44e0d000 0x1000>;
interrupt-parent = <&intc>;
interrupts = <16>;
ti,hwmods = "adc_tsc";
};
&tscadc {
tsc {
ti,wires = <4>;
ti,x-plate-resistance = <200>;
ti,steps-to-configure = <5>;
ti,wire-config = <0x00 0x11 0x22 0x33>;
};
adc {
ti,adc-channels = <8>;
};
The device is getting registered( [1.578678] input: ti-tsc as
/devices/ocp.2/44e0d000.tscadc/tsc/input/input0
[ 1.586799] tsc tsc: Initialized OK) as can be seen from the attached
kernel log(3.8_kernel_ts_adc_sys_iio_devices.txt).
Am able to view the "tiadc" under the devices in the following path cat
/sys/devices/ocp.2/44e0d000.tscadc/tiadc/iio\:device0/ and cat
/sys/bus/iio/devices/iio\:device0/ , but am not able to list out
"in_voltageX_raw" in either of the paths.
Can you please suggest if am missing anything?
Regards,
Vijay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/devicetree-discuss/attachments/20130212/6498b3ec/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 3.8_kernel_ts_adc_sys_iio_device.txt
URL: <http://lists.ozlabs.org/pipermail/devicetree-discuss/attachments/20130212/6498b3ec/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: am335x-bone-common.dtsi
Type: application/octet-stream
Size: 8240 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/devicetree-discuss/attachments/20130212/6498b3ec/attachment-0001.obj>
More information about the devicetree-discuss
mailing list