From: Tim Lunn <tim@feathertop.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
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 1/3] dt-bindings: rockchip: Add rk809 support for rk817 audio codec
Date: Wed, 17 Jan 2024 21:38:42 +1100 [thread overview]
Message-ID: <6d828e2d-a25b-4784-9905-4a264b7d78fe@feathertop.org> (raw)
In-Reply-To: <71413ca3-1a14-4eda-ad29-dc5fcbe5afb3@linaro.org>
On 1/17/24 21:12, Krzysztof Kozlowski wrote:
> On 17/01/2024 10:37, Tim Lunn wrote:
>>> You can drop the description.
>> Yes just 1 clock, i will fix this.
>>>> +
>>>> + clock-names:
>>>> + description:
>>>> + The clock name for the codec clock.
>>> Drop.
>> Just drop the description? I dont think can drop the clock names as the
>> driver use the name to lookup clock:
> Description. But anyway the problem is that adding clocks should be
> separate patch with its own explanation.
>
Right, but I am not actually adding any clocks, just documenting what is
already there.
There are already boards using this codec with rk809 in dts files and is
working fine from driver side.
>
>
>> devm_clk_get(pdev->dev.parent, "mclk");
>>>> + items:
>>>> + - const: mclk
>>>> +
>>>> + '#sound-dai-cells':
>>>> + description:
>>>> + Needed for the interpretation of sound dais.
>>> Common property, don't need the description.
>> Ok
>>>> + const: 0
>>>> +
>>>> + codec:
>>>> + description: |
>>>> + The child node for the codec to hold additional properties. If no
>>>> + additional properties are required for the codec, this node can be
>>>> + omitted.
>>> Why do you need a child node here? Just put the 1 property in the parent
>>> node.
>> This is how the existing rk817 codec driver was setup. I suppose it was
>> copied from downstream, where there are more properties than just the
>> one. I don't know if there was any intention (or need) to implement
>> those other properties.
> You need to clearly express ABI requirements in the commit msg.
> Otherwise you will get a review like for new bindings.
Got it, I will clarify this and future commit messages
Regards
Tim
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-01-17 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:46 [PATCH 0/3] dt-bindings: rockchip: Add support for rk809 " Tim Lunn
2024-01-16 8:46 ` [PATCH 1/3] dt-bindings: rockchip: Add rk809 support for rk817 " Tim Lunn
2024-01-16 19:37 ` Rob Herring
2024-01-17 9:37 ` Tim Lunn
2024-01-17 10:12 ` Krzysztof Kozlowski
2024-01-17 10:38 ` Tim Lunn [this message]
2024-01-17 10:57 ` Krzysztof Kozlowski
2024-01-17 11:08 ` Tim Lunn
2024-01-16 8:46 ` [PATCH 2/3] dt-bindings: rockchip: rk809 fix compatible string in examples Tim Lunn
2024-01-16 11:08 ` Rob Herring
2024-01-16 19:37 ` Rob Herring
2024-01-16 19:39 ` Rob Herring
2024-01-17 7:42 ` Krzysztof Kozlowski
2024-01-16 8:46 ` [PATCH 3/3] dt-bindings: rockchip: Update rk809 example with audio codec properties Tim Lunn
2024-01-16 11:08 ` Rob Herring
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=6d828e2d-a25b-4784-9905-4a264b7d78fe@feathertop.org \
--to=tim@feathertop.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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@kernel.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
all inboxes | Powered by JetHome®