From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Phil Edworthy <phil.edworthy@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: renesas: Document Renesas RZ/V2M System Configuration
Date: Mon, 14 Nov 2022 17:51:04 +0100 [thread overview]
Message-ID: <a3e5d695-535e-8587-6ccc-4c65fbeba278@linaro.org> (raw)
In-Reply-To: <OS0PR01MB59226FC7CA88208AB5C0AED586059@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 14/11/2022 17:44, Biju Das wrote:
>>>>> If the hardware manual said this is called "foo-whatever-name" or
>>>>> "rz85736dfnx2", you would use it as well?
>>>>>
>>>>> Node names should be generic.
>>>
>>> I got the following feedback from LSI team.
>>>
>>> *The reason why we use "configuration" and not "controller" is the
>>> possibility that users might take it to mean "control" of system
>>> operation (product operation). This unit determines how the whole LSI
>> configure to operate LSI, so we use "configuration" for this IP name.
>>>
>>> As per this it is not a controller. It is a Configuration IP.
>>>
>>> What should be generic node name for system configuration IP?
>>
>> Then it's closer to chipid and should be in hwinfo?
>
> You mean, sys: hwinfo@a3f03000 instead of sys: system-configuration@a3f03000 ??
Rather be put in hwinfo directory. Typical name is "chipid", but I don't
know if your device is a chipid.
>
> Also the same IP block is present on rz/v2ma as well?
>
> Shall I use the same file renesas,rzv2m-sys.yaml for both r9a09g011-sys and r9a09g055-sys?
>
>>
>> Anyway, you wrote in bindings description: "performs system control", so what
>> can I say?
>
> SYS functional description is as follows.
>
> The SYS controls the overall configuration of the chip, such as
Exactly, it controls, so it is a controller... Anyway, do not introduce
your own names, but use something generic. There is no single reference
of "system-configuration".
>
> ● Bank address settings for DMAC
> ● Bank address settings of the units for ICB> ● ETHER AxCACHE[1] (C bit) control function
> ● RAMA initialization control
> ● MD[7:0] pin monitoring
> ● LSI version register
> ● General-purpose 32-bit readable/writable registers
> ● Observability counting stop control for ICB
> ● WDT counter stop control
> ● Reading of the temperature sensor reference value
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-14 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 16:21 [PATCH v2 0/3] Add SoC identification support for RZ/V2M Biju Das
2022-11-10 16:21 ` [PATCH v2 1/3] dt-bindings: arm: renesas: Document Renesas RZ/V2M System Configuration Biju Das
2022-11-11 8:34 ` Krzysztof Kozlowski
2022-11-11 9:06 ` Biju Das
2022-11-11 10:51 ` Krzysztof Kozlowski
2022-11-11 11:16 ` Biju Das
2022-11-14 16:18 ` Biju Das
2022-11-14 16:32 ` Krzysztof Kozlowski
2022-11-14 16:44 ` Biju Das
2022-11-14 16:51 ` Krzysztof Kozlowski [this message]
2022-11-14 17:05 ` Biju Das
2022-11-14 19:12 ` Geert Uytterhoeven
2022-11-14 19:21 ` Biju Das
2022-11-15 8:08 ` Geert Uytterhoeven
2022-11-15 11:19 ` Biju Das
2022-11-15 11:24 ` Geert Uytterhoeven
2022-11-15 11:27 ` Biju Das
2022-11-16 8:14 ` Biju Das
2022-11-16 8:20 ` Geert Uytterhoeven
2022-11-10 16:21 ` [PATCH v2 3/3] arm64: dts: renesas: r9a09g011: Add system configuration node Biju Das
2022-11-11 8:34 ` Krzysztof Kozlowski
2022-11-11 9:10 ` Biju Das
2022-11-11 10:50 ` Krzysztof Kozlowski
2022-11-11 11:25 ` Biju Das
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=a3e5d695-535e-8587-6ccc-4c65fbeba278@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=phil.edworthy@renesas.com \
--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