From: cyrille.pitchen@atmel.com (Cyrille Pitchen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] i2c: at91: add support to FIFOs and alternative command
Date: Fri, 29 May 2015 15:50:07 +0200 [thread overview]
Message-ID: <cover.1432907105.git.cyrille.pitchen@atmel.com> (raw)
This series of patches adds support of two new features which will be
introduced with Atmel sama5d2x SoC.
First, the alternative command mode eases the sending of STOP conditions.
Before starting an I2C transaction, the size data to be transfered is
written into the new Alternative Command Register. For each byte transferred,
the I2C controller decreases this counter and automatically sends a STOP
condition when the counter value reaches 0, that is to say when the last byte
of the transaction has been sent/received. So there is no longer need to set
the STOP bit into the Control Register.
Then the use of FIFOs allows to reduce number I/O accesses: for instance,
the TX FIFO allows to write up to 4 data in a single access to the Transmit
Holding Register. Also the RX FIFO allows to read up to 4 data in a single
access to the Receive Holding Register. Currently only DMA transfers take
advantage of FIFOs.
Cyrille Pitchen (3):
i2c: at91: add support for new alternative command mode
i2c: at91: print hardware version
i2c: at91: add support to FIFOs
drivers/i2c/busses/i2c-at91.c | 347 +++++++++++++++++++++++++++++++++++-------
1 file changed, 288 insertions(+), 59 deletions(-)
--
1.8.2.2
next reply other threads:[~2015-05-29 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 13:50 Cyrille Pitchen [this message]
2015-05-29 13:50 ` [PATCH 1/3] i2c: at91: add support for new alternative command mode Cyrille Pitchen
2015-06-01 9:21 ` Ludovic Desroches
2015-05-29 13:50 ` [PATCH 2/3] i2c: at91: print hardware version Cyrille Pitchen
2015-06-01 9:23 ` Ludovic Desroches
2015-05-29 13:50 ` [PATCH 3/3] i2c: at91: add support to FIFOs Cyrille Pitchen
2015-06-01 9:44 ` Ludovic Desroches
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=cover.1432907105.git.cyrille.pitchen@atmel.com \
--to=cyrille.pitchen@atmel.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).