From: Jerome Brunet <jbrunet@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jian Hu <jian.hu@amlogic.com>,
Xianwei Zhao <xianwei.zhao@amlogic.com>,
Chuan Liu <chuan.liu@amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
robh+dt <robh+dt@kernel.org>, Rob Herring <robh@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
linux-amlogic <linux-amlogic@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 2/5] dt-bindings: clock: add Amlogic T7 SCMI clock controller
Date: Tue, 09 Dec 2025 11:16:52 +0100 [thread overview]
Message-ID: <1jy0ncvu23.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <4f5ec838-f8d6-4c3b-94f2-b2a60cfe64ec@kernel.org> (Krzysztof Kozlowski's message of "Tue, 9 Dec 2025 07:01:44 +0100")
On Tue 09 Dec 2025 at 07:01, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On 08/12/2025 09:40, Jian Hu wrote:
>> Hi, Krzysztof
>>
>>
>> Thans for your review.
>>
>> On 12/8/2025 2:17 PM, Krzysztof Kozlowski wrote:
>>> [ EXTERNAL EMAIL ]
>>>
>>> On Thu, Dec 04, 2025 at 01:36:31PM +0800, Jian Hu wrote:
>>>> Add DT bindings for the SCMI clock controller of the Amlogic T7 SoC family.
>>>>
>>>> Signed-off-by: Jian Hu <jian.hu@amlogic.com>
>>>> Acked-by: Rob Herring (Arm) <robh@kernel.org>
>>>> ---
>>>> include/dt-bindings/clock/amlogic,t7-scmi.h | 47 +++++++++++++++++++++
>>>> 1 file changed, 47 insertions(+)
>>>> create mode 100644 include/dt-bindings/clock/amlogic,t7-scmi.h
>>>>
>>> Where is any binding doc for this? Why is this a separate patch?
>>
>>
>> The ARM SCMI device tree binding specification is located at
>> ./Documentation/devicetree/bindings/firmware/arm,scmi.yaml.
>
> Then git grep for the file name - there is no such compatible. Are you
> sure you follow writing bindings doc?
>
> Think how are you going to use these values. You will have phandle, yes?
> To some controller, yes? Which one?
For the C3 (I believe the T7 is the same), the compatible being used is
"arm,scmi-smc". It is a generic one documented here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/firmware/arm,scmi.yaml?h=v6.18#n202
The phandle used is a subnode of that, to clock protocol:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi?h=v6.18#n116
Same things is done on imx, stm and rockchip platforms from what I can
see.
Jian is just adding the arbitrary IDs used to identify the clocks in the
FW. I don't think there is anything out of the ordirnary here.
Is there something else Rob and I missed reviewing this ?
>
>>
>> Certain secure clocks on the T7 rely on the ARM SCMI driver stack, which
>> is officially supported by ARM.
>>
>> The kernel-side SCMI client implementation resides in
>> ./drivers/firmware/arm_scmi/.
>>
>> To enable ARM SCMI on T7, three components are needed:
>>
>> - Kernel-side definition of ARM SCMI clock indices (this patch addresses
>> this component);
>> - SCMI server implementation in the ARM Trusted Firmware (ATF) running
>> at Exception Level 3 (EL3), which has been integrated into the bootloader;
>> - Device Tree Source (DTS) configuration for ARM SCMI clock nodes (the
>> DTS changes will be submitted after the T7 clock driver patches are
>> merged upstream).
>
> So silently you keep the users hidden? No, I want to see the users.
>
Is there a new requirement to submit the DTS file changes along with the
driver changes now ?
This has never been case before, especially since the changes are merged
through different trees.
>
> Best regards,
> Krzysztof
--
Jerome
next prev parent reply other threads:[~2025-12-09 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 5:36 [PATCH v6 0/5] add support for T7 family clock controller Jian Hu
2025-12-04 5:36 ` [PATCH v6 1/5] dt-bindings: clock: add Amlogic T7 PLL " Jian Hu
2025-12-04 5:36 ` [PATCH v6 2/5] dt-bindings: clock: add Amlogic T7 SCMI " Jian Hu
2025-12-08 6:17 ` Krzysztof Kozlowski
2025-12-08 8:40 ` Jian Hu
2025-12-09 6:01 ` Krzysztof Kozlowski
2025-12-09 10:16 ` Jerome Brunet [this message]
2025-12-11 6:16 ` Krzysztof Kozlowski
2025-12-11 8:30 ` Jerome Brunet
2025-12-04 5:36 ` [PATCH v6 3/5] dt-bindings: clock: add Amlogic T7 peripherals " Jian Hu
2025-12-04 5:36 ` [PATCH v6 4/5] clk: meson: t7: add support for the T7 SoC PLL clock Jian Hu
2025-12-06 3:18 ` kernel test robot
2025-12-04 5:36 ` [PATCH v6 5/5] clk: meson: t7: add t7 clock peripherals controller driver Jian Hu
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=1jy0ncvu23.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=chuan.liu@amlogic.com \
--cc=devicetree@vger.kernel.org \
--cc=jian.hu@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=xianwei.zhao@amlogic.com \
/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