From: "Jürgen Beisert" <jbe@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Lothar Waßmann" <LW@karo-electronics.de>,
"Marek Vasut" <marex@denx.de>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
fabio.estevam@freescale.com, jic23@cam.ac.uk
Subject: Re: [PATCHv5] staging/iio/adc: change the MXS touchscreen driver implementation
Date: Mon, 23 Sep 2013 15:24:37 +0200 [thread overview]
Message-ID: <201309231524.38008.jbe@pengutronix.de> (raw)
In-Reply-To: <21056.12306.714098.398250@ipc1.ka-ro>
Hi Lothar,
On Monday 23 September 2013 14:12:02 Lothar Waßmann wrote:
> [...]
> > @Lothar: What kernel revision did you use? I had to go back to 3.9 to get
> > a
>
> Current linux-next (3.12-rc1).
Okay.
> > working kernel on the MX28EVK. More recent vanilla kernels stop working
> > (MMC and network fail here).
>
> I'm seeing some messages:
> |mxs-mmc 80010000.ssp: dummy supplies not allowed
> |fec 800f0000.ethernet: dummy supplies not allowed
It was my fault. I'm also working with 3.12-rc1 now.
> But without any apparent consequences. Maybe that's a problem with the
> MX28EVK?
It seems the LRADC delay feature does not work. The touch detection interrupt
happens and the driver switches to the Y plate measurement, arms the LRADC
delay unit ... and nothing more happens. The LRADC delay unit should start a
conversion on ADC channel 4. But it does not. Never.
The i.MX28 manual says the LRADC delay unit is driven by a 2 kHz clock, but
does not say what kind of clock it is (or is derived from). I guess now, this
clock isn't enabled and thus the delay unit can't work. At least on the
MX28EVK. On your TX28 platform the clock seems enabled and the delay unit can
do its job and drive the state machine.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-09-23 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 12:22 [PATCHv5] staging/iio/adc: change the MXS touchscreen driver implementation Juergen Beisert
2013-09-19 12:22 ` [PATCH 1/7] Staging/iio/adc/touchscreen/MXS: distinguish i.MX23's and i.MX28's LRADC Juergen Beisert
2013-09-19 12:22 ` [PATCH 2/7] Staging/iio/adc/touchscreen/MXS: separate i.MX28 specific register bits Juergen Beisert
2013-09-19 12:22 ` [PATCH 3/7] Staging/iio/adc/touchscreen/MXS: simplify register access Juergen Beisert
2013-09-19 12:22 ` [PATCH 4/7] Staging/iio/adc/touchscreen/MXS: add i.MX23 support to the LRADC touchscreen driver Juergen Beisert
2013-09-19 12:22 ` [PATCH 5/7] Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection Juergen Beisert
2013-09-21 12:36 ` Jonathan Cameron
2013-09-19 12:22 ` [PATCH 6/7] Staging/iio/adc/touchscreen/MXS: Remove old touchscreen detection implementation Juergen Beisert
2013-09-19 12:22 ` [PATCH 7/7] Staging/iio/adc/touchscreen/MXS: provide devicetree adaption Juergen Beisert
2013-09-21 12:42 ` Jonathan Cameron
2013-09-23 7:42 ` Jürgen Beisert
2013-09-22 23:55 ` [PATCHv5] staging/iio/adc: change the MXS touchscreen driver implementation Marek Vasut
2013-09-23 7:55 ` Jürgen Beisert
2013-09-23 9:25 ` Lothar Waßmann
2013-09-23 10:35 ` Jürgen Beisert
2013-09-23 10:36 ` Marek Vasut
2013-09-23 11:57 ` Jürgen Beisert
2013-09-23 12:12 ` Lothar Waßmann
2013-09-23 13:24 ` Jürgen Beisert [this message]
2013-09-23 13:40 ` Lothar Waßmann
2013-09-23 14:05 ` Jürgen Beisert
2013-09-23 13:40 ` Jürgen Beisert
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=201309231524.38008.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=LW@karo-electronics.de \
--cc=devel@driverdev.osuosl.org \
--cc=fabio.estevam@freescale.com \
--cc=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.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;
as well as URLs for NNTP newsgroup(s).