From: John Watts <contact@jookia.org>
To: alsa-devel@alsa-project.org
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
John Watts <contact@jookia.org>,
patches@opensource.cirrus.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] ASoC: wm8782: Allow higher audio rates
Date: Fri, 11 Aug 2023 08:49:27 +1000 [thread overview]
Message-ID: <20230810224930.3216717-1-contact@jookia.org> (raw)
The wm8782 supports higher audio rates than just 48kHz. This is
configured by setting the FSAMPEN pin on the codec chip.
This patch series introduces the 'max-rate' device tree property
to allow indicating which rates are fully supported by the codec
without accidentally overclocking.
John Watts (3):
ASoC: wm8782: Handle maximum audio rate at runtime
ASoC: wm8782: Use max-rate device tree property
ASoC: dt-bindings: wlf,wm8782: Add max-rate property
.../devicetree/bindings/sound/wm8782.txt | 2 +
sound/soc/codecs/wm8782.c | 49 ++++++++++++++-----
2 files changed, 39 insertions(+), 12 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-10 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 22:49 John Watts [this message]
2023-08-10 22:49 ` [PATCH 1/3] ASoC: wm8782: Handle maximum audio rate at runtime John Watts
2023-08-10 22:49 ` [PATCH 2/3] ASoC: wm8782: Use max-rate device tree property John Watts
2023-08-10 22:49 ` [PATCH 3/3] ASoC: dt-bindings: wlf,wm8782: Add max-rate property John Watts
2023-08-11 13:59 ` Mark Brown
2023-08-11 14:26 ` John Watts
2023-08-14 18:27 ` Mark Brown
2023-08-14 21:44 ` John Watts
2023-08-21 17:28 ` 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=20230810224930.3216717-1-contact@jookia.org \
--to=contact@jookia.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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).