linux-kernel - Re: [PATCH v2 3/3] i2c: iproc: Support larger TX transfer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160212214436.GC1529@katana>
Date:	Fri, 12 Feb 2016 22:44:37 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Ray Jui <ray.jui@...adcom.com>
Cc:	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
	bcm-kernel-feedback-list@...adcom.com,
	Icarus Chau <ichau@...adcom.com>, Ray Jui <rjui@...adcom.com>
Subject: Re: [PATCH v2 3/3] i2c: iproc: Support larger TX transfer

On Fri, Feb 12, 2016 at 01:10:43PM -0800, Ray Jui wrote:
> From: Ray Jui <rjui@...adcom.com>
> 
> The current iProc I2C driver only allows each TX transfer up to 63
> bytes (the TX FIFO has a size of 64 bytes, and one byte is reserved
> for slave address). This patch enhances the driver to support TX
> transfer in each I2C message for up to 65535 bytes (a practical
> maximum, since member 'max_write_len' of 'struct i2c_adapter_quirks is
> of type 'u16')
> 
> This works by loading up the I2C TX FIFO and enabling the TX underrun
> interrupt for each burst. After each burst of TX data is finished,
> i.e., when the TX FIFO becomes empty, the TX underrun interrupt will be
> triggered and another burst of TX data can be loaded into the TX FIFO.
> This repeats until all TX data are finished
> 
> Signed-off-by: Ray Jui <rjui@...adcom.com>
> Tested-by: Icarus Chau <ichau@...adcom.com>
> Reviewed-by: Scott Branden <sbranden@...adcom.com>

Applied to for-next, thanks!


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)