From: Wolfram Sang <wsa@kernel.org>
To: Lucas Tanure <tanureal@opensource.cirrus.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v2 RESEND] i2c: cadence: Increase timeout per message if necessary
Date: Sat, 14 May 2022 15:59:06 +0200 [thread overview]
Message-ID: <Yn+1qhStF9TiyJVj@shikoro> (raw)
In-Reply-To: <20220413091410.17970-1-tanureal@opensource.cirrus.com>
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
On Wed, Apr 13, 2022 at 10:14:10AM +0100, Lucas Tanure wrote:
> Timeout as 1 second sets an upper limit on the length
> of the transfer executed, but there is no maximum length
> of a write or read message set in i2c_adapter_quirks for
> this controller.
>
> This upper limit affects devices that require sending
> large firmware blobs over I2C.
>
> To remove that limitation, calculate the minimal time
> necessary, plus some wiggle room, for every message and
> use it instead of the default one second, if more than
> one second.
>
> Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-14 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 9:14 [PATCH v2 RESEND] i2c: cadence: Increase timeout per message if necessary Lucas Tanure
2022-05-14 13:59 ` 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=Yn+1qhStF9TiyJVj@shikoro \
--to=wsa@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=patches@opensource.cirrus.com \
--cc=shubhrajyoti.datta@xilinx.com \
--cc=tanureal@opensource.cirrus.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