linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: linux-i2c@vger.kernel.org, linux-media@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 3/6] media: i2c: smiapp: Convert to new i2c device probe()
Date: Wed, 10 Jul 2019 22:51:46 +0100	[thread overview]
Message-ID: <20190710215149.9208-4-kieran.bingham+renesas@ideasonboard.com> (raw)
In-Reply-To: <20190710215149.9208-1-kieran.bingham+renesas@ideasonboard.com>

The I2C core framework provides a simplified probe framework from commit
b8a1a4cd5a98 ("i2c: Provide a temporary .probe_new() call-back type").

This driver does not utilise the i2c_device_id table in the probe, so we can
easily convert it to utilise the simplfied i2c driver registration.

Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
---
 drivers/media/i2c/smiapp/smiapp-core.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/media/i2c/smiapp/smiapp-core.c b/drivers/media/i2c/smiapp/smiapp-core.c
index 2d78e846d822..9adf8e034e7d 100644
--- a/drivers/media/i2c/smiapp/smiapp-core.c
+++ b/drivers/media/i2c/smiapp/smiapp-core.c
@@ -2847,8 +2847,7 @@ static struct smiapp_hwconfig *smiapp_get_hwconfig(struct device *dev)
 	return NULL;
 }
 
-static int smiapp_probe(struct i2c_client *client,
-			const struct i2c_device_id *devid)
+static int smiapp_probe(struct i2c_client *client)
 {
 	struct smiapp_sensor *sensor;
 	struct smiapp_hwconfig *hwcfg = smiapp_get_hwconfig(&client->dev);
@@ -3172,7 +3171,7 @@ static struct i2c_driver smiapp_i2c_driver = {
 		.name = SMIAPP_NAME,
 		.pm = &smiapp_pm_ops,
 	},
-	.probe	= smiapp_probe,
+	.probe_new = smiapp_probe,
 	.remove	= smiapp_remove,
 	.id_table = smiapp_id_table,
 };
-- 
2.20.1


  parent reply	other threads:[~2019-07-10 21:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190710215149.9208-1-kieran.bingham+renesas@ideasonboard.com>
2019-07-10 21:51 ` [PATCH 1/6] media: radio: si4713: Convert to new i2c device probe() Kieran Bingham
2019-07-31 19:51   ` Wolfram Sang
2019-07-10 21:51 ` [PATCH 2/6] media: radio: si470x: " Kieran Bingham
2019-07-31 19:51   ` Wolfram Sang
2019-07-10 21:51 ` Kieran Bingham [this message]
2019-07-31 19:51   ` [PATCH 3/6] media: i2c: smiapp: " Wolfram Sang
2019-07-10 21:51 ` [PATCH 4/6] media: i2c: s5c73m3: " Kieran Bingham
2019-07-12 10:27   ` Andrzej Hajda
2019-07-31 19:51   ` Wolfram Sang
2019-07-10 21:51 ` [PATCH 5/6] media: i2c: et8ek8: " Kieran Bingham
2019-07-31 19:52   ` Wolfram Sang
2019-07-10 21:51 ` [PATCH 6/6] media: i2c: " Kieran Bingham
2019-07-11  8:05   ` Marco Felsch
2019-07-11  8:18     ` Kieran Bingham
2019-07-12 10:46       ` Marco Felsch
2019-07-12 10:29   ` Andrzej Hajda
2019-07-31 19:53   ` Wolfram Sang

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=20190710215149.9208-4-kieran.bingham+renesas@ideasonboard.com \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=wsa@the-dreams.de \
    /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).