From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johnson Wang <johnson.wang@mediatek.com>,
cw00.choi@samsung.com, krzk+dt@kernel.org, robh+dt@kernel.org,
kyungmin.park@samsung.com
Cc: khilman@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, jia-wei.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2 1/2] dt-bindings: devfreq: mediatek: Add mtk cci devfreq dt-bindings
Date: Fri, 8 Apr 2022 10:17:26 +0200 [thread overview]
Message-ID: <855d7daa-45d1-d6d8-32bd-51778cf58392@linaro.org> (raw)
In-Reply-To: <20220408052150.22536-2-johnson.wang@mediatek.com>
On 08/04/2022 07:21, Johnson Wang wrote:
> Add devicetree binding of mtk cci devfreq on MediaTek SoC.
>
Thank you for your patch. There is something to discuss/improve.
> Signed-off-by: Johnson Wang <johnson.wang@mediatek.com>
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> ---
> .../devicetree/bindings/devfreq/mtk-cci.yaml | 72 +++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/devfreq/mtk-cci.yaml
Filename with vendor prefix, so something like:
mediatek,cci.yaml
Also please put it in the "interconnect" directory.
>
> diff --git a/Documentation/devicetree/bindings/devfreq/mtk-cci.yaml b/Documentation/devicetree/bindings/devfreq/mtk-cci.yaml
> new file mode 100644
> index 000000000000..ef4ea951025c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/devfreq/mtk-cci.yaml
> @@ -0,0 +1,72 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/devfreq/mtk-cci.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek Cache Coherent Interconnect (CCI) frequency and voltage scaling
> +
> +maintainers:
> + - Jia-Wei Chang <jia-wei.chang@mediatek.com>
> +
> +description: |
> + MediaTek Cache Coherent Interconnect (CCI) uses the software devfreq module
Do not reference software implementation (devfreq).
> + to scale the clock frequency and adjust the voltage. MediaTek CCI shares
> + the same power supplies with CPU, so the scheduling involves with CPUfreq.
The same - cpufreq.
Instead, focus on the hardware, what do you describe here?
> +
> +properties:
> + compatible:
> + enum:
> + - mediatek,mt8183-cci
> + - mediatek,mt8186-cci
> +
> + clocks:
> + items:
> + - description:
> + The multiplexer for clock input of CPU cluster.
> + - description:
> + A parent of "cpu" clock which is used as an intermediate clock source
> + when the original CPU is under transition and not stable yet.
> +
> + clock-names:
> + items:
> + - const: cci
> + - const: intermediate
> +
> + operating-points-v2:
> + description:
> + For details, please refer to
> + Documentation/devicetree/bindings/opp/opp-v2.yaml
No need for description. Just "operating-points-v2: true".
"opp-table:true" could stay. My previous comment about its removal was a
wrong advice, because opp-table is used for a table being a children of
this device node.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-08 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 5:21 [PATCH v2 0/2] Introduce MediaTek CCI devfreq driver Johnson Wang
2022-04-08 5:21 ` [PATCH v2 1/2] dt-bindings: devfreq: mediatek: Add mtk cci devfreq dt-bindings Johnson Wang
2022-04-08 8:17 ` Krzysztof Kozlowski [this message]
2022-04-11 12:10 ` Johnson Wang
2022-04-12 9:17 ` Krzysztof Kozlowski
2022-04-13 20:54 ` Chanwoo Choi
2022-04-14 21:55 ` Kevin Hilman
2022-04-08 5:21 ` [PATCH v2 2/2] PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver Johnson Wang
2022-04-08 8:21 ` Krzysztof Kozlowski
2022-04-12 8:39 ` Johnson Wang
2022-04-12 8:51 ` Krzysztof Kozlowski
2022-04-08 11:51 ` AngeloGioacchino Del Regno
2022-04-14 5:19 ` Johnson Wang
2022-04-13 21:43 ` Chanwoo Choi
2022-04-15 12:46 ` Johnson Wang
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=855d7daa-45d1-d6d8-32bd-51778cf58392@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jia-wei.chang@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=khilman@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@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).