From: "Vijay S" <vijay-EvXpCiN+lbve9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
To: 'Anil Kumar' <anilk4.v-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: RE: Reg:Trying to get the ADC working on the Beaglebone with 3.8 kernel
Date: Tue, 12 Feb 2013 19:37:15 +0530 [thread overview]
Message-ID: <001501ce092a$453264d0$ad0fa8c0@mistral.in> (raw)
In-Reply-To: <CABYxbz4tnBM2v_QHKANV1bBCEWpyi_oS1DZA5X=2WdJjUFNATw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Anil,
Thanks for the reply. The pins AIN0 to AIN7 are signals right? Do they have
pin mux? I'm sorry if this question is very vague.
Regards,
Vijay
-----Original Message-----
From: Anil Kumar [mailto:anilk4.v-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Tuesday, February 12, 2013 7:10 PM
To: Vijay S
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Reg:Trying to get the ADC working on the Beaglebone with 3.8
kernel
Hi Vijay,
On Tue, Feb 12, 2013 at 6:49 PM, Vijay S <vijay-EvXpCiN+lbve9wHmmfpqLFaTQe2KTcn/@public.gmane.org> wrote:
> 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@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>;
>
> };
>
have you done pin mux for this ?
>
>
>
>
> 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
>
>
>
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
next prev parent reply other threads:[~2013-02-12 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 13:19 Reg:Trying to get the ADC working on the Beaglebone with 3.8 kernel Vijay S
[not found] ` <000001ce0923$9d97f510$ad0fa8c0-HrUwqZBnLO6f0DUV/oxz1A@public.gmane.org>
2013-02-12 13:39 ` Anil Kumar
[not found] ` <CABYxbz4tnBM2v_QHKANV1bBCEWpyi_oS1DZA5X=2WdJjUFNATw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-12 14:07 ` Vijay S [this message]
[not found] ` <001501ce092a$453264d0$ad0fa8c0-HrUwqZBnLO6f0DUV/oxz1A@public.gmane.org>
2013-02-12 14:50 ` Anil Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001501ce092a$453264d0$ad0fa8c0@mistral.in' \
--to=vijay-evxpcin+lbve9whmmfpqlfatqe2ktcn/@public.gmane.org \
--cc=anilk4.v-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox