From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: [PATCH 0/3] Clean up RK3328 audio codec GPIO control
Date: Thu, 6 Feb 2020 01:07:10 +0000 [thread overview]
Message-ID: <cover.1580950046.git.robin.murphy@arm.com> (raw)
Hi all,
Investigating the RK3328 GPIO_MUTE pin in the context of boards that use
it to control a regulator has highlighted that the audio codec driver
currently has some hard-coded implicit control of that pin. Fortunately
those boards don't currently enable the audio codec, because it would be
pretty terrible if playing audio changed the SD card I/O voltage. This
is a first crack at making things better.
Robin.
Robin Murphy (3):
ASoC: dt-bindings: Make RK3328 codec GPIO explicit
ASoC: rockchip: Make RK3328 GPIO_MUTE control explicit
arm64: dts: rockchip: Describe RK3328 GPIO_MUTE users
.../bindings/sound/rockchip,rk3328-codec.txt | 7 ++++++-
arch/arm64/boot/dts/rockchip/rk3328-a1.dts | 1 +
.../arm64/boot/dts/rockchip/rk3328-rock64.dts | 1 +
sound/soc/codecs/rk3328_codec.c | 20 +++++--------------
4 files changed, 13 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-06 1:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 1:07 Robin Murphy [this message]
[not found] ` <cover.1580950046.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2020-02-06 1:07 ` [PATCH 1/3] ASoC: dt-bindings: Make RK3328 codec GPIO explicit Robin Murphy
2020-02-06 1:07 ` [PATCH 2/3] ASoC: rockchip: Make RK3328 GPIO_MUTE control explicit Robin Murphy
[not found] ` <29a846da33c02df64eca62b5fa0f3884652f788f.1580950046.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2020-02-06 11:46 ` Mark Brown
[not found] ` <20200206114606.GM3897-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2020-02-06 12:36 ` Robin Murphy
[not found] ` <ad2c941a-9724-510e-959f-3cca3cab1dc2-5wv7dgnIgG8@public.gmane.org>
2020-02-06 13:57 ` Mark Brown
[not found] ` <20200206135718.GQ3897-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2020-02-06 18:05 ` Peter Geis
[not found] ` <CAMdYzYqTEnG_Q-8SvO2R6PeaPXQ3VBKu6iVYhYvb=wK7tT7c3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-06 21:38 ` [PATCH v2 " Robin Murphy
[not found] ` <bca13994-a8b1-fa21-fdf0-9f362d693f39-5wv7dgnIgG8@public.gmane.org>
2020-02-10 13:56 ` Mark Brown
2020-02-06 1:07 ` [PATCH 3/3] arm64: dts: rockchip: Describe RK3328 GPIO_MUTE users Robin Murphy
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.1580950046.git.robin.murphy@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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: 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).