From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: git@apitzsch.eu
Cc: Ricardo Ribalda <ribalda@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Vincent Knecht <vincent.knecht@mailoo.org>,
Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [PATCH v3 10/12] media: i2c: imx214: Verify chip ID
Date: Tue, 10 Dec 2024 12:40:20 +0000 [thread overview]
Message-ID: <Z1g2tLicdrb6lfoK@kekkonen.localdomain> (raw)
In-Reply-To: <20241207-imx214-v3-10-ab60af7ee915@apitzsch.eu>
Hi André,
Thanks for the update.
On Sat, Dec 07, 2024 at 09:47:59PM +0100, André Apitzsch via B4 Relay wrote:
> From: André Apitzsch <git@apitzsch.eu>
>
> Check the chip ID and stop probing if it is no imx214 sensor.
>
> Acked-by: Ricardo Ribalda <ribalda@chromium.org>
> Signed-off-by: André Apitzsch <git@apitzsch.eu>
> ---
> drivers/media/i2c/imx214.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/media/i2c/imx214.c b/drivers/media/i2c/imx214.c
> index a35e4e60e55c2b9d9e3090c98e695f78d099cf44..3cd64bb91795d8490acad5926940c111fb95fae5 100644
> --- a/drivers/media/i2c/imx214.c
> +++ b/drivers/media/i2c/imx214.c
> @@ -20,6 +20,10 @@
> #include <media/v4l2-fwnode.h>
> #include <media/v4l2-subdev.h>
>
> +/* Chip ID */
> +#define IMX214_REG_CHIP_ID CCI_REG16(0x0016)
> +#define IMX214_CHIP_ID 0x0214
> +
> #define IMX214_REG_MODE_SELECT CCI_REG8(0x0100)
> #define IMX214_MODE_STANDBY 0x00
> #define IMX214_MODE_STREAMING 0x01
> @@ -1092,6 +1096,27 @@ static int imx214_get_regulators(struct device *dev, struct imx214 *imx214)
> imx214->supplies);
> }
>
> +/* Verify chip ID */
> +static int imx214_identify_module(struct imx214 *imx214)
> +{
> + struct i2c_client *client = v4l2_get_subdevdata(&imx214->sd);
> + int ret;
> + u64 val;
> +
> + ret = cci_read(imx214->regmap, IMX214_REG_CHIP_ID, &val, NULL);
> + if (ret)
> + return dev_err_probe(&client->dev, ret,
> + "failed to read chip id %x\n",
> + IMX214_CHIP_ID);
> +
> + if (val != IMX214_CHIP_ID)
> + return dev_err_probe(&client->dev, -EIO,
> + "chip id mismatch: %x!=%llx\n",
> + IMX214_CHIP_ID, val);
> +
> + return 0;
> +}
> +
> static int imx214_parse_fwnode(struct device *dev)
> {
> struct fwnode_handle *endpoint;
> @@ -1184,6 +1209,10 @@ static int imx214_probe(struct i2c_client *client)
> */
> imx214_power_on(imx214->dev);
>
> + ret = imx214_identify_module(imx214);
> + if (ret)
> + goto error_power_off;
The error handling was wrong in the driver, the code under the
error_power_off label only disables the regulator (and runtime PM, which
hasn't been enabled) but it does not disable or unprepare the clock. Could
you fix these in a new patch, please?
> +
> pm_runtime_set_active(imx214->dev);
> pm_runtime_enable(imx214->dev);
> pm_runtime_idle(imx214->dev);
>
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-12-10 12:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 20:47 [PATCH v3 00/12] media: i2c: imx214: Miscellaneous cleanups and improvements André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 01/12] media: i2c: imx214: Use subdev active state André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 02/12] media: i2c: imx214: Simplify with dev_err_probe() André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 03/12] media: i2c: imx214: Convert to CCI register access helpers André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 04/12] media: i2c: imx214: Replace register addresses with macros André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 05/12] media: i2c: imx214: Drop IMX214_REG_EXPOSURE from mode reg arrays André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 06/12] media: i2c: imx214: Check number of lanes from device tree André Apitzsch via B4 Relay
2024-12-08 21:07 ` Ricardo Ribalda Delgado
2024-12-10 12:35 ` Sakari Ailus
2024-12-07 20:47 ` [PATCH v3 07/12] media: i2c: imx214: Add vblank and hblank controls André Apitzsch via B4 Relay
2024-12-08 20:59 ` Ricardo Ribalda Delgado
2024-12-08 21:19 ` Ricardo Ribalda Delgado
2024-12-10 12:34 ` Sakari Ailus
2024-12-14 22:45 ` André Apitzsch
2024-12-15 12:10 ` Sakari Ailus
2024-12-08 21:35 ` André Apitzsch
2024-12-08 21:47 ` Ricardo Ribalda Delgado
2024-12-15 22:35 ` André Apitzsch
2024-12-16 13:00 ` Ricardo Ribalda Delgado
2024-12-17 7:17 ` Sakari Ailus
2024-12-07 20:47 ` [PATCH v3 08/12] media: i2c: imx214: Implement vflip/hflip controls André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 09/12] media: i2c: imx214: Add analogue/digital gain control André Apitzsch via B4 Relay
2024-12-07 20:47 ` [PATCH v3 10/12] media: i2c: imx214: Verify chip ID André Apitzsch via B4 Relay
2024-12-10 12:40 ` Sakari Ailus [this message]
2024-12-07 20:48 ` [PATCH v3 11/12] media: i2c: imx214: Add test pattern control André Apitzsch via B4 Relay
2024-12-07 20:48 ` [PATCH v3 12/12] media: i2c: imx214: Fix link frequency André Apitzsch via B4 Relay
2024-12-08 21:05 ` Ricardo Ribalda Delgado
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=Z1g2tLicdrb6lfoK@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=git@apitzsch.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=ribalda@kernel.org \
--cc=vincent.knecht@mailoo.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®