From: Stephen Kitt <steve@sk2.org>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Wolfram Sang <wsa@kernel.org>,
linux-kernel@vger.kernel.org, Stephen Kitt <steve@sk2.org>
Subject: [PATCH 11/14] ASoC: tda7419: use simple i2c probe function
Date: Tue, 5 Apr 2022 18:58:33 +0200 [thread overview]
Message-ID: <20220405165836.2165310-12-steve@sk2.org> (raw)
In-Reply-To: <20220405165836.2165310-1-steve@sk2.org>
The i2c probe functions here don't use the id information provided in
their second argument, so the single-parameter i2c probe function
("probe_new") can be used instead.
This avoids scanning the identifier tables during probes.
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
sound/soc/codecs/tda7419.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/sound/soc/codecs/tda7419.c b/sound/soc/codecs/tda7419.c
index 83d220054c96..d964e5207569 100644
--- a/sound/soc/codecs/tda7419.c
+++ b/sound/soc/codecs/tda7419.c
@@ -571,8 +571,7 @@ static const struct snd_soc_component_driver tda7419_component_driver = {
.num_dapm_routes = ARRAY_SIZE(tda7419_dapm_routes),
};
-static int tda7419_probe(struct i2c_client *i2c,
- const struct i2c_device_id *id)
+static int tda7419_probe(struct i2c_client *i2c)
{
struct tda7419_data *tda7419;
int i, ret;
@@ -630,7 +629,7 @@ static struct i2c_driver tda7419_driver = {
.name = "tda7419",
.of_match_table = tda7419_of_match,
},
- .probe = tda7419_probe,
+ .probe_new = tda7419_probe,
.id_table = tda7419_i2c_id,
};
--
2.27.0
next prev parent reply other threads:[~2022-04-06 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 16:58 [PATCH 00/14] ASoC: remaining simple i2c probe changes Stephen Kitt
2022-04-05 16:58 ` [PATCH 01/14] ASoC: ak4*: use simple i2c probe function Stephen Kitt
2022-04-05 16:58 ` [PATCH 02/14] ASoC: cx2072x: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 03/14] ASoC: es83*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 04/14] ASoC: lm4857: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 05/14] ASoC: max9*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 06/14] ASoC: ml26124: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 07/14] ASoC: nau8*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 08/14] ASoC: pcm*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 09/14] ASoC: sta*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 10/14] ASoC: tas*: " Stephen Kitt
2022-04-05 16:58 ` Stephen Kitt [this message]
2022-04-05 16:58 ` [PATCH 12/14] ASoC: tlv320*: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 13/14] ASoC: ts3a227e: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 14/14] ASoC: uda1380: " Stephen Kitt
2022-04-12 17:38 ` [PATCH 00/14] ASoC: remaining simple i2c probe changes 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=20220405165836.2165310-12-steve@sk2.org \
--to=steve@sk2.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@kernel.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
all inboxes | Powered by JetHome®