From: William Qiu <william.qiu@starfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-mmc@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] dt-bindings: syscon: Add StarFive syscon doc
Date: Thu, 16 Feb 2023 18:30:35 +0800 [thread overview]
Message-ID: <4b9edac8-20bf-be1c-6b32-69b7f7616ad5@starfivetech.com> (raw)
In-Reply-To: <41bcc545-6eda-6c30-c600-d97ef009abf2@linaro.org>
On 2023/2/16 18:23, Krzysztof Kozlowski wrote:
> On 15/02/2023 12:32, William Qiu wrote:
>> Add documentation to describe StarFive System Controller Registers.
>>
>> Signed-off-by: William Qiu <william.qiu@starfivetech.com>
>> ---
>
> Thank you for your patch. There is something to discuss/improve.
>
>> +properties:
>> + compatible:
>> + items:
>> + - enum:
>> + - starfive,jh7110-stg-syscon
>> + - starfive,jh7110-sys-syscon
>> + - starfive,jh7110-aon-syscon
>
> Maybe keep them ordered alphabetically?
>
I'm sorting by register address, or I can keep them ordered
alphabetically,which is better?
>> + - const: syscon
>> +
>> + reg:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + syscon@10240000 {
>> + compatible = "starfive,jh7110-stg-syscon", "syscon";
>> + reg = <0x10240000 0x1000>;
>> + };
>
> Keep only one example. All others are the same.
>
Will update in next version.
Thanks for taking times to review this patch series.
Best regards
William
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-02-16 10:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 11:32 [PATCH v4 0/4] StarFive's SDIO/eMMC driver support William Qiu
2023-02-15 11:32 ` [PATCH v4 1/4] dt-bindings: mmc: Add StarFive MMC module William Qiu
2023-02-15 11:59 ` Shengyu Qu
2023-02-15 12:08 ` William Qiu
2023-02-15 16:49 ` Shengyu Qu
[not found] ` <202302160545.31G5jiuf087662@SH1-CSMTP-DB111.sundns.com>
2023-02-16 5:51 ` William Qiu
2023-02-16 10:21 ` Krzysztof Kozlowski
2023-02-16 10:31 ` Conor Dooley
2023-02-16 10:39 ` Shengyu Qu
[not found] ` <a7b51602-3ba4-d822-4da0-f6e51e7dddea@outlook.com>
2023-02-15 12:03 ` Shengyu Qu
2023-02-15 11:32 ` [PATCH v4 2/4] mmc: starfive: Add sdio/emmc driver support William Qiu
2023-03-27 16:01 ` Shengyu Qu
2023-03-28 16:08 ` Shengyu Qu
2023-03-31 9:33 ` William Qiu
2023-04-10 18:04 ` Shengyu Qu
2023-04-11 2:54 ` William Qiu
2023-02-15 11:32 ` [PATCH v4 3/4] riscv: dts: starfive: Add mmc node William Qiu
2023-02-15 12:12 ` Emil Renner Berthing
2023-02-15 12:22 ` Emil Renner Berthing
2023-02-15 12:26 ` William Qiu
2023-08-05 13:14 ` Emil Renner Berthing
2023-08-07 1:51 ` William Qiu
2023-02-15 12:26 ` William Qiu
2023-02-15 11:32 ` [PATCH v4 4/4] dt-bindings: syscon: Add StarFive syscon doc William Qiu
2023-02-16 10:23 ` Krzysztof Kozlowski
2023-02-16 10:29 ` Conor Dooley
2023-02-16 10:31 ` Krzysztof Kozlowski
2023-03-06 14:04 ` Conor Dooley
2023-03-07 1:43 ` William Qiu
2023-02-16 10:30 ` William Qiu [this message]
2023-02-16 10:32 ` Krzysztof Kozlowski
2023-02-20 23:43 ` Rob Herring
2023-02-21 2:44 ` William Qiu
2023-02-27 22:29 ` Rob Herring
2023-02-28 9:05 ` William Qiu
2023-02-28 10:37 ` Krzysztof Kozlowski
2023-02-28 11:02 ` Emil Renner Berthing
2023-02-28 11:28 ` Krzysztof Kozlowski
2023-02-28 14:59 ` Emil Renner Berthing
2023-02-28 16:59 ` Krzysztof Kozlowski
2023-02-28 17:31 ` Emil Renner Berthing
2023-02-28 18:06 ` Conor Dooley
2023-02-28 11:08 ` Conor Dooley
2023-02-15 12:37 ` [PATCH v4 0/4] StarFive's SDIO/eMMC driver support Ulf Hansson
2023-02-27 7:47 ` William Qiu
2023-02-27 14:53 ` Ulf Hansson
2023-02-28 5:56 ` William Qiu
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=4b9edac8-20bf-be1c-6b32-69b7f7616ad5@starfivetech.com \
--to=william.qiu@starfivetech.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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).