From: Rob Herring <robh@kernel.org>
To: Jun Gao <jun.gao@mediatek.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
srv_heupstream@mediatek.com, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: i2c: Add MediaTek MT2712 i2c binding
Date: Wed, 20 Dec 2017 12:43:47 -0600 [thread overview]
Message-ID: <20171220184347.o2f5ez3n4vmbrq7w@rob-hp-laptop> (raw)
In-Reply-To: <1513666263-6443-2-git-send-email-jun.gao@mediatek.com>
On Tue, Dec 19, 2017 at 02:51:01PM +0800, Jun Gao wrote:
> From: Jun Gao <jun.gao@mediatek.com>
>
> Add MT2712 i2c binding to binding file. Compare to MT8173 i2c
> controller, MT2712 has timing adjust registers which can adjust
> the internal divider of i2c source clock, SCL duty cycle, SCL
> compare point, start(repeated start) and stop time, SDA change
> time.
>
> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-mtk.txt | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-12-20 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 6:51 [PATCH 0/3] Add i2c dt-binding and compatible for Mediatek MT2712 Jun Gao
2017-12-19 6:51 ` [PATCH 1/3] dt-bindings: i2c: Add MediaTek MT2712 i2c binding Jun Gao
2017-12-20 18:43 ` Rob Herring [this message]
2018-01-03 23:55 ` Wolfram Sang
[not found] ` <1513666263-6443-1-git-send-email-jun.gao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-12-19 6:51 ` [PATCH 2/3] i2c: mediatek: Add i2c compatible for MediaTek MT2712 Jun Gao
2018-01-03 23:55 ` Wolfram Sang
2017-12-19 6:51 ` [PATCH 3/3] i2c: mediatek: Enable i2c module clock before i2c registers access Jun Gao
[not found] ` <1513666263-6443-4-git-send-email-jun.gao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-01-03 23:55 ` 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=20171220184347.o2f5ez3n4vmbrq7w@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jun.gao@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=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).