| Message ID | 20240614-topic-amlogic-upstream-bindings-fixes-audio-snd-card-v1-2-9f57d9e01834@linaro.org (mailing list archive) |
|---|---|
| State | RFC |
| Headers | show |
| Series | ASoC: dt-bindings: amlogic-sound-cards: document clocks and clock-names | expand |
diff --git a/Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml b/Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml index 0ecdaf7190e9..d29dbca9ccc9 100644 --- a/Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml +++ b/Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml @@ -27,6 +27,18 @@ properties: A list off component DAPM widget. Each entry is a pair of strings, the first being the widget type, the second being the widget name + clocks: + maxItems: 3 + description: + Base PLL clocks of audio susbsytem, used to configure base clock + frequencies for different audio use-cases. + + clock-names: + items: + - const: mpll0 + - const: mpll1 + - const: mpll2 + patternProperties: "^dai-link-[0-9]+$": type: object
The sound card design is based on 3 reference PLL frequencies that are the root of all clock rates calculations. Today, those 3 frequencies are specified in DT via assigned-clocks, because they correspond to the basic audio use-case. It makes no sense to setup clock rates for a sound card without referencing the clocks for the sound card, mainly because at some point more complex audio use cases will be supported and those root rates would need to change. To solve this situation, let's legitimize the presence of assigned-clocks in the sound card by documenting those clocks, as it describes a true dependency of the sound card and paths the way of more complex audio uses-cases involving those root frequencies. Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org> --- .../devicetree/bindings/sound/amlogic,gx-sound-card.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+)