From: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 3/9] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards
Date: Mon, 15 May 2017 09:53:37 +0200 [thread overview]
Message-ID: <33b3a8a3-006b-91b3-e30d-56518fb9ae7a@gmail.com> (raw)
In-Reply-To: <e8f5dc8578c3980ac9c6411ad7fae1c8d747f567.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
On 12/05/17 09:56, sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org wrote:
> From: Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
>
> Because there are two versions of MT7623 SoC that is MT7623a and MT7623n
> respectively. So update the part of MT7623n bindings to allow that people
> tend to differentiate which MT7623 SoC the boards applies.
>
> Signed-off-by: John Crispin <john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org>
> Signed-off-by: Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
> ---
> Documentation/devicetree/bindings/arm/mediatek.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt b/Documentation/devicetree/bindings/arm/mediatek.txt
> index c860b24..0924b62 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek.txt
> +++ b/Documentation/devicetree/bindings/arm/mediatek.txt
> @@ -1,6 +1,6 @@
> MediaTek mt65xx, mt67xx & mt81xx Platforms Device Tree Bindings
>
> -Boards with a MediaTek mt65xx/mt67xx/mt81xx SoC shall have the
> +Boards with a MediaTek mt65xx/mt67xx/mt762x/mt81xx SoC shall have the
> following property:
>
> Required root node property:
> @@ -12,7 +12,7 @@ compatible: Must contain one of
> "mediatek,mt6592"
> "mediatek,mt6755"
> "mediatek,mt6795"
> - "mediatek,mt7623"
> + "mediatek,mt7623" which is referred to MT7623N SoC
> "mediatek,mt8127"
> "mediatek,mt8135"
> "mediatek,mt8173"
> @@ -38,9 +38,9 @@ Supported boards:
> - Evaluation board for MT6795(Helio X10):
> Required root node properties:
> - compatible = "mediatek,mt6795-evb", "mediatek,mt6795";
> -- Evaluation board for MT7623:
> +- Reference board for MT7623n with NAND:
> Required root node properties:
> - - compatible = "mediatek,mt7623-evb", "mediatek,mt7623";
> + - compatible = "mediatek,mt7623n-rfb-nand", "mediatek,mt7623";
Please explain in the commit message why you change this binding and why
this is not problematic. Either in this patch or add a new one.
For convenience for the device-tree maintainer, add the binding patches
at the beginning of your patch list. It makes their life easier and a
review faster, a clear win-win situation :)
Thanks,
Matthias
> - MTK mt8127 tablet moose EVB:
> Required root node properties:
> - compatible = "mediatek,mt8127-moose", "mediatek,mt8127";
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-15 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 7:56 [PATCH v3 0/9] arm: dts: extend mt7623 support sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-12 7:56 ` [PATCH v3 1/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file sean.wang
[not found] ` <e8d8ba305d0e245753ffc78479b4ca4cfd4c4d5f.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-12 10:46 ` kbuild test robot
2017-05-12 15:46 ` Matthias Brugger
[not found] ` <7f1d5fb3-5295-bb61-f21b-9d08bfaf070c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-13 0:44 ` Fengguang Wu
2017-05-12 7:56 ` [PATCH v3 3/9] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards sean.wang
[not found] ` <e8f5dc8578c3980ac9c6411ad7fae1c8d747f567.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-15 7:53 ` Matthias Brugger [this message]
2017-05-15 9:19 ` Sean Wang
2017-05-12 7:56 ` [PATCH v3 4/9] dt-bindings: arm: mediatek: add bindings for mediatek MT7623a SoC Platform sean.wang
[not found] ` <1e21077e4676a8b2596ec5f04251905760147920.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-15 20:51 ` Rob Herring
[not found] ` <cover.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-12 7:56 ` [PATCH v3 2/9] arm: dts: mt7623: rename mt7623-evb.dts to arch/arm/boot/dts/mt7623n-rfb.dtsi sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-12 7:56 ` [PATCH v3 5/9] ARM: mediatek: add MT7623a smp bringup code sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-12 7:56 ` [PATCH v3 6/9] arm: dts: mt7623: cleanup the mt7623n rfb uart nodes sean.wang
2017-05-12 7:56 ` [PATCH v3 7/9] arm: dts: mt7623: enable the usb device on the mt7623n rfb sean.wang
[not found] ` <98cb8c175852364c58425d7b59fe7b182e2b8d02.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-12 11:11 ` kbuild test robot
2017-05-12 7:56 ` [PATCH v3 8/9] arm: dts: mt7623: enable the nand device on the mt7623n nand rfb sean.wang
2017-05-12 7:56 ` [PATCH v3 9/9] arm: dts: mt7623: add dts file for Bananapi R2 (BPI-R2) board sean.wang
[not found] ` <0beebd0e209b4caeb349a062be7ef245d0689fb6.1494574682.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-12 11:39 ` kbuild test robot
2017-05-15 20:56 ` Rob Herring
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=33b3a8a3-006b-91b3-e30d-56518fb9ae7a@gmail.com \
--to=matthias.bgg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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).