Linux GPIO subsystem development
 help / color / mirror / Atom feed
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 2/2] ASoC: rt5677: Enable standalone compilation for generic card use
Date: Sat, 20 Jun 2026 15:50:59 +0200	[thread overview]
Message-ID: <20260620-smaug-audio-v1-2-e318acdf5abd@bootlin.com> (raw)
In-Reply-To: <20260620-smaug-audio-v1-0-e318acdf5abd@bootlin.com>

Add a prompt string to make the RT5677 driver user-selectable, allowing
it to be built independently for use with generic sound card bindings.

Signed-off-by: Diogo Ivo <diogo.ivo@bootlin.com>
---
 sound/soc/codecs/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
index 252f683be3c1..e9de333c5c8a 100644
--- a/sound/soc/codecs/Kconfig
+++ b/sound/soc/codecs/Kconfig
@@ -1888,7 +1888,7 @@ config SND_SOC_RT5670
 	depends on I2C
 
 config SND_SOC_RT5677
-	tristate
+	tristate "Realtek RT5677 Codec"
 	depends on I2C
 	select REGMAP_I2C
 	select REGMAP_IRQ

-- 
2.54.0


  parent 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 [PATCH 0/2] ASoC: rt5677: add GPIO get_direction and enable standalone compilation Diogo Ivo
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 ` Diogo Ivo [this message]
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-2-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