From: William Qiu <william.qiu@starfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<devicetree@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [RESEND v1 2/2] riscv: dts: starfive: Add spi node for JH7110 SoC
Date: Wed, 5 Jul 2023 11:40:43 +0800 [thread overview]
Message-ID: <1e9dedc6-dee3-b65d-2823-0468fcb13193@starfivetech.com> (raw)
In-Reply-To: <7f3b600d-d315-22d6-b987-eabfe1b04fdf@linaro.org>
On 2023/7/4 17:39, Krzysztof Kozlowski wrote:
> On 04/07/2023 11:22, William Qiu wrote:
>> Add spi node for JH7110 SoC.
>>
>> Co-developed-by: Xingyu Wu <xingyu.wu@starfivetech.com>
>
> Missing SoB.
>
It looks like that drop it is the best solution.
>> Signed-off-by: William Qiu <william.qiu@starfivetech.com>
>> ---
>> .../jh7110-starfive-visionfive-2.dtsi | 52 ++++++++++
>> arch/riscv/boot/dts/starfive/jh7110.dtsi | 98 +++++++++++++++++++
>> 2 files changed, 150 insertions(+)
>>
>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> index 2a6d81609284..a066d2e399c4 100644
>> --- a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> +++ b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> @@ -126,6 +126,20 @@ &i2c6 {
>> status = "okay";
>> };
>>
>> +&spi0 {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&spi0_pins>;
>> + status = "okay";
>> +
>> + spi_dev0: spi@0 {
>> + compatible = "st,m25p80";
>> + pl022,com-mode = <1>;
>> + spi-max-frequency = <10000000>;
>> + reg = <0>;
>
> reg is always following compatible, not somewhere deep in properties.
>
Will update.
>> + status = "okay";
>
> okay is by default
>
Will drop.
>> + };
>> +};
>
>
> Best regards,
> Krzysztof
>
Thanks for taking time to review this patch series.
prev parent reply other threads:[~2023-07-05 3:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 9:21 [RESEND v1 0/2] Add SPI module for StarFive JH7110 SoC William Qiu
2023-07-04 9:21 ` [RESEND v1 1/2] dt-binding: spi: constrain minItems of clocks and clock-names William Qiu
2023-07-04 9:38 ` Krzysztof Kozlowski
2023-07-05 3:37 ` William Qiu
2023-07-05 6:00 ` Krzysztof Kozlowski
2023-07-05 6:20 ` William Qiu
2023-07-04 9:22 ` [RESEND v1 2/2] riscv: dts: starfive: Add spi node for JH7110 SoC William Qiu
2023-07-04 9:39 ` Krzysztof Kozlowski
2023-07-04 12:26 ` Mark Brown
2023-07-04 12:27 ` Krzysztof Kozlowski
2023-07-04 13:16 ` Mark Brown
2023-07-04 13:21 ` Krzysztof Kozlowski
2023-07-04 14:13 ` Mark Brown
2023-07-04 16:41 ` Conor Dooley
2023-07-05 3:40 ` William Qiu [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=1e9dedc6-dee3-b65d-2823-0468fcb13193@starfivetech.com \
--to=william.qiu@starfivetech.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--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).