From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: Andrew Victor <avictor.za-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [RFC: 2.6 patch] remove the i2c-at91.c driver
Date: Thu, 4 Sep 2008 13:25:30 -0700 [thread overview]
Message-ID: <200809041325.30330.david-b@pacbell.net> (raw)
In-Reply-To: <cd73a99e0809041314i54c7fd71ued53270517ecc829-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thursday 04 September 2008, Andrew Victor wrote:
> According to the datasheet, the G20 supports both clock stretching and
> repeated starts.
Same is true for docs about current silicon ... but the clock
stretching doesn't prevent those FIFO problems, and repeated
starts are barely enough to support older versions of SMBus.
Is that a *general* mechanism for repeated starts?
Or is it just the current/limited one where there can be at most
two segments in any combined message, going to the same slave
address ... a write of up to 3 bytes (assuming 7bit addressses)
then a longer read?
Either way: driver updates needed for that!
(I'd call clock stretching to prevent those FIFO issues just
a bugfix, myself. It should need no driver updates.)
> The TWI is now also connected to a PDC, so we can set-up a DMA buffer
> for the TWI receives and transmits.
Using DMA also implies driver updates.
Maybe the best answer would be to remove this and have a g20-specific
driver later.
- Dave
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-09-04 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 16:10 [RFC: 2.6 patch] remove the i2c-at91.c driver Adrian Bunk
[not found] ` <20080831161005.GC3695-re2QNgSbS3j4D6uPqz5PAwR5/fbUUdgG@public.gmane.org>
2008-09-01 13:13 ` Andrew Victor
[not found] ` <cd73a99e0809010613w40569b3fv9f5fc96a7bfb6a29-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-02 10:11 ` Ben Dooks
[not found] ` <20080902101127.GJ2716-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-09-04 18:55 ` Andrew Victor
[not found] ` <cd73a99e0809041155m1f9e576dt5659da679fffb56d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-04 19:18 ` David Brownell
[not found] ` <200809041218.49604.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-09-04 20:14 ` Andrew Victor
[not found] ` <cd73a99e0809041314i54c7fd71ued53270517ecc829-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-04 20:25 ` David Brownell [this message]
[not found] ` <200809041325.30330.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-09-22 18:22 ` Andrew Victor
2008-09-02 10:24 ` Ben Dooks
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=200809041325.30330.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=avictor.za-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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