devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Qiu <william.qiu@starfivetech.com>
To: Rob Herring <robh@kernel.org>
Cc: <linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
	<linux-mmc@vger.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: Tue, 21 Feb 2023 10:44:02 +0800	[thread overview]
Message-ID: <348796cc-72d9-4dcf-9f09-4c2aa55cb858@starfivetech.com> (raw)
In-Reply-To: <20230220234335.GA615198-robh@kernel.org>



On 2023/2/21 7:43, Rob Herring wrote:
> On Wed, Feb 15, 2023 at 07:32:49PM +0800, William Qiu wrote:
>> Add documentation to describe StarFive System Controller Registers.
>> 
>> Signed-off-by: William Qiu <william.qiu@starfivetech.com>
>> ---
>>  .../bindings/soc/starfive/jh7110-syscon.yaml  | 51 +++++++++++++++++++
>>  MAINTAINERS                                   |  5 ++
>>  2 files changed, 56 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/soc/starfive/jh7110-syscon.yaml
>> 
>> diff --git a/Documentation/devicetree/bindings/soc/starfive/jh7110-syscon.yaml b/Documentation/devicetree/bindings/soc/starfive/jh7110-syscon.yaml
>> new file mode 100644
>> index 000000000000..fa4d8522a454
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/starfive/jh7110-syscon.yaml
>> @@ -0,0 +1,51 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/soc/starfive/jh7110-syscon.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: StarFive JH7110 SoC system controller
>> +
>> +maintainers:
>> +  - William Qiu <william.qiu@starfivetech.com>
>> +
>> +description: |
>> +  The StarFive JH7110 SoC system controller provides register information such
>> +  as offset, mask and shift to configure related modules such as MMC and PCIe.
>> +
>> +properties:
>> +  compatible:
>> +    items:
>> +      - enum:
>> +          - starfive,jh7110-stg-syscon
>> +          - starfive,jh7110-sys-syscon
>> +          - starfive,jh7110-aon-syscon
> 
> Is 'syscon' really part of what the blocks are called? Is just 'stg', 
> 'sys' and 'aon' not unique enough?
> 
> Rob
Hi Rob,

In StarFive SoC, we do have syscrg/aoncrg/stgcrg, which is uesd to be the clock
controller, so 'syscon' is added to avoid confusion.

Best regards
William

  reply	other threads:[~2023-02-21  2:44 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
2023-02-16 10:32       ` Krzysztof Kozlowski
2023-02-20 23:43   ` Rob Herring
2023-02-21  2:44     ` William Qiu [this message]
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=348796cc-72d9-4dcf-9f09-4c2aa55cb858@starfivetech.com \
    --to=william.qiu@starfivetech.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jh80.chung@samsung.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh@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).