linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Isak Lichtenstein <Isak.Lichtenstein@kistler.com>,
	"'linux-iio@vger.kernel.org'" <linux-iio@vger.kernel.org>,
	Zubair Lutfullah <zubair.lutfullah@gmail.com>
Subject: Re: TI-am335x-adc
Date: Sat, 28 Mar 2015 13:50:05 +0000	[thread overview]
Message-ID: <5516B18D.1070605@kernel.org> (raw)
In-Reply-To: <91B4C1B91AAEFD42AC985EA0F3D4E668012B0BCFD1@kihagwinex01.int.kistler.com>

On 17/03/15 10:40, Isak Lichtenstein wrote:
> 
> Hi everybody,
> 
> I've started using the TI-am335x-adc driver in continuous mode on our custom board with AM3359 and yocto-linux-standard 3.17 and get a weird behavior when testing it using generic_buffer.c
> 
> Every now and then channel 0 seems to contain the value of channel 1, see the attached output of the following command: ./genericBuffer -n TI-am335x-adc -l 128 -c 100 ( I've added tabs to make it more readable).
> 
> 
> Is this a driver bug ( maybe already patched after 3.17 ), or is my board not properly configured?
> 
> I'm not using the TSC and my device tree is configured as follows:
> 
> #include "am33xx.dtsi"
> 
> &tscadc {
>             status = "okay";
>             /*
>             tsc {
>                         ti,wires = <4>;
>                         ti,x-plate-resistance = <200>;
>                         ti,coordinate-readouts = <5>;
>                         ti,wire-config = <0x00 0x11 0x22 0x33>;
>             };
>             */
> 
>             adc {
>                         ti,adc-channels = <0 1 2 3 4 5 6 7>;
>             };
> };
> 
> 
> Thanks in advance for your advice.
> 
> Best regards
> 
> Isak Lichtenstein
> 
Zubair, any thought on this?
(or anyone else for that matter!)



      reply	other threads:[~2015-03-28 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <91B4C1B91AAEFD42AC985EA0F3D4E668010B98E15D@kihagwinex01.int.kistler.com>
2015-03-17 10:40 ` TI-am335x-adc Isak Lichtenstein
2015-03-28 13:50   ` Jonathan Cameron [this message]

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=5516B18D.1070605@kernel.org \
    --to=jic23@kernel.org \
    --cc=Isak.Lichtenstein@kistler.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=zubair.lutfullah@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).