From: Matthias Brugger <matthias.bgg@gmail.com>
To: Jun Gao <jun.gao@mediatek.com>, Wolfram Sang <wsa@the-dreams.de>
Cc: 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 v4 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding
Date: Mon, 29 May 2017 17:30:26 +0200 [thread overview]
Message-ID: <1d073e6a-e275-24e1-7954-f1af913bd03b@gmail.com> (raw)
In-Reply-To: <1495784107-6711-2-git-send-email-jun.gao@mediatek.com>
On 26/05/17 09:35, Jun Gao wrote:
> From: Jun Gao <jun.gao@mediatek.com>
>
> Add MT2701 i2c binding to i2c-mt6577.txt and there is no need to
> modify i2c driver.
>
> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-mt6577.txt | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> index 0ce6fa3..52f2023 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
> @@ -4,11 +4,12 @@ The Mediatek's I2C controller is used to interface with I2C devices.
>
> Required properties:
> - compatible: value should be either of the following.
> - (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
> - (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
> - (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
> - (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
> - (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
> + "mediatek,mt2701-i2c", "mediatek,mt6577-i2c": for Mediatek MT2701
I send a cleanup patch for the file, which fixes all the other SoCs.
I can fold this one into it, a soon as I got a Signed-off from the DT
maintainers.
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> + "mediatek,mt6577-i2c": for Mediatek MT6577
> + "mediatek,mt6589-i2c": for Mediatek MT6589
> + "mediatek,mt8127-i2c": for Mediatek MT8127
> + "mediatek,mt8135-i2c": for Mediatek MT8135
> + "mediatek,mt8173-i2c": for Mediatek MT8173
> - reg: physical base address of the controller and dma base, length of memory
> mapped region.
> - interrupts: interrupt number to the cpu.
>
next prev parent reply other threads:[~2017-05-29 15:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 7:35 [PATCH v4 0/2] Add i2c dt-binding and device node for Mediatek MT2701 Soc Jun Gao
2017-05-26 7:35 ` [PATCH v4 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding Jun Gao
2017-05-29 15:30 ` Matthias Brugger [this message]
2017-05-30 21:38 ` Rob Herring
2017-05-31 2:24 ` Jun Gao
2017-05-31 12:05 ` Matthias Brugger
2017-05-26 7:35 ` [PATCH v4 2/2] arm: dts: Add Mediatek MT2701 i2c device node Jun Gao
2017-06-12 11:54 ` Jun Gao
2017-06-13 9:36 ` Matthias Brugger
2017-06-13 10:24 ` Jun Gao
2017-06-13 12:52 ` Matthias Brugger
2017-06-13 13:23 ` Jun Gao
2017-06-13 13:45 ` Matthias Brugger
2017-06-14 1:11 ` Jun Gao
2017-06-14 9:24 ` Matthias Brugger
2017-06-14 9:43 ` Jun Gao
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=1d073e6a-e275-24e1-7954-f1af913bd03b@gmail.com \
--to=matthias.bgg@gmail.com \
--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=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
all inboxes | Powered by JetHome®