public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Michael Welling <mwelling@ieee.org>, "Cooper Jr.,
	Franklin" <fcooper@ti.com>
Cc: "Griffis, Brad" <bgriffis@ti.com>, "Balbi, Felipe" <balbi@ti.com>,
	"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"wsa@the-dreams.de" <wsa@the-dreams.de>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"GWilson@sakuraus.com" <GWilson@sakuraus.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: AM335x touchscreen issues
Date: Wed, 27 May 2015 09:36:35 +0530	[thread overview]
Message-ID: <556542CB.80106@ti.com> (raw)
In-Reply-To: <20150526230649.GB24948@deathray>

Hi Michael,

On Wednesday 27 May 2015 04:36 AM, Michael Welling wrote:
> On Tue, May 26, 2015 at 10:31:32PM +0000, Cooper Jr., Franklin wrote:
>>

[snip]

> 
> Perhaps there is coupling between the LCD lines and the ADC lines?

On Beaglebone Black with BB-View 4.3" Cape from Farnell, the LCD lines
and TSCADC lines are placed close to one another, hence the analog
signals are affected by digital LCD signals, leading to above issue.

This was reported when I submitted the patches in question. Please see
http://thread.gmane.org/gmane.linux.kernel.iio/14710/focus=121321
http://thread.gmane.org/gmane.linux.kernel.iio/14710/focus=15242

I did document this in my cover letter. Please see
http://thread.gmane.org/gmane.linux.kernel.iio/15583

I think its the same issue that you are facing.

Regards
Vignesh

  parent reply	other threads:[~2015-05-27  4:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 18:11 AM335x touchscreen issues Michael Welling
2015-05-26 18:37 ` Felipe Balbi
2015-05-26 20:53   ` Michael Welling
2015-05-26 21:15     ` Cooper Jr., Franklin
2015-05-26 21:28       ` Michael Welling
2015-05-26 21:34         ` Cooper Jr., Franklin
2015-05-26 21:36           ` Griffis, Brad
2015-05-26 21:50             ` Michael Welling
2015-05-26 22:25               ` Griffis, Brad
2015-05-26 22:46                 ` Michael Welling
2015-05-26 22:31               ` Cooper Jr., Franklin
2015-05-26 23:06                 ` Michael Welling
2015-05-26 23:37                   ` Cooper Jr., Franklin
2015-05-27  4:06                   ` Vignesh R [this message]
2015-05-27 17:29                     ` Michael Welling
2015-05-26 21:41           ` Michael Welling

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=556542CB.80106@ti.com \
    --to=vigneshr@ti.com \
    --cc=GWilson@sakuraus.com \
    --cc=balbi@ti.com \
    --cc=bgriffis@ti.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=fcooper@ti.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=mwelling@ieee.org \
    --cc=wsa@the-dreams.de \
    /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