From: Jacky Huang <ychuang3@nuvoton.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"olof@lixom.net" <olof@lixom.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"soc@kernel.org" <soc@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: dts: nuvoton: Add initial support for MA35D1
Date: Wed, 6 Apr 2022 17:25:42 +0800 [thread overview]
Message-ID: <ab89589f-6dd7-d4ff-635d-ff8dbd2d3e02@nuvoton.com> (raw)
In-Reply-To: <bba99b9d-6960-f6e8-0ee4-0b5fe8a5601d@linaro.org>
On 2022/4/6 下午 03:14, Krzysztof Kozlowski wrote:
> On 06/04/2022 04:58, Jacky Huang wrote:
>>>> diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
>>>> index 639e01a4d855..28e01442094f 100644
>>>> --- a/arch/arm64/boot/dts/Makefile
>>>> +++ b/arch/arm64/boot/dts/Makefile
>>>> @@ -30,3 +30,4 @@ subdir-y += synaptics
>>>> subdir-y += ti
>>>> subdir-y += toshiba
>>>> subdir-y += xilinx
>>>> +subdir-y += nuvoton
>>>> diff --git a/arch/arm64/boot/dts/nuvoton/Makefile b/arch/arm64/boot/dts/nuvoton/Makefile
>>>> new file mode 100644
>>>> index 000000000000..e1e0c466bf5e
>>>> --- /dev/null
>>>> +++ b/arch/arm64/boot/dts/nuvoton/Makefile
>>>> @@ -0,0 +1,2 @@
>>>> +# SPDX-License-Identifier: GPL-2.0
>>>> +dtb-$(CONFIG_ARCH_NUVOTON) += ma35d1-evb.dtb
>>> ARCH_NUVOTON does not exist.
>> I would add the following to end of arch/arm64/Kconfig.platforms,
> Don't add things at the end of files but rather in respective place
> without messing the order.
OK, I will put it to the right place in alphanumeric order.
It should be between ARCH_MXC and ARCH_QCOM.
>
>> and
>> add the
>> modification to this patch series.
>>
>> config ARCH_MA35D1
>> bool "Nuvoton MA35D1 SOC Family"
> We do not add options for specific SoCs, but for entire families, so
> ARCH_NUVOTON is correct.
Yes, I would like to modify it as the following:
config ARCH_NUVOTON
bool "Nuvoton SoC Family"
select PINCTRL
select PINCTRL_MA35D1
select PM
select GPIOLIB
select SOC_BUS
help
This enables support for Nuvoton MA35D1 ARMv8 SoC.
(Currently, we have MA35D1 only in the support list for arm64 SoC.).
>> select PINCTRL
>> select PINCTRL_MA35D1
>> select PM
>> select GPIOLIB
>> select SOC_BUS
>> select VIDEOMODE_HELPERS
>> select FB_MODE_HELPERS
>> help
>> This enables support for Nuvoton MA35D1 SOC Family.
>>
>>
>>>> diff --git a/arch/arm64/boot/dts/nuvoton/ma35d1-evb.dts b/arch/arm64/boot/dts/nuvoton/ma35d1-evb.dts
>>>> new file mode 100644
>>>> index 000000000000..38e4f734da0f
>>>> --- /dev/null
>>>> +++ b/arch/arm64/boot/dts/nuvoton/ma35d1-evb.dts
>>>> @@ -0,0 +1,23 @@
>>>> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>>>> +/*
>>>> + * Device Tree Source for MA35D1 Evaluation Board (EVB)
>>>> + *
>>>> + * Copyright (C) 2021 Nuvoton Technology Corp.
>>>> + */
>>>> +
>>>> +/dts-v1/;
>>>> +#include "ma35d1.dtsi"
>>>> +
>>>> +/ {
>>>> + model = "Nuvoton MA35D1-EVB";
>>>> +
>>>> + chosen {
>>>> + bootargs = "console=ttyS0,115200n8";
>>> No bootargs. "chosen", please.
>> OK, I would modify it as:
>>
>> chosen {
>> stdout-path = "serial0:115200n8";
>> };
>>
>>
>>>> + };
>>> You need compatible and bindings.
>> I will add the compatible here
>> compatible = "nuvoton,ma35d1-evb", "nuvoton,ma35d1"
>>
>> And, I should create a new binding file
>> Documentation/devicetree/bindings/arm/nuvoton.yaml to this patch series.
>> And the property would be:
>>
>> properties:
>> compatible:
>> description: Nuvoton MA35D1-EVB
>> items:
>> - const: nuvoton,ma35d1-evb
>> - const: nuvoton,ma35d1
>>
>>
>> Is it OK?
> Yes
>
>
>
> Best regards,
> Krzysztof
Thanks for your review.
Sincerely,
Jacky
next prev parent reply other threads:[~2022-04-06 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 9:19 [PATCH 0/3] Add initial support for MA35D1 SoC Jacky Huang
2022-03-07 9:19 ` [PATCH 1/3] dt-bindings: clock: add binding for MA35D1 clock controller Jacky Huang
2022-03-07 10:21 ` Krzysztof Kozlowski
2022-03-08 4:15 ` MS10 YCHuang3
2022-03-07 9:19 ` [PATCH 2/3] dt-bindings: clock: Document MA35D1 clock controller bindings Jacky Huang
2022-03-07 10:21 ` Krzysztof Kozlowski
2022-03-08 1:07 ` Rob Herring
2022-03-09 3:31 ` MS10 YCHuang3
2022-03-07 9:19 ` [PATCH 3/3] arm64: dts: nuvoton: Add initial support for MA35D1 Jacky Huang
2022-03-07 10:25 ` Krzysztof Kozlowski
2022-04-06 2:58 ` Jacky Huang
2022-04-06 7:14 ` Krzysztof Kozlowski
2022-04-06 9:25 ` Jacky Huang [this message]
2022-04-06 9:40 ` Arnd Bergmann
2022-04-07 4:17 ` Jacky Huang
2022-04-06 7:43 ` Arnd Bergmann
2022-04-07 4:07 ` Jacky Huang
2022-03-31 2:42 [PATCH 0/3] Add initial support for MA35D1 SoC Jacky Huang
2022-03-31 2:42 ` [PATCH 3/3] arm64: dts: nuvoton: Add initial support for MA35D1 Jacky Huang
2022-03-31 6:32 ` Krzysztof Kozlowski
[not found] ` <20220401233422.58670C2BBE4@smtp.kernel.org>
2022-04-02 9:55 ` Krzysztof Kozlowski
2022-04-06 2:11 ` Jacky Huang
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=ab89589f-6dd7-d4ff-635d-ff8dbd2d3e02@nuvoton.com \
--to=ychuang3@nuvoton.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@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®