From: Tim Lunn <tim@feathertop.org>
To: linux-rockchip@lists.infradead.org, conor.dooley@microchip.com,
robh+dt@kernel.org, krzysztof.kozlowski@linaro.org,
devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Tim Lunn <tim@feathertop.org>,
Chris Morgan <macromorgan@hotmail.com>,
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: [PATCH v3 0/3] dt-bindings: rockchip: Add support for rk809 audio codec
Date: Sun, 21 Jan 2024 00:55:26 +1100 [thread overview]
Message-ID: <20240120135529.899403-1-tim@feathertop.org> (raw)
Rockchip RK809 shares the same audio codec block as the rk817 mfd, and
is compatible with the existing rk817_codec driver. There are already
about seven rk809 based boards that implement this codec in existing
device tree files.
This series documents the audio codec properties in rockchip,rk809.yaml
bindings and updates the example with their usage. It also fixes a typo
in the existing example that was causing the example to be validated
against the wrong binding.
Changes in v3:
- split out clocks into separate patch and group example properties
where properties are introduced.
- Address review comments
- drop clock descriptions that arent required
- set maxitems on clocks
Changes in v2:
- Fix vcc-supply warning detected by dt_binding bot
- Fix missing include and pinctrl for codec example
Tim Lunn (3):
dt-bindings: rockchip: rk809 fix existing example
dt-bindings: rockchip: rk809: Document audio codec properties
dt-bindings: rockchip: rk809: Document audio codec clock
.../bindings/mfd/rockchip,rk809.yaml | 42 +++++++++++++++----
1 file changed, 35 insertions(+), 7 deletions(-)
--
2.40.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-01-20 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 13:55 Tim Lunn [this message]
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
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=20240120135529.899403-1-tim@feathertop.org \
--to=tim@feathertop.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=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=macromorgan@hotmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).