[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0c84a8ab-5b92-49a3-aa14-08aaff856445@linaro.org>
Date: Fri, 22 Mar 2024 07:17:48 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Frank Li <Frank.li@....com>, Rob Herring <robh@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Shengjiu Wang <shengjiu.wang@....com>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..."
<linux-sound@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] ASoC: dt-bindings: fsl-esai: Convert fsl,esai.txt to
yaml
On 21/03/2024 17:19, Frank Li wrote:
>>> + clocks:
>>> + minItems: 3
>>> + maxItems: 4
>>> +
>>> + clock-names:
>>> + minItems: 3
>>> + description: |
>>> + core: The core clock used to access registers.
>>> + extal: The esai baud clock for esai controller used to
>>> + derive HCK, SCK and FS.
>>> + fsys: The system clock derived from ahb clock used to
>>> + derive HCK, SCK and FS.
>>> + spba: The spba clock is required when ESAI is placed as a
>>> + bus slave of the Shared Peripheral Bus and when two
>>> + or more bus masters (CPU, DMA or DSP) try to access
>>> + it. This property is optional depending on the SoC
>>> + design.
>>
>> This description should be split into each items entry below.
Description of clocks goes to clocks. Here, just items with 'const' items.
There are plenty of examples for this, most of complex devices define
clocks that way.
Best regards,
Krzysztof
Powered by blists - more mailing lists