public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Morgan <macroalpha82@gmail.com>
To: linux-sound@vger.kernel.org
Cc: devicetree@vger.kernel.org, wangweidong.a@awinic.com,
	tiwai@suse.com, perex@perex.cz, conor+dt@kernel.org,
	krzk+dt@kernel.org, robh@kernel.org, broonie@kernel.org,
	lgirdwood@gmail.com, Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2] Anbernic RG-DS AW87391 Speaker Amps
Date: Fri, 23 Jan 2026 09:47:29 -0600	[thread overview]
Message-ID: <20260123154731.130649-1-macroalpha82@gmail.com> (raw)

From: Chris Morgan <macromorgan@hotmail.com>

Add support for the Anbernic RG-DS Speaker Amplifiers. The Anbernic
RG-DS uses two AW87391 ICs at 0x58 and 0x5B on i2c2. However, the
manufacturer did not provide a firmware file, only a sequence of
register writes to each device to enable and disable them.

Add support for this *specific* configuration in the AW87390 driver.
Since we are relying on a device specific sequence I am using a
device specific compatible string. This driver does not currently
support the aw87391 for any other device as I have none to test
with valid firmware. Attempts to create firmware with the AwinicSCPv4
have not been successful.

Chris Morgan (2):
  ASoC: dt-bindings: aw87390: Add Anbernic RG-DS Amplifier
  ASoC: codecs: aw87390: Add Anbernic RG-DS amplifier driver

 .../bindings/sound/awinic,aw87390.yaml        |  34 +++-
 sound/soc/codecs/aw87390.c                    | 176 +++++++++++++++++-
 sound/soc/codecs/aw87390.h                    |  86 +++++++++
 3 files changed, 283 insertions(+), 13 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-01-23 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 15:47 Chris Morgan [this message]
2026-01-23 15:47 ` [PATCH 1/2] ASoC: dt-bindings: aw87390: Add Anbernic RG-DS Amplifier Chris Morgan
2026-01-23 17:09   ` Conor Dooley
2026-01-23 15:47 ` [PATCH 2/2] ASoC: codecs: aw87390: Add Anbernic RG-DS amplifier driver Chris Morgan
2026-01-23 23:32   ` kernel test robot

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=20260123154731.130649-1-macroalpha82@gmail.com \
    --to=macroalpha82@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.com \
    --cc=wangweidong.a@awinic.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