From: Eddie Huang <eddie.huang@mediatek.com>
To: Liguo Zhang <liguo.zhang@mediatek.com>
Cc: "Wolfram Sang" <wsa@the-dreams.de>,
"Xudong Chen (陈旭东)" <Xudong.Chen@mediatek.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] Mediatek I2C driver fixup
Date: Mon, 2 Nov 2015 14:35:06 +0800 [thread overview]
Message-ID: <1446446106.12497.6.camel@mtksdaap41> (raw)
In-Reply-To: <1445936367-30141-1-git-send-email-liguo.zhang@mediatek.com>
On Tue, 2015-10-27 at 16:59 +0800, Liguo Zhang wrote:
> This series contain two patches, first is to optimize Mediatek I2C driver to use WRRD
> if hardware support auto restart. Because auto restart will issue auto restart
> interrupt, change to use WRRD can reduce interrupt latency. The second is to fix
> multi transfer error in high speed mode. If hardware support auto restart, need driver
> to send master code first.
Please fix checkpatch warning in 2/2, then you get my reviewed-by for
this series:
Reviewed-by:Eddie Huang <eddie.huang@mediatek.com>
>
> Liguo Zhang (2):
> i2c: mediatek: add i2c first write then read optimization
> i2c: mediatek: fix i2c multi transfer issue in high speed mode
>
> drivers/i2c/busses/i2c-mt65xx.c | 77 +++++++++++++++++++++++++++++++++++++----
> 1 file changed, 71 insertions(+), 6 deletions(-)
prev parent reply other threads:[~2015-11-02 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 8:59 [PATCH 0/2] Mediatek I2C driver fixup Liguo Zhang
2015-10-27 8:59 ` [PATCH 1/2] i2c: mediatek: add i2c first write then read optimization Liguo Zhang
2015-10-27 8:59 ` [PATCH 2/2] i2c: mediatek: fix i2c multi transfer issue in high speed mode Liguo Zhang
2015-11-02 6:35 ` Eddie Huang [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=1446446106.12497.6.camel@mtksdaap41 \
--to=eddie.huang@mediatek.com \
--cc=Xudong.Chen@mediatek.com \
--cc=liguo.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.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).