From: Tim Lunn <tim@feathertop.org>
To: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Cc: Tim Lunn <tim@feathertop.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>, Rob Herring <robh+dt@kernel.org>,
Zhang Qing <zhangqing@rock-chips.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] dt-bindings: rockchip: Add support for rk809 audio codec
Date: Tue, 16 Jan 2024 19:46:15 +1100 [thread overview]
Message-ID: <20240116084618.3112410-1-tim@feathertop.org> (raw)
Rockchip RK809 shares the same audio codec as the rk817 mfd, it is also
using the same rk817_codec driver. However it is missing from the
bindings.
This series documents the audio codec properties in rockchip,rk809.yaml
bindings and updates example.
Tim Lunn (3):
dt-bindings: rockchip: Add rk809 support for rk817 audio codec
dt-bindings: rockchip: rk809 fix compatible string in examples
dt-bindings: rockchip: Update rk809 example with audio codec
properties
.../bindings/mfd/rockchip,rk809.yaml | 40 +++++++++++++++++--
1 file changed, 37 insertions(+), 3 deletions(-)
--
2.40.1
next reply other threads:[~2024-01-16 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:46 Tim Lunn [this message]
2024-01-16 8:46 ` [PATCH 1/3] dt-bindings: rockchip: Add rk809 support for rk817 audio codec 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
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=20240116084618.3112410-1-tim@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=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=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