[PATCHv2] ASoC: tegra: ADX: use of_device_get_match_data

Rosen Penev posted 1 patch 1 week, 3 days ago
sound/soc/tegra/tegra210_adx.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
[PATCHv2] ASoC: tegra: ADX: use of_device_get_match_data
Posted by Rosen Penev 1 week, 3 days ago
Remove open coding of the function to simplify the code.

Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
 v2: move back soc_data assignment to the same place
 sound/soc/tegra/tegra210_adx.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/sound/soc/tegra/tegra210_adx.c b/sound/soc/tegra/tegra210_adx.c
index 12371f895234..9b662fcee66f 100644
--- a/sound/soc/tegra/tegra210_adx.c
+++ b/sound/soc/tegra/tegra210_adx.c
@@ -677,8 +677,7 @@ static int tegra210_adx_platform_probe(struct platform_device *pdev)
 {
 	struct device *dev = &pdev->dev;
 	struct tegra210_adx *adx;
-	const struct of_device_id *match;
-	struct tegra210_adx_soc_data *soc_data;
+	const struct tegra210_adx_soc_data *soc_data;
 	void __iomem *regs;
 	int err, i;

@@ -686,8 +685,7 @@ static int tegra210_adx_platform_probe(struct platform_device *pdev)
 	if (!adx)
 		return -ENOMEM;

-	match = of_match_device(tegra210_adx_of_match, dev);
-	soc_data = (struct tegra210_adx_soc_data *)match->data;
+	soc_data = of_device_get_match_data(dev);
 	adx->soc_data = soc_data;

 	dev_set_drvdata(dev, adx);
--
2.54.0
Re: [PATCHv2] ASoC: tegra: ADX: use of_device_get_match_data
Posted by Mark Brown 4 days, 2 hours ago
On Thu, 28 May 2026 15:19:28 -0700, Rosen Penev wrote:
> ASoC: tegra: ADX: use of_device_get_match_data

Applied to

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

Thanks!

[1/1] ASoC: tegra: ADX: use of_device_get_match_data
      https://git.kernel.org/broonie/sound/c/ce3d971735bb

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