From: Wolfram Sang <wsa@the-dreams.de>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
nicolas.ferre@atmel.com, linux-arm-kernel@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>
Subject: Re: [PATCH] i2c: at91: fix support of the "alternative command" feature
Date: Mon, 15 Aug 2016 00:34:37 +0200 [thread overview]
Message-ID: <20160814223437.GG10501@katana> (raw)
In-Reply-To: <20160803145826.11927-1-ludovic.desroches@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Wed, Aug 03, 2016 at 04:58:26PM +0200, Ludovic Desroches wrote:
> From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>
> The "alternative command" feature was introduced with sama5d2 SoCs.
>
> Its purpose is to let the hardware i2c controller automatically send the
> STOP condition on the i2c bus at the end of a data transfer.
> Without this feature, the i2c driver has to write the 'STOP' bit into the
> Control Register so the hardware i2c controller is triggered to send the
> STOP condition on the bus.
>
> Using the "alternative command" feature requires to set the transfer data
> length into the 8bit DATAL field of the Alternative Command Register.
> Hence only data transfers up to 255 bytes can take advantage of the
> "alternative command" feature. For greater data transfer sizes, the driver
> should use the previous implementation, when the "alternative command"
> support was not implemented yet.
>
> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-14 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 14:58 [PATCH] i2c: at91: fix support of the "alternative command" feature Ludovic Desroches
2016-08-14 22:34 ` Wolfram Sang [this message]
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=20160814223437.GG10501@katana \
--to=wsa@the-dreams.de \
--cc=cyrille.pitchen@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
/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).