From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-mips@vger.kernel.org, paul.burton@mips.com,
keguang.zhang@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] MIPS: Loongson32: dts: add ls1b & ls1c
Date: Wed, 13 Mar 2019 09:08:42 +0800 [thread overview]
Message-ID: <04e55af9-4d2f-bf93-4b8a-a59735fa4cae@flygoat.com> (raw)
In-Reply-To: <CABGGiszYh0uE_ybrfhK2byz4XZVAm9wvL5tQg0R85nnLt4c1iw@mail.gmail.com>
Hi Rob,
Thanks for your reply, I have some questions on that:
在 2019/3/12 下午8:28, Rob Herring 写道:
> On Tue, Mar 12, 2019 at 4:16 AM Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>> Add devicetree skeleton for ls1b and ls1c
>>
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>> ---
>>
>> +/ {
>> + model = "Loongson LS1B";
>> + compatible = "loongson,ls1b";
> Documented?
Should I document the vendor string or whole
"loongson,ls1b"?
>
>> +
>> +};
>> +
>> +&ehci0 {
>> + status = "okay";
>> +};
>> +
>> +&ohci0 {
>> + status = "okay";
>> +};
>> \ No newline at end of file
> Fix this.
>
>> diff --git a/arch/mips/boot/dts/loongson/ls1c.dts b/arch/mips/boot/dts/loongson/ls1c.dts
>> new file mode 100644
>> index 000000000000..778d205a586e
>> --- /dev/null
>> +++ b/arch/mips/boot/dts/loongson/ls1c.dts
>> @@ -0,0 +1,25 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Copyright (c) 2019 Jiaxun Yang <jiaxun.yang@flygoat.com>
>> + */
>> +
>> +/dts-v1/;
>> +#include <ls1x.dtsi>
>> +
>> +/ {
>> + model = "Loongson LS1C300A";
>> + compatible = "loongson,ls1c300a";
>> +
>> +};
>> +
>> +&platintc4 {
>> + status = "okay";
>> +};
>> +
>> +&ehci0 {
>> + status = "okay";
>> +};
>> +
>> +&ohci0 {
>> + status = "okay";
>> +};
>> \ No newline at end of file
>> diff --git a/arch/mips/boot/dts/loongson/ls1x.dtsi b/arch/mips/boot/dts/loongson/ls1x.dtsi
>> new file mode 100644
>> index 000000000000..f808e4328fd8
>> --- /dev/null
>> +++ b/arch/mips/boot/dts/loongson/ls1x.dtsi
>> @@ -0,0 +1,117 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Copyright (c) 2019 Jiaxun Yang <jiaxun.yang@flygoat.com>
>> + */
>> +
>> +/dts-v1/;
>> +#include <dt-bindings/interrupt-controller/irq.h>
>> +
>> +
>> +/ {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> + cpus {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + cpu@0 {
>> + device_type = "cpu";
>> + reg = <0>;
> Needs a (documented) compatible string.
>
>
>
>> + };
>> +
>> + ehci0: usb@1fe20000 {
>> + compatible = "generic-ehci";
> It would be better to add a chip specific compatible here. Most all
> USB controllers have some quirks.
Should it be documented?
>
>> + reg = <0x1fe20000 0x100>;
>> + interrupt-parent = <&platintc1>;
>> + interrupts = <0 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + status = "disabled";
>> + };
>> +
>> + ohci0: usb@1fe28000 {
>> + compatible = "generic-ohci";
>> + reg = <0x1fe28000 0x100>;
>> + interrupt-parent = <&platintc1>;
>> + interrupts = <1 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + status = "disabled";
>> + };
> Don't you need a serial port or something for a console?
serial port is currently added by legacy pdev code. I'm going to add it
to devicetree after rework on clk driver being sent out.
Thanks.
--
Jiaxun Yang
prev parent reply other threads:[~2019-03-13 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 9:15 [PATCH 0/4] Loongson-32 initial DeviceTree support Jiaxun Yang
2019-03-12 9:15 ` [PATCH 1/4] MIPS: Loongson32: Remove ehci platform device Jiaxun Yang
2019-03-12 9:15 ` [PATCH 2/4] MIPS: Loongson32: Add DeviceTree support Jiaxun Yang
2019-03-12 9:15 ` [PATCH 3/4] MIPS: Loongson32: Kconfig merge CPU_LOONGSON1B&C Jiaxun Yang
2019-03-12 9:15 ` [PATCH 4/4] MIPS: Loongson32: dts: add ls1b & ls1c Jiaxun Yang
2019-03-12 12:28 ` Rob Herring
2019-03-13 1:08 ` Jiaxun Yang [this message]
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=04e55af9-4d2f-bf93-4b8a-a59735fa4cae@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--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®