From: Harvey Hunt <Harvey.Hunt@imgtec.com>
To: Rob Herring <robh@kernel.org>
Cc: <mark.rutland@arm.com>, <ralf@linux-mips.org>, <john@phrozen.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-mips@linux-mips.org>
Subject: Re: [PATCH 2/3] MIPS: dts: Add VoCore2 board
Date: Fri, 18 Aug 2017 14:21:59 +0100 [thread overview]
Message-ID: <5b00f77c-12be-76d2-e9eb-03f8a4b6375e@imgtec.com> (raw)
In-Reply-To: <20170817213628.nrkeuek7vu6oebfx@rob-hp-laptop>
Hi Rob,
Thanks for the review.
On 17/08/17 22:36, Rob Herring wrote:
> On Tue, Aug 15, 2017 at 05:32:52PM +0100, Harvey Hunt wrote:
>> The VoCore2 board is a low cost MT7628A based board with 128MB RAM, 16MB
>> flash and multiple external peripherals.
>>
>> This initial DTS provides enough support to get to userland and use the USB
>> port.
>>
>> Signed-off-by: Harvey Hunt <harvey.hunt@imgtec.com>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: devicetree@vger.kernel.org
>> Cc: linux-mips@linux-mips.org
>> ---
>> MAINTAINERS | 6 ++++++
>> arch/mips/boot/dts/ralink/Makefile | 1 +
>> arch/mips/boot/dts/ralink/vocore2.dts | 18 ++++++++++++++++++
>> arch/mips/ralink/Kconfig | 5 +++++
>> 4 files changed, 30 insertions(+)
>> create mode 100644 arch/mips/boot/dts/ralink/vocore2.dts
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 6f7721d..82dcc6f 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14127,6 +14127,12 @@ L: netdev@vger.kernel.org
>> S: Maintained
>> F: drivers/net/vmxnet3/
>>
>> +VOCORE VOCORE2 BOARD
>> +M: Harvey Hunt <harveyhuntnexus@gmail.com>
>> +L: linux-mips@linux-mips.org
>> +S: Maintained
>> +F: arch/mips/boot/dts/ralink/vocore2.dts
>> +
>> VOLTAGE AND CURRENT REGULATOR FRAMEWORK
>> M: Liam Girdwood <lgirdwood@gmail.com>
>> M: Mark Brown <broonie@kernel.org>
>> diff --git a/arch/mips/boot/dts/ralink/Makefile b/arch/mips/boot/dts/ralink/Makefile
>> index 2a72259..a191788 100644
>> --- a/arch/mips/boot/dts/ralink/Makefile
>> +++ b/arch/mips/boot/dts/ralink/Makefile
>> @@ -2,6 +2,7 @@ dtb-$(CONFIG_DTB_RT2880_EVAL) += rt2880_eval.dtb
>> dtb-$(CONFIG_DTB_RT305X_EVAL) += rt3052_eval.dtb
>> dtb-$(CONFIG_DTB_RT3883_EVAL) += rt3883_eval.dtb
>> dtb-$(CONFIG_DTB_MT7620A_EVAL) += mt7620a_eval.dtb
>> +dtb-$(CONFIG_DTB_VOCORE2) += vocore2.dtb
>>
>> obj-y += $(patsubst %.dtb, %.dtb.o, $(dtb-y))
>>
>> diff --git a/arch/mips/boot/dts/ralink/vocore2.dts b/arch/mips/boot/dts/ralink/vocore2.dts
>> new file mode 100644
>> index 0000000..7591340
>> --- /dev/null
>> +++ b/arch/mips/boot/dts/ralink/vocore2.dts
>> @@ -0,0 +1,18 @@
>> +/dts-v1/;
>> +
>> +#include "mt7628a.dtsi"
>> +
>> +/ {
>> + compatible = "vocore,vocore2", "ralink,mt7628a-soc";
>
> Is vocore,vocore2 documented?
It's not, do you want me to add a file in
Documentation/devicetree/bindings/mips?
If so, shall I just create a vocore.txt file or create a "vocore"
directory with vocore2.txt in it?
Thanks,
Harvey
>
>> + model = "VoCore2";
>> +
>> + memory@0 {
>> + device_type = "memory";
>> + reg = <0x0 0x8000000>;
>> + };
>> +
>> + chosen {
>> + bootargs = "console=ttyS2,115200";
>> + stdout-path = "serial2:115200";
>> + };
>> +};
>> diff --git a/arch/mips/ralink/Kconfig b/arch/mips/ralink/Kconfig
>> index 710b04c..c2b2c2d 100644
>> --- a/arch/mips/ralink/Kconfig
>> +++ b/arch/mips/ralink/Kconfig
>> @@ -82,6 +82,11 @@ choice
>> depends on SOC_MT7620
>> select BUILTIN_DTB
>>
>> + config DTB_VOCORE2
>> + bool "VoCore2"
>> + depends on SOC_MT7620
>> + select BUILTIN_DTB
>> +
>> endchoice
>>
>> endif
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2017-08-18 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 16:32 [PATCH 1/3] dt-bindings: vendors: Add VoCore as a vendor Harvey Hunt
2017-08-15 16:32 ` [PATCH 2/3] MIPS: dts: Add VoCore2 board Harvey Hunt
2017-08-17 10:05 ` kbuild test robot
2017-08-17 21:36 ` Rob Herring
2017-08-18 13:21 ` Harvey Hunt [this message]
2017-08-15 16:32 ` [PATCH 3/3] MIPS: configs: Add VoCore2 defconfig Harvey Hunt
2017-08-17 21:35 ` [PATCH 1/3] dt-bindings: vendors: Add VoCore as a vendor 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=5b00f77c-12be-76d2-e9eb-03f8a4b6375e@imgtec.com \
--to=harvey.hunt@imgtec.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=ralf@linux-mips.org \
--cc=robh@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
all inboxes | Powered by JetHome®