[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc66e8ef-987e-48e2-890e-418cd582e7df@linaro.org>
Date: Tue, 23 Jan 2024 08:41:01 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tim Lunn <tim@...thertop.org>, linux-rockchip@...ts.infradead.org,
conor.dooley@...rochip.com, robh+dt@...nel.org, devicetree@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org, Chris Zhong <zyw@...k-chips.com>,
Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Lee Jones <lee@...nel.org>, Zhang Qing <zhangqing@...k-chips.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] dt-bindings: rockchip: rk809: Document audio codec
clock
On 23/01/2024 05:25, Tim Lunn wrote:
>
> On 1/22/24 19:16, Krzysztof Kozlowski wrote:
>> On 20/01/2024 14:55, Tim Lunn wrote:
>>> Rockchip RK809 shares the same audio codec block as the rk817 mfd, and
>> What rk817 has anything to do with this?
>
> The existing codec driver in linux already is from the rk817 and thus
> called rk817, however
> that driver is also compatible with the codec in rk809.
Sure, but how is this any related? Your commit msg says two independent
things:
1. Something shares same audio codec block
2. Add clocks
I don't see how they are anyhow related to each other, IOW, how from (1)
comes (2).
Best regards,
Krzysztof
Powered by blists - more mailing lists