From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] dt-bindings: soc: socionext: Add UniPhier system controller
Date: Thu, 1 Dec 2022 17:29:39 +0900 [thread overview]
Message-ID: <ba9fac4e-bfb1-3b8e-ad81-5d8109529d43@socionext.com> (raw)
In-Reply-To: <cb76a56f-6492-5209-be30-e31aa075ce8e@linaro.org>
On 2022/12/01 0:24, Krzysztof Kozlowski wrote:
> On 30/11/2022 09:59, Kunihiko Hayashi wrote:
>>>> +maintainers:
>>>> + - Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>>>> +
>>>> +description: |+
>>>> + System controller implemented on Socionext UniPhier SoCs has multiple
>>>> + functions such as clock control, reset control, internal watchdog
>>>> timer,
>>>> + thermal management, and so on.
>>>> +
>>>> +properties:
>>>> + compatible:
>>>> + items:
>>>> + - enum:
>>>> + - socionext,uniphier-ld4-sysctrl
>>>> + - socionext,uniphier-pro4-sysctrl
>>>> + - socionext,uniphier-pro5-sysctrl
>>>> + - socionext,uniphier-pxs2-sysctrl
>>>> + - socionext,uniphier-ld6b-sysctrl
>>>> + - socionext,uniphier-sld8-sysctrl
>>>> + - socionext,uniphier-ld11-sysctrl
>>>> + - socionext,uniphier-ld20-sysctrl
>>>> + - socionext,uniphier-pxs3-sysctrl
>>>> + - socionext,uniphier-nx1-sysctrl
>>>
>>> All of them can have children or only some?
>>
>> In case of this system controller,
>> all SoCs has clock-controller, reset-controller and watchdog.
>>
>> However, some SoCs don't have thermal-sensor and
>> their register addresses are reserved.
>
> OK
>
>>
>>>> + - socionext,uniphier-sysctrl
>
> What about this one? What SoC is this? Looks too generic.
It's the same one as soc-glue, so it should be placed as follows.
items:
- enum:
- ...
- ...
- const: socionext,uniphier-sysctrl
However, currently it is no use for now. I'll drop it.
Thank you,
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2022-12-01 8:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 10:35 [PATCH 0/8] dt-bidnings: soc: Introduce UniPhier miscelaneous register blocks Kunihiko Hayashi
2022-11-29 10:35 ` [PATCH 1/8] dt-bindings: soc: socionext: Add UniPhier system controller Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-11-29 14:41 ` Krzysztof Kozlowski
2022-11-30 8:59 ` Kunihiko Hayashi
2022-11-30 15:24 ` Krzysztof Kozlowski
2022-12-01 8:29 ` Kunihiko Hayashi [this message]
2022-11-29 10:35 ` [PATCH 2/8] dt-bindings: soc: socionext: Add UniPhier SoC-glue logic Kunihiko Hayashi
2022-11-29 14:43 ` Krzysztof Kozlowski
2022-11-30 8:59 ` Kunihiko Hayashi
2022-11-30 15:27 ` Krzysztof Kozlowski
2022-12-01 8:29 ` Kunihiko Hayashi
2022-11-29 10:35 ` [PATCH 3/8] dt-bindings: soc: socionext: Add UniPhier peripheral block Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-11-29 14:46 ` Krzysztof Kozlowski
2022-11-30 9:00 ` Kunihiko Hayashi
2022-11-29 10:35 ` [PATCH 4/8] dt-bindings: soc: socionext: Add UniPhier media I/O block Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-11-29 10:35 ` [PATCH 5/8] dt-bindings: soc: socionext: Add UniPhier SD interface block Kunihiko Hayashi
2022-11-29 10:35 ` [PATCH 6/8] dt-bindings: soc: socionext: Add UniPhier ADAMV block Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-11-29 10:35 ` [PATCH 7/8] dt-bindings: soc: socionext: Add UniPhier DWC3 USB glue layer Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-11-29 14:52 ` Krzysztof Kozlowski
2022-11-30 9:00 ` Kunihiko Hayashi
2022-11-30 15:32 ` Krzysztof Kozlowski
2022-12-01 8:30 ` Kunihiko Hayashi
2022-11-29 10:35 ` [PATCH 8/8] dt-bindings: soc: socionext: Add UniPhier AHCI " Kunihiko Hayashi
2022-11-29 13:32 ` Rob Herring
2022-12-01 9:30 ` Kunihiko Hayashi
2022-12-02 12:08 ` Krzysztof Kozlowski
2022-12-02 12:14 ` Kunihiko Hayashi
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=ba9fac4e-bfb1-3b8e-ad81-5d8109529d43@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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).