Skip to contentSkip to conversation

ASoC: tegra: Set driver name explicitly

PATCH In review Thierry Reding 2 participants 2 messages Mar 30, 2021 – Apr 1, 2021

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ASoC: tegra: Set driver name explicitly

From: Thierry Reding <[email protected]>

The SoC sound core will generate a driver name by normalizing the card name. However, most of the time that name does not tell anything about the driver and is therefore useless for this purpose.

Make the driver name more useful by setting it explicitly during card initialization.

---
 sound/soc/tegra/tegra_audio_graph_card.c | 1 +
 1 file changed, 1 insertion(+)
sound/soc/tegra/tegra_audio_graph_card.c +1 -0
index ddedf18adde1..47b319504c8c 100644
@@ -198,6 +198,7 @@ static int tegra_audio_graph_probe(struct platform_device *pdev)
 		return -ENOMEM;
 
 	card = simple_priv_to_card(&priv->simple);
+	card->driver_name = "tegra-ape";
 
 	card->probe = tegra_audio_graph_card_probe;
 
Signature · 1 line
2.30.2
maintainer
#1 lore raw
Quoted 6 lines · Thierry Reding

The SoC sound core will generate a driver name by normalizing the card name. However, most of the time that name does not tell anything about the driver and is therefore useless for this purpose.

Make the driver name more useful by setting it explicitly during card initialization.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: tegra: Set driver name explicitly

      commit: 868d5c6340d878f44acf73c92923995b896b6454

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark