[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad7f3328-6eb7-4b32-9316-b0c79fd2753e@linaro.org>
Date: Mon, 6 May 2024 22:08:00 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jonas Karlman <jonas@...boo.se>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Heiko Stuebner <heiko@...ech.de>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Lee Jones <lee@...nel.org>,
Chris Zhong <zyw@...k-chips.com>, Zhang Qing <zhangqing@...k-chips.com>
Subject: Re: [PATCH 2/4] dt-bindings: mfd: rk809: Add audio codec properties
On 06/05/2024 18:14, Jonas Karlman wrote:
>>
>>> +
>>> + codec:
>>> + description: |
>>
>> Do not need '|' unless you need to preserve formatting.
>>
>>> + The child node for the codec to hold additional properties. If no
>>> + additional properties are required for the codec, this node can be
>>> + omitted.
>>
>> That's useless description. Describe hardware, not syntax. This must say
>> what this node represents.
>>
>> Anyway drop it. You do not have any resources there, so put properties
>> in top level.
>
> This just tries to follow the rockchip,rk817 binding, not fully sure
> about the reasoning behind this node in the the rk817 binding.
>
> RK809/RK817 are very similar and their schema files could possible be
> merged.
That binding was a conversion from something older, so it might not be
in good shape. At least new binding should follow usual rules/style.
Best regards,
Krzysztof
Powered by blists - more mailing lists