From: "De Marchi, Lucas" <lucas.demarchi@intel.com>
To: "christian.ruppert@alitech.com" <christian.ruppert@alitech.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Cc: "mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v3 0/3] i2c: designware: improve performance for transfers
Date: Mon, 15 Aug 2016 12:34:14 +0000 [thread overview]
Message-ID: <1471264451.2394.5.camel@intel.com> (raw)
In-Reply-To: <28c393bf-416b-b406-ff39-a2d85317a102@alitech.com>
On Fri, 2016-08-12 at 16:59 +0200, Christian Ruppert wrote:
> On 29.07.2016 00:03, Lucas De Marchi wrote:
> >
> > 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"
>
> Tested-by: Christian Ruppert <christian.ruppert@alitech.com>
> on TB101 with Linux-4.7
>
> Seems to work perfectly now, congratulations and thanks for your
> patience with our platform... This was a hard one!
Awesome, thanks for testing this series.
Looks like I forgot to CC Wolfram. CC'ing now on this cover letter, let
me know if you also need the individual patches.
Lucas De Marchi
>
> >
> > 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(-)
> >
>
next prev parent reply other threads:[~2016-08-15 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:03 [PATCH v3 0/3] i2c: designware: improve performance for transfers Lucas De Marchi
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 [this message]
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=1471264451.2394.5.camel@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).