ASoC: lm49xxx: use simple i2c probe function
Subsystems (3)
PATCH 1/1 ASoC: lm49xxx: use simple i2c probe function
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.
--- sound/soc/codecs/isabelle.c | 5 ++--- sound/soc/codecs/lm49453.c | 5 ++--- 2 files changed, 4 insertions(+), 6 deletions(-)
sound/soc/codecs/isabelle.c +2 -3
@@ -1108,8 +1108,7 @@ static const struct regmap_config isabelle_regmap_config = { .cache_type = REGCACHE_RBTREE, }; -static int isabelle_i2c_probe (struct i2c_client *i2c, -const struct i2c_device_id *id) +static int isabelle_i2c_probe (struct i2c_client *i2c) {struct regmap *isabelle_regmap;int ret =0 ;
@@ -1144,7 +1143,7 @@ static struct i2c_driver isabelle_i2c_driver = { .driver = { .name = "isabelle", }, - .probe = isabelle_i2c_probe, + .probe_new = isabelle_i2c_probe, .id_table = isabelle_i2c_id, };
sound/soc/codecs/lm49453.c +2 -3
@@ -1412,8 +1412,7 @@ static const struct regmap_config lm49453_regmap_config = { .cache_type = REGCACHE_RBTREE, }; -static int lm49453_i2c_probe (struct i2c_client *i2c, -const struct i2c_device_id *id) +static int lm49453_i2c_probe (struct i2c_client *i2c) {struct lm49453_priv *lm49453;int ret =0 ;
@@ -1458,7 +1457,7 @@ static struct i2c_driver lm49453_i2c_driver = { .driver = { .name = "lm49453", }, - .probe = lm49453_i2c_probe, + .probe_new = lm49453_i2c_probe, .remove = lm49453_i2c_remove, .id_table = lm49453_i2c_id, };
Signature · 1 line
2.27.0
Mark Brown
maintainerQuoted 8 lines · Stephen Kitt
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.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: lm49xxx: use simple i2c probe function
commit: 6b84012ef242c8793c1fdcc002db48c822bb641b
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