linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: linux-i2c@vger.kernel.org, raviteja.narayanam@xilinx.com,
	michal.simek@xilinx.com, anurag.kumar.vulisha@xilinx.com,
	shubhrajyoti.datta@xilinx.com
Subject: Re: [PATCH] i2c: cadence: Change large transfer count reset logic to be unconditional
Date: Sat, 16 Jul 2022 14:46:48 +0200	[thread overview]
Message-ID: <YtKzOBdSy754CkQ1@shikoro> (raw)
In-Reply-To: <20220614232919.1372621-1-robert.hancock@calian.com>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

On Tue, Jun 14, 2022 at 05:29:19PM -0600, Robert Hancock wrote:
> Problems were observed on the Xilinx ZynqMP platform with large I2C reads.
> When a read of 277 bytes was performed, the controller NAKed the transfer
> after only 252 bytes were transferred and returned an ENXIO error on the
> transfer.
> 
> There is some code in cdns_i2c_master_isr to handle this case by resetting
> the transfer count in the controller before it reaches 0, to allow larger
> transfers to work, but it was conditional on the CDNS_I2C_BROKEN_HOLD_BIT
> quirk being set on the controller, and ZynqMP uses the r1p14 version of
> the core where this quirk is not being set. The requirement to do this to
> support larger reads seems like an inherently required workaround due to
> the core only having an 8-bit transfer size register, so it does not
> appear that this should be conditional on the broken HOLD bit quirk which
> is used elsewhere in the driver.
> 
> Remove the dependency on the CDNS_I2C_BROKEN_HOLD_BIT for this transfer
> size reset logic to fix this problem.
> 
> Fixes: 63cab195bf49 ("i2c: removed work arounds in i2c driver for Zynq Ultrascale+ MPSoC")
> Signed-off-by: Robert Hancock <robert.hancock@calian.com>

Applied to for-current, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2022-07-16 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 23:29 [PATCH] i2c: cadence: Change large transfer count reset logic to be unconditional Robert Hancock
2022-06-16  5:17 ` Datta, Shubhrajyoti
2022-06-16 17:03   ` Robert Hancock
2022-07-14 11:58 ` Datta, Shubhrajyoti
2022-07-14 12:35   ` Michal Simek
2022-07-16 12:46   ` wsa
2022-07-16 12:46 ` 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=YtKzOBdSy754CkQ1@shikoro \
    --to=wsa@kernel.org \
    --cc=anurag.kumar.vulisha@xilinx.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=raviteja.narayanam@xilinx.com \
    --cc=robert.hancock@calian.com \
    --cc=shubhrajyoti.datta@xilinx.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).