From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawn.guo@linaro.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
brian@crystalfontz.com, linux-doc@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
jimwall@q.com, Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Landley <rob@landley.net>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCHv3 2/3] ARM: mxs: cfa10049: Switch bus i2c1 to bitbanging
Date: Tue, 02 Jul 2013 19:15:49 +0200 [thread overview]
Message-ID: <51D30AC5.9000701@free-electrons.com> (raw)
In-Reply-To: <201307021833.04282.marex@denx.de>
On 02/07/2013 18:33, Marek Vasut wrote:
> Dear Alexandre Belloni,
>
>> On 02/07/2013 13:50, Alexandre Belloni wrote:
>>> On 02/07/2013 13:45, Fabio Estevam wrote:
>>>> Shouldn't this be
>>>>
>>>> i2c@1 {
>>>>
>>>> reg = <1>; ?
>>>
>>> No, we have 4 devices on that mux and 2 pins to select the muxing.
>>
>> OK, got it working.
>>
>> So, the results:
>>
>> bitbanging:
>>
>> # time cat /sys/bus/iio/devices/iio\:device1/in_voltage0_raw
>> 2637
>> real 0m 0.09s
>> user 0m 0.01s
>> sys 0m 0.01s
>>
>>
>> i2c-mxs PIO mode:
>>
>> # time cat /sys/bus/iio/devices/iio\:device1/in_voltage0_raw
>> [ 35.007650] [sched_delayed] sched: RT throttling activated
>> 2627
>> real 0m 7.14s
>> user 0m 0.02s
>> sys 0m 0.01s
>>
>>
>> i2c-mxs PIO mode without LRADC:
>>
>> # time cat /sys/bus/iio/devices/iio\:device1/in_voltage0_raw
>> [ 18.007432] [sched_delayed] sched: RT throttling activated
>> 2629
>> real 0m 7.09s
>> user 0m 0.00s
>> sys 0m 0.03s
>>
>>
>> i2c-mxs DMA mode:
>>
>> # time cat /sys/bus/iio/devices/iio\:device1/in_voltage0_raw
>> 2631
>> real 0m 0.12s
>> user 0m 0.01s
>> sys 0m 0.01s
>>
>>
>> It seems fine for me.
>
> I think I'm getting a little lost in these gazilions of i2c and lradc threads.
> Can we not create one thread and keep the related stuff in there instead of
> discussing it all around !?
>
> Only one question comes to mind with this email -- what do LRADC and I2C have to
> do with each other here ?
>
Yeah, sorry, I meant the lradc touchscreen support. This seemed to
trigger the issue for Fabio but as my testing shows, this is not the
case for me, I get the issue with PIO, whether the lradc touchscreen
support is activated or not.
I think Torsten is the one that investigated it the most :
http://www.spinics.net/lists/linux-i2c/msg12619.html
> It'd be nice if someone could summarize on what I should focus and possibly
> prepare a testcase.
>
On my setup, it happens on every i2c read that are done in PIO mode.
But, my setup may be a bit unconventional as we are using a i2c gpio muxer.
Regards,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-07-02 17:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:24 [PATCHv3 0/3] Add support for the Nuvoton NAU7802 ADC to the cfa10049 Alexandre Belloni
2013-06-24 17:24 ` [PATCHv3 1/3] iio: Add Nuvoton NAU7802 ADC driver Alexandre Belloni
2013-07-04 9:08 ` Lars-Peter Clausen
2013-07-06 10:24 ` Jonathan Cameron
2013-07-09 14:04 ` Alexandre Belloni
2013-07-09 17:43 ` Jonathan Cameron
2013-06-24 17:24 ` [PATCHv3 2/3] ARM: mxs: cfa10049: Switch bus i2c1 to bitbanging Alexandre Belloni
2013-07-02 2:45 ` Fabio Estevam
2013-07-02 11:35 ` Alexandre Belloni
2013-07-02 11:45 ` Fabio Estevam
2013-07-02 11:50 ` Alexandre Belloni
2013-07-02 14:06 ` Alexandre Belloni
2013-07-02 16:33 ` Marek Vasut
2013-07-02 17:15 ` Alexandre Belloni [this message]
2013-07-06 10:26 ` Jonathan Cameron
2013-07-07 8:47 ` Alexandre Belloni
2013-06-24 17:24 ` [PATCHv3 3/3] ARM: mxs: cfa10049: Add NAU7802 ADCs to the device tree Alexandre Belloni
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=51D30AC5.9000701@free-electrons.com \
--to=alexandre.belloni@free-electrons.com \
--cc=brian@crystalfontz.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=festevam@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=jic23@cam.ac.uk \
--cc=jimwall@q.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=maxime.ripard@free-electrons.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=shawn.guo@linaro.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