devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qii Wang <qii.wang@mediatek.com>
To: Boris Lysov <arzamas-16@mail.ee>
Cc: <linux-i2c@vger.kernel.org>, <robh+dt@kernel.org>,
	<matthias.bgg@gmail.com>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: i2c: i2c-mt65xx: Update binding example
Date: Mon, 7 Sep 2020 09:28:07 +0800	[thread overview]
Message-ID: <1599442087.25719.2.camel@mhfsdcap03> (raw)
In-Reply-To: <20200904223345.3daea5ad@hp15>

On Fri, 2020-09-04 at 22:33 +0300, Boris Lysov wrote:
> Example uses values for MT6589 SoC, but MT6577 was specified in "compatible" property.
> 

Why do you think the example is MT6589 SoC, not MT6577?

> Signed-off-by: Boris Lysov <arzamas-16@mail.ee>
> ---
>  Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt b/Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt
> index 7f0194fdd0cc..acf3d4d28b98 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt
> @@ -36,7 +36,7 @@ Optional properties:
>  Example:
>  
>  	i2c0: i2c@1100d000 {
> -			compatible = "mediatek,mt6577-i2c";
> +			compatible = "mediatek,mt6589-i2c";
>  			reg = <0x1100d000 0x70>,
>  			      <0x11000300 0x80>;
>  			interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_LOW>;


  reply	other threads:[~2020-09-07  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 19:33 [PATCH] dt-bindings: i2c: i2c-mt65xx: Update binding example Boris Lysov
2020-09-07  1:28 ` Qii Wang [this message]
2020-09-07 15:08   ` Boris Lysov
2020-09-14  2:09     ` Qii Wang
2020-10-25 18:53       ` Boris Lysov

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=1599442087.25719.2.camel@mhfsdcap03 \
    --to=qii.wang@mediatek.com \
    --cc=arzamas-16@mail.ee \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    /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).