From: Lucas De Marchi <lucas.demarchi@intel.com>
To: linux-i2c@vger.kernel.org
Cc: Christian Ruppert <christian.ruppert@alitech.com>,
mika.westerberg@linux.intel.com, jarkko.nikula@linux.intel.com,
linux-kernel@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: [PATCH v4 0/4] i2c: designware: improve performance for transfers
Date: Tue, 23 Aug 2016 19:18:52 -0300 [thread overview]
Message-ID: <1471990736-30190-1-git-send-email-lucas.demarchi@intel.com> (raw)
Diff from v3:
- Fix over 80chars in one place
- Move check for adapter being able to dynamically update TAR to be done
on probe time rather than init as requested by Jarkko
For the previous version, Christian had added:
Tested-by: Christian Ruppert <christian.ruppert@alitech.com>
on TB101 with Linux-4.7
And Jarkko added his Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
on patches 1 and 3 (now 4).
There's a new patch #2 as a preparatory work to move the check
mentioned above to i2c_dw_probe().
v3 of "i2c: designware: do not disable adapter after transfer". Differences
are:
- Now there's a first patch that does not depend on IC_TAR being dynamically
enabled/disabled: it just doesn't wait for the state change when not needed.
- We added a patch that allows detecting if HW supports the dynamic TAR updates
- In the last patch the bits were changed as suggested by Jarkko.
- This is tested on BayTrail and CherryTrail, both of them returning true for
"dynamically update TAR"
José Roberto de Souza (1):
i2c: designware: wait for disable/enable only if necessary
Lucas De Marchi (3):
i2c: designware: add common functions for locking
i2c: designware: detect when dynamic tar update is possible
i2c: designware: do not disable adapter after transfer
drivers/i2c/busses/i2c-designware-core.c | 162 +++++++++++++++++++++----------
drivers/i2c/busses/i2c-designware-core.h | 1 +
2 files changed, 111 insertions(+), 52 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-23 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 22:18 Lucas De Marchi [this message]
2016-08-23 22:18 ` [PATCH v4 1/4] i2c: designware: wait for disable/enable only if necessary Lucas De Marchi
2017-03-26 19:44 ` Andrey Utkin
2017-03-27 8:29 ` Jarkko Nikula
2016-08-23 22:18 ` [PATCH v4 2/4] i2c: designware: add common functions for locking Lucas De Marchi
2016-08-23 22:18 ` [PATCH v4 3/4] i2c: designware: detect when dynamic tar update is possible Lucas De Marchi
2016-08-25 20:03 ` Wolfram Sang
2016-08-23 22:18 ` [PATCH v4 4/4] i2c: designware: do not disable adapter after transfer Lucas De Marchi
2016-08-24 10:31 ` [PATCH v4 0/4] i2c: designware: improve performance for transfers Jarkko Nikula
2016-08-25 16:23 ` Christian Ruppert
2016-08-25 20:07 ` 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=1471990736-30190-1-git-send-email-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=christian.ruppert@alitech.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).