From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 01/11] ASoC: dt-bindings: renesas,fsi: add support multiple clocks
Date: Tue, 9 Jun 2026 10:17:22 +0200 [thread overview]
Message-ID: <6103e3fc-4b27-47b5-aee9-8b481759eb65@kernel.org> (raw)
In-Reply-To: <CAABR9nF6uhEyCo-6cekhKwfm3zkqjXCpj2O8C8Xk=2Frw0arRg@mail.gmail.com>
On 09/06/2026 10:11, Bui Duc Phuc wrote:
> Hi Krzysztof,
>
> Thank you for your reviews.
>
>>> + properties:
>>> + clock-names:
>>> + minItems: 2
>>> + uniqueItems: true
>>
>> You don't need this, it's by default.
>>
>
> Could you clarify which part you are referring to?
> Are you referring to the "uniqueItems: true" property or another
> constraint in this block?
The uniqueItems should not be needed.
>
>
>>> + items:
>>> + - const: fck
>>> + - const: spu
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>> + - enum: [icka, ickb, diva, divb, xcka, xckb]
>>
>> Are all optional in the board design? I cannot find answers to that in
>> commit msg, but it is important - you need to explain WHY you are doing
>> this and WHY such different way.
>>
>
> For r8a7740, "fck" and "spu" are required. The SPU clock must be enabled
> to access the FSI registers because the FSI block is located behind the
> SPU bus.
> The remaining clocks (icka/b, diva/b and xcka/b) are not always required.
> Their presence depends on the clock topology used by each FSI port.
> In the previous discussion I described the supported clock configurations:
> https://lore.kernel.org/all/CAABR9nEhOTz1-0NmCMTbz=-+782Pto0yovSQhBXrXqhLwMg80Q@mail.gmail.com/
This commit must stand on its own, thus here you must explain that.
> The hardware supports several valid configurations, for example:
> - FSIA/FSIB slave: only fck and spu are needed.
> - FSI master using an internal clock: ickx and divx are used.
> - FSI master using an external clock: ickx and xckx are used.
>
> Therefore, while fck and spu are mandatory on r8a7740, the other clocks
> depend on the selected master/slave configuration and clock source, so
> not all of them are expected to be present in every DT.
Explain that in the commit msg and be explicit that all these further
clocks are optional.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-09 8:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 1:30 [PATCH v5 00/11] ASoC: renesas: fsi: Fix system hang by adding SPU clock phucduc.bui
2026-06-09 1:30 ` [PATCH v5 01/11] ASoC: dt-bindings: renesas,fsi: add support multiple clocks phucduc.bui
2026-06-09 1:41 ` sashiko-bot
2026-06-09 6:54 ` Krzysztof Kozlowski
2026-06-09 8:11 ` Bui Duc Phuc
2026-06-09 8:17 ` Krzysztof Kozlowski [this message]
2026-06-09 8:42 ` Bui Duc Phuc
2026-06-09 8:54 ` Krzysztof Kozlowski
2026-06-09 9:05 ` Bui Duc Phuc
2026-06-09 1:30 ` [PATCH v5 02/11] ARM: dts: renesas: r8a7740: Add clocks for FSI phucduc.bui
2026-06-09 1:30 ` [PATCH v5 03/11] ASoC: renesas: fsi: Fix trigger stop ordering phucduc.bui
2026-06-09 1:43 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 04/11] ASoC: renesas: fsi: Move fsi_stream_is_working() phucduc.bui
2026-06-09 1:44 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 05/11] ASoC: renesas: fsi: Fix register access from in-flight IRQ after shutdown phucduc.bui
2026-06-09 1:59 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 06/11] ASoC: renesas: fsi: Move fsi_clk_init() phucduc.bui
2026-06-09 1:46 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 07/11] ASoC: renesas: fsi: Use devm_clk_get_optional() for optional clocks phucduc.bui
2026-06-09 1:31 ` [PATCH v5 08/11] ASoC: renesas: fsi: refactor clock initialization phucduc.bui
2026-06-09 1:43 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 09/11] ASoC: renesas: fsi: Add SPU clock support phucduc.bui
2026-06-09 1:47 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 10/11] ASoC: renesas: fsi: add fsi_clk_prepare/unprepare() phucduc.bui
2026-06-09 1:51 ` sashiko-bot
2026-06-09 1:31 ` [PATCH v5 11/11] ASoC: renesas: fsi: Add SPU clock control in hw_startup/shutdown phucduc.bui
2026-06-09 1:50 ` sashiko-bot
2026-06-09 6:57 ` [PATCH v5 00/11] ASoC: renesas: fsi: Fix system hang by adding SPU clock Kuninori Morimoto
2026-06-09 9:49 ` Bui Duc Phuc
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=6103e3fc-4b27-47b5-aee9-8b481759eb65@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=perex@perex.cz \
--cc=phucduc.bui@gmail.com \
--cc=robh@kernel.org \
--cc=tiwai@suse.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