From: Wolfram Sang <wsa@the-dreams.de>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: peda@axentia.se, linux-i2c@vger.kernel.org
Subject: Re: [PATCH i2c-next 3/4] i2c: mlxcpld: Reduce polling time for performance improvement
Date: Mon, 4 Oct 2021 21:59:05 +0200 [thread overview]
Message-ID: <YVtdCceWuSVHAoLb@kunai> (raw)
In-Reply-To: <20210823144504.1249203-4-vadimp@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
On Mon, Aug 23, 2021 at 05:45:03PM +0300, Vadim Pasternak wrote:
> Decrease polling time 'MLXCPLD_I2C_POLL_TIME' from 400 usec to 200
> usec. It improves performance of I2C transactions.
>
> Reliability of setting polling time to 200 usec has been validated
> across all the supported systems.
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-04 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:45 [PATCH i2c-next 0/4] i2c: mlxcpld: Add fixes and features for transaction polling time setting Vadim Pasternak
2021-08-23 14:45 ` [PATCH i2c-next 1/4] i2c: mlxcpld: Fix criteria for frequency setting Vadim Pasternak
2021-10-04 19:58 ` Wolfram Sang
2021-08-23 14:45 ` [PATCH i2c-next 2/4] i2c: mlxcpld: Modify register setting for 400KHz frequency Vadim Pasternak
2021-10-04 19:59 ` Wolfram Sang
2021-08-23 14:45 ` [PATCH i2c-next 3/4] i2c: mlxcpld: Reduce polling time for performance improvement Vadim Pasternak
2021-10-04 19:59 ` Wolfram Sang [this message]
2021-08-23 14:45 ` [PATCH i2c-next 4/4] i2c: mlxcpld: Allow flexible polling time setting for I2C transactions Vadim Pasternak
2021-10-04 20:00 ` Wolfram Sang
2021-10-11 10:32 ` Wolfram Sang
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=YVtdCceWuSVHAoLb@kunai \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
--cc=vadimp@nvidia.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).