From: Diogo Ivo <diogo.ivo@bootlin.com>
To: Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, Diogo Ivo <diogo.ivo@bootlin.com>
Subject: [PATCH 0/2] ASoC: rt5677: add GPIO get_direction and enable standalone compilation
Date: Sat, 20 Jun 2026 15:50:57 +0200 [thread overview]
Message-ID: <20260620-smaug-audio-v1-0-e318acdf5abd@bootlin.com> (raw)
This small series fixes two issues in the RT5677 ASoC codec driver:
- Patch 1 adds the missing GPIO .get_direction() callback, allowing
the direction of GPIO pins to be queried.
- Patch 2 makes the Kconfig option user-visible so the driver can be
built standalone for example when using generic audio-graph-card
bindings, which do not pull in specific codec drivers via select/imply.
Signed-off-by: Diogo Ivo <diogo.ivo@bootlin.com>
---
Diogo Ivo (2):
ASoC: rt5677: Add GPIO .get_direction() callback
ASoC: rt5677: Enable standalone compilation for generic card use
sound/soc/codecs/Kconfig | 2 +-
sound/soc/codecs/rt5677.c | 17 +++++++++++++++++
2 files changed, 18 insertions(+), 1 deletion(-)
---
base-commit: 1a3746ccbb0a97bed3c06ccde6b880013b1dddc1
change-id: 20260620-smaug-audio-34f0209f22b4
Best regards,
--
Diogo Ivo <diogo.ivo@bootlin.com>
next reply other threads:[~2026-06-20 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 13:50 Diogo Ivo [this message]
2026-06-20 13:50 ` [PATCH 1/2] ASoC: rt5677: Add GPIO .get_direction() callback Diogo Ivo
2026-06-22 8:13 ` Bartosz Golaszewski
2026-06-20 13:50 ` [PATCH 2/2] ASoC: rt5677: Enable standalone compilation for generic card use Diogo Ivo
2026-06-29 18:41 ` [PATCH 0/2] ASoC: rt5677: add GPIO get_direction and enable standalone compilation Mark Brown
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=20260620-smaug-audio-v1-0-e318acdf5abd@bootlin.com \
--to=diogo.ivo@bootlin.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--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