linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13/14] ASoC: ts3a227e: use simple i2c probe function
Date: Tue,  5 Apr 2022 18:58:35 +0200	[thread overview]
Message-ID: <20220405165836.2165310-14-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/ts3a227e.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/sound/soc/codecs/ts3a227e.c b/sound/soc/codecs/ts3a227e.c
index 962f5d48378a..d8ab0810fceb 100644
--- a/sound/soc/codecs/ts3a227e.c
+++ b/sound/soc/codecs/ts3a227e.c
@@ -282,8 +282,7 @@ static int ts3a227e_parse_device_property(struct ts3a227e *ts3a227e,
 	return 0;
 }
 
-static int ts3a227e_i2c_probe(struct i2c_client *i2c,
-			      const struct i2c_device_id *id)
+static int ts3a227e_i2c_probe(struct i2c_client *i2c)
 {
 	struct ts3a227e *ts3a227e;
 	struct device *dev = &i2c->dev;
@@ -389,7 +388,7 @@ static struct i2c_driver ts3a227e_driver = {
 		.of_match_table = of_match_ptr(ts3a227e_of_match),
 		.acpi_match_table = ACPI_PTR(ts3a227e_acpi_match),
 	},
-	.probe = ts3a227e_i2c_probe,
+	.probe_new = ts3a227e_i2c_probe,
 	.id_table = ts3a227e_i2c_ids,
 };
 module_i2c_driver(ts3a227e_driver);
-- 
2.27.0


  parent reply	other threads:[~2022-04-05 23:41 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 ` [PATCH 11/14] ASoC: tda7419: " Stephen Kitt
2022-04-05 16:58 ` [PATCH 12/14] ASoC: tlv320*: " Stephen Kitt
2022-04-05 16:58 ` Stephen Kitt [this message]
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-14-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;
as well as URLs for NNTP newsgroup(s).