From: h.feurstein@gmail.com (Hubert Feurstein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/5] AT91: replace broken TWI driver i2c-at91.c
Date: Fri, 25 Nov 2011 16:42:13 +0100 [thread overview]
Message-ID: <4ECFB755.6060509@gmail.com> (raw)
In-Reply-To: <cover.1322062555.git.n.voss@weinmann.de>
Hi,
I've tested this driver on a 2.6.38 kernel with several i2c clients
(temp-sensor, audio-codec, touchscreen-controller, w1-bridge,
io-expanders) and works without problems. SoC: at91sam9g45
Because of the 2.6.38 kernel, I had to skip "[PATCH v7 2/5] Replace
clk_lookup.con_id with clk_lookup.dev_id entries for twi clk" and used
instead: at91_clock_associate("twi0_clk", &at91sam9g45_twi0_device.dev,
"twi_clk");
Best Regards
Hubert
On 2011-11-23 16:35, Nikolaus Voss wrote:
> The old driver has two main deficencies:
> i) No repeated start (Sr) condiction is possible, this makes it unusable
> e.g. for most SMBus transfers.
> ii) I/O was done with polling/busy waiting what caused over-/underruns
> even at light system loads and clock speeds.
>
> The new driver overcomes these deficencies and in addition allows for
> more than one TWI interface.
>
Tested-by: Hubert Feurstein <h.feurstein@gmail.com>
next prev parent reply other threads:[~2011-11-25 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1322062555.git.n.voss@weinmann.de>
[not found] ` <ee23c49c5a190a2cce0859f7828c2dc771ff3207.1322062555.git.n.voss@weinmann.de>
2011-11-23 16:18 ` [PATCH v7 3/5] drivers/i2c/busses/i2c-at91.c: add new driver Arnd Bergmann
2011-11-24 10:33 ` Voss, Nikolaus
2011-11-24 15:39 ` Arnd Bergmann
2011-11-24 16:36 ` Voss, Nikolaus
2011-11-24 16:47 ` Arnd Bergmann
2011-11-23 23:32 ` [PATCH v7 0/5] AT91: replace broken TWI driver i2c-at91.c Ben Dooks
2011-11-24 6:33 ` Voss, Nikolaus
2011-11-24 22:13 ` Ryan Mallon
2011-11-25 15:42 ` Hubert Feurstein [this message]
2011-12-28 13:36 ` AW: " Carsten Behling
2012-01-11 14:06 ` Voss, Nikolaus
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=4ECFB755.6060509@gmail.com \
--to=h.feurstein@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).