From: Lucas De Marchi <lucas.demarchi@intel.com>
To: linux-i2c@vger.kernel.org
Cc: christian.ruppert@alitech.com, linux-kernel@vger.kernel.org,
mika.westerberg@linux.intel.com, jarkko.nikula@linux.intel.com
Subject: [PATCH v3 0/3] i2c: designware: improve performance for transfers
Date: Thu, 28 Jul 2016 19:03:41 -0300 [thread overview]
Message-ID: <1469743424-2480-1-git-send-email-lucas.demarchi@intel.com> (raw)
This can be considered a 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 (2):
i2c: designware: detect when dynamic tar update is possible
i2c: designware: do not disable adapter after transfer
drivers/i2c/busses/i2c-designware-core.c | 103 +++++++++++++++++++++----------
drivers/i2c/busses/i2c-designware-core.h | 1 +
2 files changed, 72 insertions(+), 32 deletions(-)
--
2.7.4
next reply other threads:[~2016-07-28 22:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:03 Lucas De Marchi [this message]
2016-07-28 22:03 ` [PATCH v3 1/3] i2c: designware: wait for disable/enable only if necessary Lucas De Marchi
2016-08-16 13:59 ` Jarkko Nikula
2016-07-28 22:03 ` [PATCH v3 2/3] i2c: designware: detect when dynamic tar update is possible Lucas De Marchi
2016-08-16 14:00 ` Jarkko Nikula
2016-08-16 14:07 ` De Marchi, Lucas
2016-08-17 8:05 ` Jarkko Nikula
2016-08-17 12:48 ` De Marchi, Lucas
2016-07-28 22:03 ` [PATCH v3 3/3] i2c: designware: do not disable adapter after transfer Lucas De Marchi
2016-08-16 14:00 ` Jarkko Nikula
2016-08-12 14:59 ` [PATCH v3 0/3] i2c: designware: improve performance for transfers Christian Ruppert
2016-08-15 12:34 ` De Marchi, Lucas
2016-08-16 12:14 ` 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=1469743424-2480-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 \
/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).