From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tim Lunn <tim@feathertop.org>,
linux-rockchip@lists.infradead.org, conor.dooley@microchip.com,
robh+dt@kernel.org, devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lee Jones <lee@kernel.org>, Zhang Qing <zhangqing@rock-chips.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] dt-bindings: rockchip: rk809: Document audio codec clock
Date: Tue, 23 Jan 2024 08:41:01 +0100 [thread overview]
Message-ID: <dc66e8ef-987e-48e2-890e-418cd582e7df@linaro.org> (raw)
In-Reply-To: <9e5cace9-8725-45a4-a55f-f996a561c9a4@feathertop.org>
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
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2024-01-23 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 13:55 [PATCH v3 0/3] dt-bindings: rockchip: Add support for rk809 audio codec Tim Lunn
2024-01-20 13:55 ` [PATCH v3 1/3] dt-bindings: rockchip: rk809 fix existing example Tim Lunn
2024-01-20 13:55 ` [PATCH v3 2/3] dt-bindings: rockchip: rk809: Document audio codec properties Tim Lunn
2024-01-22 8:14 ` Krzysztof Kozlowski
2024-01-23 4:10 ` Tim Lunn
2024-01-23 7:37 ` Krzysztof Kozlowski
2024-01-23 8:33 ` Tim Lunn
2024-01-20 13:55 ` [PATCH v3 3/3] dt-bindings: rockchip: rk809: Document audio codec clock Tim Lunn
2024-01-22 8:16 ` Krzysztof Kozlowski
2024-01-23 4:25 ` Tim Lunn
2024-01-23 7:41 ` Krzysztof Kozlowski [this message]
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=dc66e8ef-987e-48e2-890e-418cd582e7df@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=tim@feathertop.org \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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