From: Geert Uytterhoeven <geert+renesas@glider.be> To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Damien Horsley <Damien.Horsley@imgtec.com>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH 0/2] dt-bindings: sound: ti,pcm3168a: json-schema conversion and fixes Date: Fri, 2 Dec 2022 13:55:42 +0100 [thread overview] Message-ID: <cover.1669980383.git.geert+renesas@glider.be> (raw) Hi all, This patch series is an attempt to convert the existing DT binding documentation for the Texas Instruments PCM3168A Audio Codec to json-schema ("another one bites the dust" ;-). It consists of two parts: 1. The actual DT binding conversion, 2. An RFC patch to fix the impedance mismatch between the bindings and the description in the Shimafuji Kingfisher board DTS. I'm not super-familiar with the audio details, so I would be very grateful to receive your comments. Thanks! Geert Uytterhoeven (2): dt-bindings: sound: ti,pcm3168a: Convert to json-schema [RFC] arm64: dts: renesas: ulcb-kf: Fix pcm3168a audio codec node .../devicetree/bindings/sound/ti,pcm3168a.txt | 56 ---------- .../bindings/sound/ti,pcm3168a.yaml | 105 ++++++++++++++++++ arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 5 +- 3 files changed, 107 insertions(+), 59 deletions(-) delete mode 100644 Documentation/devicetree/bindings/sound/ti,pcm3168a.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,pcm3168a.yaml -- 2.25.1 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert+renesas@glider.be> To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Damien Horsley <Damien.Horsley@imgtec.com>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org, alsa-devel@alsa-project.org, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH 0/2] dt-bindings: sound: ti, pcm3168a: json-schema conversion and fixes Date: Fri, 2 Dec 2022 13:55:42 +0100 [thread overview] Message-ID: <cover.1669980383.git.geert+renesas@glider.be> (raw) Hi all, This patch series is an attempt to convert the existing DT binding documentation for the Texas Instruments PCM3168A Audio Codec to json-schema ("another one bites the dust" ;-). It consists of two parts: 1. The actual DT binding conversion, 2. An RFC patch to fix the impedance mismatch between the bindings and the description in the Shimafuji Kingfisher board DTS. I'm not super-familiar with the audio details, so I would be very grateful to receive your comments. Thanks! Geert Uytterhoeven (2): dt-bindings: sound: ti,pcm3168a: Convert to json-schema [RFC] arm64: dts: renesas: ulcb-kf: Fix pcm3168a audio codec node .../devicetree/bindings/sound/ti,pcm3168a.txt | 56 ---------- .../bindings/sound/ti,pcm3168a.yaml | 105 ++++++++++++++++++ arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 5 +- 3 files changed, 107 insertions(+), 59 deletions(-) delete mode 100644 Documentation/devicetree/bindings/sound/ti,pcm3168a.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,pcm3168a.yaml -- 2.25.1 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next reply other threads:[~2022-12-02 12:55 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-02 12:55 Geert Uytterhoeven [this message] 2022-12-02 12:55 ` [PATCH 0/2] dt-bindings: sound: ti, pcm3168a: json-schema conversion and fixes Geert Uytterhoeven 2022-12-02 12:55 ` [PATCH 1/2] dt-bindings: sound: ti,pcm3168a: Convert to json-schema Geert Uytterhoeven 2022-12-02 12:55 ` Geert Uytterhoeven 2022-12-03 12:13 ` Krzysztof Kozlowski 2022-12-03 12:13 ` Krzysztof Kozlowski 2022-12-05 8:00 ` Geert Uytterhoeven 2022-12-05 8:00 ` [PATCH 1/2] dt-bindings: sound: ti, pcm3168a: " Geert Uytterhoeven 2022-12-06 9:16 ` [PATCH 1/2] dt-bindings: sound: ti,pcm3168a: " Krzysztof Kozlowski 2022-12-06 9:16 ` Krzysztof Kozlowski 2022-12-02 12:55 ` [PATCH/RFC 2/2] arm64: dts: renesas: ulcb-kf: Fix pcm3168a audio codec node Geert Uytterhoeven 2022-12-02 12:55 ` Geert Uytterhoeven 2022-12-07 0:36 ` Kuninori Morimoto 2022-12-07 0:36 ` Kuninori Morimoto 2022-12-12 23:49 ` Kuninori Morimoto 2022-12-12 23:49 ` Kuninori Morimoto 2022-12-13 8:31 ` Geert Uytterhoeven 2022-12-13 8:31 ` Geert Uytterhoeven 2022-12-13 23:10 ` Kuninori Morimoto 2022-12-13 23:10 ` Kuninori Morimoto
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=cover.1669980383.git.geert+renesas@glider.be \ --to=geert+renesas@glider.be \ --cc=Damien.Horsley@imgtec.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=kuninori.morimoto.gx@renesas.com \ --cc=lgirdwood@gmail.com \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=robh+dt@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.