From: Binbin Zhou <zhoubinbin@loongson.cn>
To: Binbin Zhou <zhoubb.aaron@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, devicetree@vger.kernel.org,
linux-sound@vger.kernel.org, Binbin Zhou <zhoubinbin@loongson.cn>
Subject: [PATCH 0/3] ASoC: Add Loongson-2k0300 I2S controller support
Date: Wed, 11 Mar 2026 14:37:15 +0800 [thread overview]
Message-ID: <cover.1773107475.git.zhoubinbin@loongson.cn> (raw)
Hi all:
This patchset adds support for the Loongson-2K0300 I2S controller.
Similar to the Loongson-2K2000, it utilizes internal DMA for data
transfer but interfaces as a platform device.
Also, I cleaned up the redundant code from before.
Thanks.
Binbin
Binbin Zhou (6):
MAINTAINERS: Add entry for Loongson ASoC driver
ASoC: loongson: Combined regmap definitions
ASoC: loongson: Add `internal` to the names of internal DMA variables
ASoC: loongson: Separate external shared DMA from the platform
interface
ASoC: dt-bindings: loongson,ls2k1000-i2s: Document Loongson-2K0300
compatible
ASoC: loongson: Add Loongson-2k0300 I2S controller support
.../bindings/sound/loongson,ls2k1000-i2s.yaml | 22 ++-
MAINTAINERS | 7 +
sound/soc/loongson/Makefile | 4 +-
sound/soc/loongson/loongson_card.c | 2 +-
sound/soc/loongson/loongson_dma.c | 142 ++++++++++++------
sound/soc/loongson/loongson_dma.h | 6 +-
sound/soc/loongson/loongson_i2s.c | 61 +++++++-
sound/soc/loongson/loongson_i2s.h | 7 +-
sound/soc/loongson/loongson_i2s_pci.c | 59 +-------
sound/soc/loongson/loongson_i2s_plat.c | 98 ++++--------
10 files changed, 229 insertions(+), 179 deletions(-)
base-commit: e69bc9b4c9827f4af5dfecba10df35dcc67d180a
--
2.52.0
next reply other threads:[~2026-03-11 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 6:37 Binbin Zhou [this message]
2026-03-11 6:37 ` [PATCH 1/6] MAINTAINERS: Add entry for Loongson ASoC driver Binbin Zhou
2026-03-11 6:37 ` [PATCH 2/6] ASoC: loongson: Combined regmap definitions Binbin Zhou
2026-03-11 7:55 ` Huacai Chen
2026-03-11 8:17 ` Binbin Zhou
2026-03-11 6:37 ` [PATCH 3/6] ASoC: loongson: Add `internal` to the names of internal DMA variables Binbin Zhou
2026-03-11 7:56 ` Huacai Chen
2026-03-11 8:24 ` Binbin Zhou
2026-03-11 6:37 ` [PATCH 4/6] ASoC: loongson: Separate external shared DMA from the platform interface Binbin Zhou
2026-03-11 6:37 ` [PATCH 5/6] ASoC: dt-bindings: loongson,ls2k1000-i2s: Document Loongson-2K0300 compatible Binbin Zhou
2026-03-11 7:57 ` Huacai Chen
2026-03-11 8:29 ` Binbin Zhou
2026-03-13 13:18 ` Krzysztof Kozlowski
2026-03-11 6:37 ` [PATCH 6/6] ASoC: loongson: Add Loongson-2k0300 I2S controller support Binbin Zhou
2026-03-11 16:15 ` Mark Brown
2026-03-17 12:46 ` Binbin Zhou
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.1773107475.git.zhoubinbin@loongson.cn \
--to=zhoubinbin@loongson.cn \
--cc=broonie@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
--cc=zhoubb.aaron@gmail.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