Skip to contentSkip to conversation

support for AD5820 camera auto-focus coil

PATCH Superseded Pavel Machek 11 participants 73 messages May 17, 2016 – Dec 19, 2016

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +435 -0

435 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#1 lore raw

Hi Pavel,

Quoted 14 lines · Pavel Machek
drivers/media/i2c/ad5820.c new file +14 -0
+static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
+{
+	struct ad5820_device *coil =
+		container_of(ctrl->handler, struct ad5820_device, ctrls);
+	u32 code;
+	int r = 0;
+
+	switch (ctrl->id) {
+	case V4L2_CID_FOCUS_ABSOLUTE:
+		coil->focus_absolute = ctrl->val;
+		return ad5820_update_hw(coil);
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+		code = RAMP_US_TO_CODE(ctrl->val);

drivers/media/i2c/ad5820.c line 168

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+		ctrl->val = CODE_TO_RAMP_US(code);
+		coil->focus_ramp_time = ctrl->val;
+		break;
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+		coil->focus_ramp_mode = ctrl->val;
+		break;
+	}
+
+	return r;

Just return 0 instead, r is not used.

drivers/media/i2c/ad5820.c line 248

Quoted 3 lines
drivers/media/i2c/ad5820.c new file +3 -0
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	static const int CHECK_VALUE = 0x3FF0;

CHECK_VALUE is not used?

Quoted 15 lines
drivers/media/i2c/ad5820.c new file +15 -0
+static int ad5820_probe(struct i2c_client *client,
+			const struct i2c_device_id *devid)
+{
+	struct ad5820_device *coil;
+	int ret = 0;
+
+	coil = kzalloc(sizeof(*coil), GFP_KERNEL);
+	if (coil == NULL)
+		return -ENOMEM;
+
+	mutex_init(&coil->power_lock);
+
+	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
+	coil->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
+	coil->subdev.internal_ops = &ad5820_internal_ops;

drivers/media/i2c/ad5820.c line 373

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	strcpy(coil->subdev.name, "ad5820 focus");
+
+	ret = media_entity_pads_init(&coil->subdev.entity, 0, NULL);
+	if (ret < 0) {
+		kfree(coil);
+		return ret;
+	}
+
+	ret = v4l2_async_register_subdev(&coil->subdev);
+	if (ret < 0)

Do we need to call media_entity_cleanup() here?

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+static int __init ad5820_init(void)
+{
+	int rval;
+
+	rval = i2c_add_driver(&ad5820_i2c_driver);
+	if (rval)
+		printk(KERN_INFO "%s: failed registering " AD5820_NAME "\n",
+		       __func__);
+
+	return rval;

drivers/media/i2c/ad5820.c line 431

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+}
+
+static void __exit ad5820_exit(void)
+{
+	i2c_del_driver(&ad5820_i2c_driver);
+}
+
+
+module_init(ad5820_init);
+module_exit(ad5820_exit);

Use module_i2c_driver() instead.

Cheers
Marcus Folkesson

#2 lore raw

Hi!

...

Quoted 1 line

Use module_i2c_driver() instead.

Thanks for all the comments, I've fixed it up like this, will post new version soon.

Best regards,
Pavel

commit 97a793fb20be29e7ed217c007e8bf857f9854968

Author: Pavel <[email protected]>
Date:   Wed May 18 10:22:06 2016 +0200

Cleanups, as suggested by Marcus Folkesson

drivers/media/i2c/ad5820.c +10 -29
index b71cc11..7725829 100644
@@ -147,7 +147,6 @@ static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
 	struct ad5820_device *coil =
 		container_of(ctrl->handler, struct ad5820_device, ctrls);
 	u32 code;
-	int r = 0;
 
 	switch (ctrl->id) {
 	case V4L2_CID_FOCUS_ABSOLUTE:
@@ -165,7 +164,7 @@ static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
 		break;
 	}
 
-	return r;
+	return 0;
 }
 
 static const struct v4l2_ctrl_ops ad5820_ctrl_ops = {
@@ -245,8 +244,6 @@ static int ad5820_init_controls(struct ad5820_device *coil)
  */
 static int ad5820_registered(struct v4l2_subdev *subdev)
 {
-	static const int CHECK_VALUE = 0x3FF0;
-
 	struct ad5820_device *coil = to_ad5820_device(subdev);
 	struct i2c_client *client = v4l2_get_subdevdata(subdev);
 
@@ -364,16 +361,19 @@ static int ad5820_probe(struct i2c_client *client,
 	strcpy(coil->subdev.name, "ad5820 focus");
 
 	ret = media_entity_pads_init(&coil->subdev.entity, 0, NULL);
-	if (ret < 0) {
-		kfree(coil);
-		return ret;
-	}
+	if (ret < 0)
+		goto free;
 
 	ret = v4l2_async_register_subdev(&coil->subdev);
 	if (ret < 0)
-		kfree(coil);
+		goto cleanup;
 
 	return ret;
+cleanup:
+	media_entity_cleanup(&coil->subdev.entity);
+free:
+	kfree(coil);
+	return ret;
 }
 
 static int __exit ad5820_remove(struct i2c_client *client)
@@ -409,26 +409,7 @@ static struct i2c_driver ad5820_i2c_driver = {
 	.id_table	= ad5820_id_table,
 };
 
-static int __init ad5820_init(void)
-{
-	int rval;
-
-	rval = i2c_add_driver(&ad5820_i2c_driver);
-	if (rval)
-		printk(KERN_INFO "%s: failed registering " AD5820_NAME "\n",
-		       __func__);
-
-	return rval;
-}
-
-static void __exit ad5820_exit(void)
-{
-	i2c_del_driver(&ad5820_i2c_driver);
-}
-
-
-module_init(ad5820_init);
-module_exit(ad5820_exit);
+module_i2c_driver(ad5820_i2c_driver);
 
 MODULE_AUTHOR("Tuukka Toivonen");
 MODULE_DESCRIPTION("AD5820 camera lens driver");
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#3 lore raw

PATCH v2 1/1 support for AD5820 camera auto-focus coil

In reply to Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe

I think it is ready. Please apply :-).

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +416 -0

416 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#4 lore raw

Hi,

Quoted 65 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe

I think it is ready. Please apply :-).

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
  	  To compile this driver as a module, choose M here: the
  	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
  config VIDEO_SAA7110
  	tristate "Philips SAA7110 video decoder"
  	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
  obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
  obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
  obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
  obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
  obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
  obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +19 -0
new file mode 100644
index 0000000..7725829
@@ -0,0 +1,416 @@
+/*
+ * drivers/media/i2c/ad5820.c
+ *
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * Copyright (C) 2008 Nokia Corporation
+ * Copyright (C) 2007 Texas Instruments
+ * Copyright (C) 2016 Pavel Machek <[email protected]>
+ *
+ * Contact: Tuukka Toivonen
+ *          Sakari Ailus
+ *
+ * Based on af_d88.c by Texas Instruments.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but

drivers/media/i2c/ad5820.c line 29

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ */
+

Remove FSF address from the above.

drivers/media/i2c/ad5820.c line 40

Quoted 11 lines
drivers/media/i2c/ad5820.c new file +11 -0
+#include <linux/module.h>
+#include <linux/errno.h>
+#include <linux/i2c.h>
+#include <linux/slab.h>
+#include <linux/sched.h>
+#include <linux/delay.h>
+#include <linux/bitops.h>
+#include <linux/kernel.h>
+#include <linux/regulator/consumer.h>
+
+#include <media/ad5820.h>

drivers/media/i2c/ad5820.c:40:26: fatal error: media/ad5820.h: No such file or directory

Quoted 71 lines
drivers/media/i2c/ad5820.c new file +71 -0
+#include <media/v4l2-device.h>
+
+#define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
+#define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
+
+/**
+ * @brief I2C write using i2c_transfer().
+ * @param coil - the driver data structure
+ * @param data - register value to be written
+ * @returns nonnegative on success, negative if failed
+ */
+static int ad5820_write(struct ad5820_device *coil, u16 data)
+{
+	struct i2c_client *client = v4l2_get_subdevdata(&coil->subdev);
+	struct i2c_msg msg;
+	int r;
+
+	if (!client->adapter)
+		return -ENODEV;
+
+	data = cpu_to_be16(data);
+	msg.addr  = client->addr;
+	msg.flags = 0;
+	msg.len   = 2;
+	msg.buf   = (u8 *)&data;
+
+	r = i2c_transfer(client->adapter, &msg, 1);
+	if (r < 0) {
+		dev_err(&client->dev, "write failed, error %d\n", r);
+		return r;
+	}
+
+	return 0;
+}
+
+/*
+ * Calculate status word and write it to the device based on current
+ * values of V4L2 controls. It is assumed that the stored V4L2 control
+ * values are properly limited and rounded.
+ */
+static int ad5820_update_hw(struct ad5820_device *coil)
+{
+	u16 status;
+
+	status = RAMP_US_TO_CODE(coil->focus_ramp_time);
+	status |= coil->focus_ramp_mode
+		? AD5820_RAMP_MODE_64_16 : AD5820_RAMP_MODE_LINEAR;
+	status |= coil->focus_absolute << AD5820_DAC_SHIFT;
+
+	if (coil->standby)
+		status |= AD5820_POWER_DOWN;
+
+	return ad5820_write(coil, status);
+}
+
+/*
+ * Power handling
+ */
+static int ad5820_power_off(struct ad5820_device *coil, int standby)
+{
+	int ret = 0;
+
+	/*
+	 * Go to standby first as real power off my be denied by the hardware
+	 * (single power line control for both coil and sensor).
+	 */
+	if (standby) {
+		coil->standby = 1;
+		ret = ad5820_update_hw(coil);
+	}
+

drivers/media/i2c/ad5820.c line 121

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	ret |= regulator_disable(coil->vana);
+
+	return ret;
+}
+
+static int ad5820_power_on(struct ad5820_device *coil, int restore)
+{
+	int ret;
+
+	printk("ad5820_power_on: 1\n");

Some remnants from testing?

Quoted 43 lines
drivers/media/i2c/ad5820.c new file +43 -0
+	ret = regulator_enable(coil->vana);
+	if (ret < 0)
+		return ret;
+
+	if (restore) {
+		/* Restore the hardware settings. */
+		coil->standby = 0;
+		ret = ad5820_update_hw(coil);
+		if (ret)
+			goto fail;
+	}
+	return 0;
+
+fail:
+	coil->standby = 1;
+	regulator_disable(coil->vana);
+
+	return ret;
+}
+
+/*
+ * V4L2 controls
+ */
+static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
+{
+	struct ad5820_device *coil =
+		container_of(ctrl->handler, struct ad5820_device, ctrls);
+	u32 code;
+
+	switch (ctrl->id) {
+	case V4L2_CID_FOCUS_ABSOLUTE:
+		coil->focus_absolute = ctrl->val;
+		return ad5820_update_hw(coil);
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+		code = RAMP_US_TO_CODE(ctrl->val);
+		ctrl->val = CODE_TO_RAMP_US(code);
+		coil->focus_ramp_time = ctrl->val;
+		break;
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+		coil->focus_ramp_mode = ctrl->val;
+		break;

drivers/media/i2c/ad5820.c line 174

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	}
+
+	return 0;
+}
+
+static const struct v4l2_ctrl_ops ad5820_ctrl_ops = {
+	.s_ctrl = ad5820_set_ctrl,
+};
+
+static const char *ad5820_focus_menu[] = {

static const char * const ?

Quoted 56 lines
drivers/media/i2c/ad5820.c new file +56 -0
+	"Linear ramp",
+	"64/16 ramp",
+};
+
+static const struct v4l2_ctrl_config ad5820_ctrls[] = {
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
+		.type		= V4L2_CTRL_TYPE_INTEGER,
+		.name		= "Focus ramping time [us]",
+		.min		= 0,
+		.max		= 3200,
+		.step		= 50,
+		.def		= 0,
+		.flags		= 0,
+	},
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,
+		.type		= V4L2_CTRL_TYPE_MENU,
+		.name		= "Focus ramping mode",
+		.min		= 0,
+		.max		= ARRAY_SIZE(ad5820_focus_menu),
+		.step		= 0,
+		.def		= 0,
+		.flags		= 0,
+		.qmenu		= ad5820_focus_menu,
+	},
+};
+
+
+static int ad5820_init_controls(struct ad5820_device *coil)
+{
+	unsigned int i;
+
+	v4l2_ctrl_handler_init(&coil->ctrls, ARRAY_SIZE(ad5820_ctrls) + 1);
+
+	/*
+	 * V4L2_CID_FOCUS_ABSOLUTE
+	 *
+	 * Minimum current is 0 mA, maximum is 100 mA. Thus, 1 code is
+	 * equivalent to 100/1023 = 0.0978 mA. Nevertheless, we do not use [mA]
+	 * for focus position, because it is meaningless for user. Meaningful
+	 * would be to use focus distance or even its inverse, but since the
+	 * driver doesn't have sufficiently knowledge to do the conversion, we
+	 * will just use abstract codes here. In any case, smaller value = focus
+	 * position farther from camera. The default zero value means focus at
+	 * infinity, and also least current consumption.
+	 */
+	v4l2_ctrl_new_std(&coil->ctrls, &ad5820_ctrl_ops,
+			  V4L2_CID_FOCUS_ABSOLUTE, 0, 1023, 1, 0);
+
+	/* V4L2_CID_TEST_PATTERN and V4L2_CID_MODE_* */
+	for (i = 0; i < ARRAY_SIZE(ad5820_ctrls); ++i)
+		v4l2_ctrl_new_custom(&coil->ctrls, &ad5820_ctrls[i], NULL);
+

drivers/media/i2c/ad5820.c line 240

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	if (coil->ctrls.error)
+		return coil->ctrls.error;
+
+	coil->focus_absolute = 0;
+	coil->focus_ramp_time = 0;
+	coil->focus_ramp_mode = 0;
+
+	coil->subdev.ctrl_handler = &coil->ctrls;
+	return 0;
+}

please add a new line before return.

Quoted 103 lines
drivers/media/i2c/ad5820.c new file +103 -0
+
+/*
+ * V4L2 subdev operations
+ */
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");
+	if (IS_ERR(coil->vana)) {
+		dev_err(&client->dev, "could not get regulator for vana\n");
+		return -ENODEV;
+	}
+
+	return ad5820_init_controls(coil);
+}
+
+static int
+ad5820_set_power(struct v4l2_subdev *subdev, int on)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	int ret = 0;
+
+	mutex_lock(&coil->power_lock);
+
+	/*
+	 * If the power count is modified from 0 to != 0 or from != 0 to 0,
+	 * update the power state.
+	 */
+	if (coil->power_count == !on) {
+		ret = on ? ad5820_power_on(coil, 1) : ad5820_power_off(coil, 1);
+		if (ret < 0)
+			goto done;
+	}
+
+	/* Update the power count. */
+	coil->power_count += on ? 1 : -1;
+	WARN_ON(coil->power_count < 0);
+
+done:
+	mutex_unlock(&coil->power_lock);
+	return ret;
+}
+
+static int ad5820_open(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 1);
+}
+
+static int ad5820_close(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 0);
+}
+
+static const struct v4l2_subdev_core_ops ad5820_core_ops = {
+	.s_power = ad5820_set_power,
+};
+
+static const struct v4l2_subdev_ops ad5820_ops = {
+	.core = &ad5820_core_ops,
+};
+
+static const struct v4l2_subdev_internal_ops ad5820_internal_ops = {
+	.registered = ad5820_registered,
+	.open = ad5820_open,
+	.close = ad5820_close,
+};
+
+/*
+ * I2C driver
+ */
+#ifdef CONFIG_PM
+
+static int ad5820_suspend(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_off(coil, 0);
+}
+
+static int ad5820_resume(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_on(coil, 1);
+}
+
+#else
+
+#define ad5820_suspend	NULL
+#define ad5820_resume	NULL
+

drivers/media/i2c/ad5820.c line 353

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+#endif /* CONFIG_PM */
+
+static int ad5820_probe(struct i2c_client *client,
+			const struct i2c_device_id *devid)
+{
+	struct ad5820_device *coil;
+	int ret = 0;
+
+	coil = kzalloc(sizeof(*coil), GFP_KERNEL);
+	if (coil == NULL)

if (!coil) ?

Quoted 14 lines
drivers/media/i2c/ad5820.c new file +14 -0
+		return -ENOMEM;
+
+	mutex_init(&coil->power_lock);
+
+	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
+	coil->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
+	coil->subdev.internal_ops = &ad5820_internal_ops;
+	strcpy(coil->subdev.name, "ad5820 focus");
+
+	ret = media_entity_pads_init(&coil->subdev.entity, 0, NULL);
+	if (ret < 0)
+		goto free;
+
+	ret = v4l2_async_register_subdev(&coil->subdev);

drivers/media/i2c/ad5820.c line 377

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	if (ret < 0)
+		goto cleanup;
+
+	return ret;
+cleanup:
+	media_entity_cleanup(&coil->subdev.entity);
+free:
+	kfree(coil);
+	return ret;
+}

new line before return, also I would put new lines before labels :)

drivers/media/i2c/ad5820.c line 390

Quoted 13 lines
drivers/media/i2c/ad5820.c new file +13 -0
+
+static int __exit ad5820_remove(struct i2c_client *client)
+{
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	v4l2_device_unregister_subdev(&coil->subdev);
+	v4l2_ctrl_handler_free(&coil->ctrls);
+	media_entity_cleanup(&coil->subdev.entity);
+	if (coil->vana)
+		regulator_put(coil->vana);
+
+	kfree(coil);

new line here

Quoted 17 lines
drivers/media/i2c/ad5820.c new file +16 -0
+	return 0;
+}
+
+static const struct i2c_device_id ad5820_id_table[] = {
+	{ AD5820_NAME, 0 },
+	{ }
+};
+MODULE_DEVICE_TABLE(i2c, ad5820_id_table);
+
+static SIMPLE_DEV_PM_OPS(ad5820_pm, ad5820_suspend, ad5820_resume);
+
+static struct i2c_driver ad5820_i2c_driver = {
+	.driver		= {
+		.name	= AD5820_NAME,
+		.pm	= &ad5820_pm,
+	},

drivers/media/i2c/ad5820.c line 416

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	.probe		= ad5820_probe,
+	.remove		= __exit_p(ad5820_remove),
+	.id_table	= ad5820_id_table,
+};
+
+module_i2c_driver(ad5820_i2c_driver);
+
+MODULE_AUTHOR("Tuukka Toivonen");
+MODULE_DESCRIPTION("AD5820 camera lens driver");
+MODULE_LICENSE("GPL");

Thanks,
Ivo

#5 lore raw

PATCH v3 1/1 support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe

v3: more cleanups, remove printk, add include

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +416 -0

416 lines not on this page · raw message

include/media/ad5820.h new file +70 -0

70 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#6 lore raw

Hi,

Quoted 65 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe

v3: more cleanups, remove printk, add include

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
  	  To compile this driver as a module, choose M here: the
  	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
  config VIDEO_SAA7110
  	tristate "Philips SAA7110 video decoder"
  	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
  obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
  obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
  obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
  obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
  obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
  obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +19 -0
new file mode 100644
index 0000000..7725829
@@ -0,0 +1,416 @@
+/*
+ * drivers/media/i2c/ad5820.c
+ *
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * Copyright (C) 2008 Nokia Corporation
+ * Copyright (C) 2007 Texas Instruments
+ * Copyright (C) 2016 Pavel Machek <[email protected]>
+ *
+ * Contact: Tuukka Toivonen
+ *          Sakari Ailus
+ *
+ * Based on af_d88.c by Texas Instruments.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but

drivers/media/i2c/ad5820.c line 29

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ */
+

At least on my machine checkpatch.pl complains about FSF address.

drivers/media/i2c/ad5820.c line 35

Quoted 6 lines
drivers/media/i2c/ad5820.c new file +6 -0
+#include <linux/module.h>
+#include <linux/errno.h>
+#include <linux/i2c.h>
+#include <linux/slab.h>
+#include <linux/sched.h>
+#include <linux/delay.h>

Doesn't seem to get used.

Quoted 205 lines
drivers/media/i2c/ad5820.c new file +205 -0
+#include <linux/bitops.h>
+#include <linux/kernel.h>
+#include <linux/regulator/consumer.h>
+
+#include <media/ad5820.h>
+#include <media/v4l2-device.h>
+
+#define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
+#define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
+
+/**
+ * @brief I2C write using i2c_transfer().
+ * @param coil - the driver data structure
+ * @param data - register value to be written
+ * @returns nonnegative on success, negative if failed
+ */
+static int ad5820_write(struct ad5820_device *coil, u16 data)
+{
+	struct i2c_client *client = v4l2_get_subdevdata(&coil->subdev);
+	struct i2c_msg msg;
+	int r;
+
+	if (!client->adapter)
+		return -ENODEV;
+
+	data = cpu_to_be16(data);
+	msg.addr  = client->addr;
+	msg.flags = 0;
+	msg.len   = 2;
+	msg.buf   = (u8 *)&data;
+
+	r = i2c_transfer(client->adapter, &msg, 1);
+	if (r < 0) {
+		dev_err(&client->dev, "write failed, error %d\n", r);
+		return r;
+	}
+
+	return 0;
+}
+
+/*
+ * Calculate status word and write it to the device based on current
+ * values of V4L2 controls. It is assumed that the stored V4L2 control
+ * values are properly limited and rounded.
+ */
+static int ad5820_update_hw(struct ad5820_device *coil)
+{
+	u16 status;
+
+	status = RAMP_US_TO_CODE(coil->focus_ramp_time);
+	status |= coil->focus_ramp_mode
+		? AD5820_RAMP_MODE_64_16 : AD5820_RAMP_MODE_LINEAR;
+	status |= coil->focus_absolute << AD5820_DAC_SHIFT;
+
+	if (coil->standby)
+		status |= AD5820_POWER_DOWN;
+
+	return ad5820_write(coil, status);
+}
+
+/*
+ * Power handling
+ */
+static int ad5820_power_off(struct ad5820_device *coil, int standby)
+{
+	int ret = 0;
+
+	/*
+	 * Go to standby first as real power off my be denied by the hardware
+	 * (single power line control for both coil and sensor).
+	 */
+	if (standby) {
+		coil->standby = 1;
+		ret = ad5820_update_hw(coil);
+	}
+
+	ret |= regulator_disable(coil->vana);
+
+	return ret;
+}
+
+static int ad5820_power_on(struct ad5820_device *coil, int restore)
+{
+	int ret;
+
+	printk("ad5820_power_on: 1\n");
+	ret = regulator_enable(coil->vana);
+	if (ret < 0)
+		return ret;
+
+	if (restore) {
+		/* Restore the hardware settings. */
+		coil->standby = 0;
+		ret = ad5820_update_hw(coil);
+		if (ret)
+			goto fail;
+	}
+	return 0;
+
+fail:
+	coil->standby = 1;
+	regulator_disable(coil->vana);
+
+	return ret;
+}
+
+/*
+ * V4L2 controls
+ */
+static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
+{
+	struct ad5820_device *coil =
+		container_of(ctrl->handler, struct ad5820_device, ctrls);
+	u32 code;
+
+	switch (ctrl->id) {
+	case V4L2_CID_FOCUS_ABSOLUTE:
+		coil->focus_absolute = ctrl->val;
+		return ad5820_update_hw(coil);
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+		code = RAMP_US_TO_CODE(ctrl->val);
+		ctrl->val = CODE_TO_RAMP_US(code);
+		coil->focus_ramp_time = ctrl->val;
+		break;
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+		coil->focus_ramp_mode = ctrl->val;
+		break;
+	}
+
+	return 0;
+}
+
+static const struct v4l2_ctrl_ops ad5820_ctrl_ops = {
+	.s_ctrl = ad5820_set_ctrl,
+};
+
+static const char *ad5820_focus_menu[] = {
+	"Linear ramp",
+	"64/16 ramp",
+};
+
+static const struct v4l2_ctrl_config ad5820_ctrls[] = {
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
+		.type		= V4L2_CTRL_TYPE_INTEGER,
+		.name		= "Focus ramping time [us]",
+		.min		= 0,
+		.max		= 3200,
+		.step		= 50,
+		.def		= 0,
+		.flags		= 0,
+	},
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,
+		.type		= V4L2_CTRL_TYPE_MENU,
+		.name		= "Focus ramping mode",
+		.min		= 0,
+		.max		= ARRAY_SIZE(ad5820_focus_menu),
+		.step		= 0,
+		.def		= 0,
+		.flags		= 0,
+		.qmenu		= ad5820_focus_menu,
+	},
+};
+
+
+static int ad5820_init_controls(struct ad5820_device *coil)
+{
+	unsigned int i;
+
+	v4l2_ctrl_handler_init(&coil->ctrls, ARRAY_SIZE(ad5820_ctrls) + 1);
+
+	/*
+	 * V4L2_CID_FOCUS_ABSOLUTE
+	 *
+	 * Minimum current is 0 mA, maximum is 100 mA. Thus, 1 code is
+	 * equivalent to 100/1023 = 0.0978 mA. Nevertheless, we do not use [mA]
+	 * for focus position, because it is meaningless for user. Meaningful
+	 * would be to use focus distance or even its inverse, but since the
+	 * driver doesn't have sufficiently knowledge to do the conversion, we
+	 * will just use abstract codes here. In any case, smaller value = focus
+	 * position farther from camera. The default zero value means focus at
+	 * infinity, and also least current consumption.
+	 */
+	v4l2_ctrl_new_std(&coil->ctrls, &ad5820_ctrl_ops,
+			  V4L2_CID_FOCUS_ABSOLUTE, 0, 1023, 1, 0);
+
+	/* V4L2_CID_TEST_PATTERN and V4L2_CID_MODE_* */
+	for (i = 0; i < ARRAY_SIZE(ad5820_ctrls); ++i)
+		v4l2_ctrl_new_custom(&coil->ctrls, &ad5820_ctrls[i], NULL);
+
+	if (coil->ctrls.error)
+		return coil->ctrls.error;
+
+	coil->focus_absolute = 0;
+	coil->focus_ramp_time = 0;
+	coil->focus_ramp_mode = 0;
+
+	coil->subdev.ctrl_handler = &coil->ctrls;
+	return 0;
+}

drivers/media/i2c/ad5820.c line 250

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+
+/*
+ * V4L2 subdev operations
+ */
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");

devm_regulator_get()?

Quoted 92 lines
drivers/media/i2c/ad5820.c new file +92 -0
+	if (IS_ERR(coil->vana)) {
+		dev_err(&client->dev, "could not get regulator for vana\n");
+		return -ENODEV;
+	}
+
+	return ad5820_init_controls(coil);
+}
+
+static int
+ad5820_set_power(struct v4l2_subdev *subdev, int on)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	int ret = 0;
+
+	mutex_lock(&coil->power_lock);
+
+	/*
+	 * If the power count is modified from 0 to != 0 or from != 0 to 0,
+	 * update the power state.
+	 */
+	if (coil->power_count == !on) {
+		ret = on ? ad5820_power_on(coil, 1) : ad5820_power_off(coil, 1);
+		if (ret < 0)
+			goto done;
+	}
+
+	/* Update the power count. */
+	coil->power_count += on ? 1 : -1;
+	WARN_ON(coil->power_count < 0);
+
+done:
+	mutex_unlock(&coil->power_lock);
+	return ret;
+}
+
+static int ad5820_open(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 1);
+}
+
+static int ad5820_close(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 0);
+}
+
+static const struct v4l2_subdev_core_ops ad5820_core_ops = {
+	.s_power = ad5820_set_power,
+};
+
+static const struct v4l2_subdev_ops ad5820_ops = {
+	.core = &ad5820_core_ops,
+};
+
+static const struct v4l2_subdev_internal_ops ad5820_internal_ops = {
+	.registered = ad5820_registered,
+	.open = ad5820_open,
+	.close = ad5820_close,
+};
+
+/*
+ * I2C driver
+ */
+#ifdef CONFIG_PM
+
+static int ad5820_suspend(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_off(coil, 0);
+}
+
+static int ad5820_resume(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_on(coil, 1);
+}
+
+#else
+
+#define ad5820_suspend	NULL
+#define ad5820_resume	NULL

drivers/media/i2c/ad5820.c line 352

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+
+#endif /* CONFIG_PM */
+
+static int ad5820_probe(struct i2c_client *client,
+			const struct i2c_device_id *devid)
+{
+	struct ad5820_device *coil;
+	int ret = 0;
+
+	coil = kzalloc(sizeof(*coil), GFP_KERNEL);

devm_kzalloc() ?

Quoted 104 lines
drivers/media/i2c/ad5820.c new file +64 -0
+	if (coil == NULL)
+		return -ENOMEM;
+
+	mutex_init(&coil->power_lock);
+
+	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
+	coil->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
+	coil->subdev.internal_ops = &ad5820_internal_ops;
+	strcpy(coil->subdev.name, "ad5820 focus");
+
+	ret = media_entity_pads_init(&coil->subdev.entity, 0, NULL);
+	if (ret < 0)
+		goto free;
+
+	ret = v4l2_async_register_subdev(&coil->subdev);
+	if (ret < 0)
+		goto cleanup;
+
+	return ret;
+cleanup:
+	media_entity_cleanup(&coil->subdev.entity);
+free:
+	kfree(coil);
+	return ret;
+}
+
+static int __exit ad5820_remove(struct i2c_client *client)
+{
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	v4l2_device_unregister_subdev(&coil->subdev);
+	v4l2_ctrl_handler_free(&coil->ctrls);
+	media_entity_cleanup(&coil->subdev.entity);
+	if (coil->vana)
+		regulator_put(coil->vana);
+
+	kfree(coil);
+	return 0;
+}
+
+static const struct i2c_device_id ad5820_id_table[] = {
+	{ AD5820_NAME, 0 },
+	{ }
+};
+MODULE_DEVICE_TABLE(i2c, ad5820_id_table);
+
+static SIMPLE_DEV_PM_OPS(ad5820_pm, ad5820_suspend, ad5820_resume);
+
+static struct i2c_driver ad5820_i2c_driver = {
+	.driver		= {
+		.name	= AD5820_NAME,
+		.pm	= &ad5820_pm,
+	},
+	.probe		= ad5820_probe,
+	.remove		= __exit_p(ad5820_remove),
+	.id_table	= ad5820_id_table,
+};
+
+module_i2c_driver(ad5820_i2c_driver);
+
+MODULE_AUTHOR("Tuukka Toivonen");
+MODULE_DESCRIPTION("AD5820 camera lens driver");
+MODULE_LICENSE("GPL");
include/media/ad5820.h new file +34 -0
new file mode 100644
index 0000000..f5a1565
@@ -0,0 +1,70 @@
+/*
+ * include/media/ad5820.h
+ *
+ * Copyright (C) 2008 Nokia Corporation
+ * Copyright (C) 2007 Texas Instruments
+ *
+ * Contact: Tuukka Toivonen <[email protected]>
+ *          Sakari Ailus <[email protected]>
+ *
+ * Based on af_d88.c by Texas Instruments.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ */
+
+#ifndef AD5820_H
+#define AD5820_H
+
+#include <linux/i2c.h>
+#include <linux/mutex.h>
+#include <linux/videodev2.h>
+
+#include <media/v4l2-ctrls.h>

include/media/ad5820.h line 44

Quoted 10 lines
include/media/ad5820.h new file +10 -0
+#include <media/v4l2-subdev.h>
+
+struct regulator;
+
+#define AD5820_NAME		"ad5820"
+#define AD5820_I2C_ADDR		(0x18 >> 1)
+
+/* Register definitions */
+#define AD5820_POWER_DOWN		(1 << 15)
+#define AD5820_DAC_SHIFT		4

Do those defines really belong here? Isn't it better if they are moved to ad5820.c?

Quoted 15 lines
include/media/ad5820.h new file +15 -0
+#define AD5820_RAMP_MODE_LINEAR		(0 << 3)
+#define AD5820_RAMP_MODE_64_16		(1 << 3)
+
+struct ad5820_platform_data {
+	int (*set_xshutdown)(struct v4l2_subdev *subdev, int set);
+};
+
+#define to_ad5820_device(sd)	container_of(sd, struct ad5820_device, subdev)
+
+struct ad5820_device {
+	struct v4l2_subdev subdev;
+	struct ad5820_platform_data *platform_data;
+	struct regulator *vana;
+
+	struct v4l2_ctrl_handler ctrls;

include/media/ad5820.h line 69

Quoted 10 lines
include/media/ad5820.h new file +10 -0
+	u32 focus_absolute;
+	u32 focus_ramp_time;
+	u32 focus_ramp_mode;
+
+	struct mutex power_lock;
+	int power_count;
+
+	int standby : 1;
+};
+

The same for struct ad5820_device, is it really part of the public API?

Quoted 4 lines
include/media/ad5820.h new file +1 -0
+#endif /* AD5820_H */
#7 lore raw
Quoted 38 lines · On Saturday 21 May 2016 14:43:43 Ivaylo Dimitrov wrote:
Quoted 38 lines
include/media/ad5820.h new file +32 -0
new file mode 100644
index 0000000..f5a1565
@@ -0,0 +1,70 @@
+/*
+ * include/media/ad5820.h
+ *
+ * Copyright (C) 2008 Nokia Corporation
+ * Copyright (C) 2007 Texas Instruments
+ *
+ * Contact: Tuukka Toivonen <[email protected]>
+ *          Sakari Ailus <[email protected]>
+ *
+ * Based on af_d88.c by Texas Instruments.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ */
+
+#ifndef AD5820_H
+#define AD5820_H
+
+#include <linux/i2c.h>
+#include <linux/mutex.h>
+#include <linux/videodev2.h>
Quoted 8 lines

include/media/ad5820.h line 40

Quoted 8 lines
include/media/ad5820.h new file +8 -0
+
+#include <media/v4l2-ctrls.h>
+#include <media/v4l2-subdev.h>
+
+struct regulator;
+
+#define AD5820_NAME		"ad5820"
+#define AD5820_I2C_ADDR		(0x18 >> 1)

Maybe write I2C address is more readable form? What is reason such bit shift format?

Quoted 6 lines

include/media/ad5820.h line 44

Quoted 3 lines
include/media/ad5820.h new file +3 -0
+/* Register definitions */
+#define AD5820_POWER_DOWN		(1 << 15)
+#define AD5820_DAC_SHIFT		4

Do those defines really belong here? Isn't it better if they are moved to ad5820.c?

For me it looks like this is private for ad5820.c.

Quoted 6 lines

include/media/ad5820.h line 50

Quoted 6 lines
include/media/ad5820.h new file +6 -0
+#define AD5820_RAMP_MODE_LINEAR		(0 << 3)
+#define AD5820_RAMP_MODE_64_16		(1 << 3)
+
+struct ad5820_platform_data {
+	int (*set_xshutdown)(struct v4l2_subdev *subdev, int set);
+};

This is for legacy board code support right? We need DT support for N900 as legacy board code is going to be deleted.

Quoted 12 lines
Quoted 12 lines
include/media/ad5820.h new file +12 -0
+#define to_ad5820_device(sd)	container_of(sd, struct ad5820_device, subdev)
+
+struct ad5820_device {
+	struct v4l2_subdev subdev;
+	struct ad5820_platform_data *platform_data;
+	struct regulator *vana;
+
+	struct v4l2_ctrl_handler ctrls;
+	u32 focus_absolute;
+	u32 focus_ramp_time;
+	u32 focus_ramp_mode;
+
Quoted 8 lines

include/media/ad5820.h line 69

Quoted 6 lines
include/media/ad5820.h new file +6 -0
+	struct mutex power_lock;
+	int power_count;
+
+	int standby : 1;
+};
+

The same for struct ad5820_device, is it really part of the public API?

Yes, this is also private for ad5820.c

Quoted 4 lines
Quoted 4 lines
include/media/ad5820.h new file +1 -0
+#endif /* AD5820_H */
Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
#8 lore raw
In reply to Ivaylo Dimitrov

Hi!

Quoted 8 lines

drivers/media/i2c/ad5820.c line 250

Quoted 6 lines
drivers/media/i2c/ad5820.c new file +6 -0
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");

devm_regulator_get()?

I'd rather avoid devm_ here. Driver is simple enough to allow it.

Quoted 19 lines
Quoted 19 lines
include/media/ad5820.h new file +19 -0
+#define AD5820_RAMP_MODE_LINEAR		(0 << 3)
+#define AD5820_RAMP_MODE_64_16		(1 << 3)
+
+struct ad5820_platform_data {
+	int (*set_xshutdown)(struct v4l2_subdev *subdev, int set);
+};
+
+#define to_ad5820_device(sd)	container_of(sd, struct ad5820_device, subdev)
+
+struct ad5820_device {
+	struct v4l2_subdev subdev;
+	struct ad5820_platform_data *platform_data;
+	struct regulator *vana;
+
+	struct v4l2_ctrl_handler ctrls;
+	u32 focus_absolute;
+	u32 focus_ramp_time;
+	u32 focus_ramp_mode;
+
Quoted 8 lines

include/media/ad5820.h line 69

Quoted 6 lines
include/media/ad5820.h new file +6 -0
+	struct mutex power_lock;
+	int power_count;
+
+	int standby : 1;
+};
+

The same for struct ad5820_device, is it really part of the public API?

Let me check what can be done with it.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#9 lore raw
Quoted 11 lines · Pavel Machek

Hi!

Quoted 8 lines

drivers/media/i2c/ad5820.c line 250

Quoted 6 lines
drivers/media/i2c/ad5820.c new file +6 -0
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");

devm_regulator_get()?

Quoted 2 lines

I'd rather avoid devm_ here. Driver is simple enough to allow it.

Now thinking about it, what would happen here if regulator_get() returns -EPROBE_DEFER? Wouldn't it be better to move regulator_get to the probe() function, something like:

static int ad5820_probe(struct i2c_client *client,
const struct i2c_device_id *devid)

{
	struct ad5820_device *coil;
	int ret = 0;

	coil = devm_kzalloc(sizeof(*coil), GFP_KERNEL);
	if (coil == NULL)
		return -ENOMEM;

	coil->vana = devm_regulator_get(&client->dev, NULL);
	if (IS_ERR(coil->vana)) {
		ret = PTR_ERR(coil->vana);
		if (ret != -EPROBE_DEFER)
			dev_err(&client->dev, "could not get regulator for vana\n");
		return ret;
	}

	mutex_init(&coil->power_lock);

...

with the appropriate changes to remove() because of the devm API usage.

Quoted 31 lines
Quoted 19 lines
Quoted 19 lines
include/media/ad5820.h new file +19 -0
+#define AD5820_RAMP_MODE_LINEAR		(0 << 3)
+#define AD5820_RAMP_MODE_64_16		(1 << 3)
+
+struct ad5820_platform_data {
+	int (*set_xshutdown)(struct v4l2_subdev *subdev, int set);
+};
+
+#define to_ad5820_device(sd)	container_of(sd, struct ad5820_device, subdev)
+
+struct ad5820_device {
+	struct v4l2_subdev subdev;
+	struct ad5820_platform_data *platform_data;
+	struct regulator *vana;
+
+	struct v4l2_ctrl_handler ctrls;
+	u32 focus_absolute;
+	u32 focus_ramp_time;
+	u32 focus_ramp_mode;
+
Quoted 8 lines

include/media/ad5820.h line 69

Quoted 6 lines
include/media/ad5820.h new file +6 -0
+	struct mutex power_lock;
+	int power_count;
+
+	int standby : 1;
+};
+

The same for struct ad5820_device, is it really part of the public API?

Let me check what can be done with it.
Pavel

#10 lore raw

Hi!

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

devm_regulator_get()?

I'd rather avoid devm_ here. Driver is simple enough to allow it.

Now thinking about it, what would happen here if regulator_get() returns -EPROBE_DEFER? Wouldn't it be better to move regulator_get to the probe() function, something like:

Ok, I can do it.

Oh, and don't try to complain about newlines before returns. It looks better this way.

Quoted 19 lines

static int ad5820_probe(struct i2c_client *client,
const struct i2c_device_id *devid)

{
	struct ad5820_device *coil;
	int ret = 0;

	coil = devm_kzalloc(sizeof(*coil), GFP_KERNEL);
	if (coil == NULL)
		return -ENOMEM;

	coil->vana = devm_regulator_get(&client->dev, NULL);
	if (IS_ERR(coil->vana)) {
		ret = PTR_ERR(coil->vana);
		if (ret != -EPROBE_DEFER)
			dev_err(&client->dev, "could not get regulator for vana\n");
		return ret;
	}

	mutex_init(&coil->power_lock);
Quoted 4 lines

...

with the appropriate changes to remove() because of the devm API
usage.

Something like this?

drivers/media/i2c/ad5820.c +10 -18
index f956bd3..f871366 100644
@@ -8,7 +8,7 @@
  * Copyright (C) 2016 Pavel Machek <[email protected]>
  *
  * Contact: Tuukka Toivonen
- *          Sakari Ailus
+ *	    Sakari Ailus
  *
  * Based on af_d88.c by Texas Instruments.
  *
@@ -263,13 +263,6 @@ static int ad5820_init_controls(struct ad5820_device *coil)
 static int ad5820_registered(struct v4l2_subdev *subdev)
 {
 	struct ad5820_device *coil = to_ad5820_device(subdev);
-	struct i2c_client *client = v4l2_get_subdevdata(subdev);
-
-	coil->vana = regulator_get(&client->dev, "VANA");
-	if (IS_ERR(coil->vana)) {
-		dev_err(&client->dev, "could not get regulator for vana\n");
-		return -ENODEV;
-	}
 
 	return ad5820_init_controls(coil);
 }
@@ -367,10 +360,18 @@ static int ad5820_probe(struct i2c_client *client,
 	struct ad5820_device *coil;
 	int ret = 0;
 
-	coil = kzalloc(sizeof(*coil), GFP_KERNEL);
+	coil = devm_kzalloc(sizeof(*coil), GFP_KERNEL);
 	if (!coil)
 		return -ENOMEM;
 
+	coil->vana = devm_regulator_get(&client->dev, NULL);
+	if (IS_ERR(coil->vana)) {
+		ret = PTR_ERR(coil->vana);
+		if (ret != -EPROBE_DEFER)
+			dev_err(&client->dev, "could not get regulator for vana\n");
+		return ret;
+	}
+	
 	mutex_init(&coil->power_lock);
 
 	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
@@ -390,10 +391,6 @@ static int ad5820_probe(struct i2c_client *client,
 
 cleanup:
 	media_entity_cleanup(&coil->subdev.entity);
-
-free:
-	kfree(coil);
-
 	return ret;
 }
 
@@ -405,11 +402,6 @@ static int __exit ad5820_remove(struct i2c_client *client)
 	v4l2_device_unregister_subdev(&coil->subdev);
 	v4l2_ctrl_handler_free(&coil->ctrls);
 	media_entity_cleanup(&coil->subdev.entity);
-	if (coil->vana)
-		regulator_put(coil->vana);
-
-	kfree(coil);
-
 	return 0;
 }
 
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#11 lore raw
Quoted 7 lines · Pavel Machek

Hi!

Quoted 5 lines
Quoted 4 lines
Quoted 1 line

devm_regulator_get()?

I'd rather avoid devm_ here. Driver is simple enough to allow it.

Quoted 9 lines
Quoted 3 lines

Now thinking about it, what would happen here if regulator_get() returns -EPROBE_DEFER? Wouldn't it be better to move regulator_get to the probe() function, something like:

Ok, I can do it.

Oh, and don't try to complain about newlines before returns. It looks better this way.

All I complain about is missing empty line before a final return at the end of a function :). I guess it is a matter of preference though.

Quoted 18 lines
Quoted 18 lines

static int ad5820_probe(struct i2c_client *client,
const struct i2c_device_id *devid)

{
	struct ad5820_device *coil;
	int ret = 0;

	coil = devm_kzalloc(sizeof(*coil), GFP_KERNEL);
	if (coil == NULL)
		return -ENOMEM;

	coil->vana = devm_regulator_get(&client->dev, NULL);
	if (IS_ERR(coil->vana)) {
		ret = PTR_ERR(coil->vana);
		if (ret != -EPROBE_DEFER)
			dev_err(&client->dev, "could not get regulator for vana\n");
		return ret;
	}
Quoted 8 lines
Quoted 5 lines
	mutex_init(&coil->power_lock);

...

with the appropriate changes to remove() because of the devm API
usage.

Something like this?

Didn't try to apply it, but yes, looks right. Besides the missing mutex_destroy(&coil->power_lock); pointed out by Sakari.

Quoted 70 lines
drivers/media/i2c/ad5820.c +10 -18
index f956bd3..f871366 100644
@@ -8,7 +8,7 @@
   * Copyright (C) 2016 Pavel Machek <[email protected]>
   *
   * Contact: Tuukka Toivonen
- *          Sakari Ailus
+ *	    Sakari Ailus
   *
   * Based on af_d88.c by Texas Instruments.
   *
@@ -263,13 +263,6 @@ static int ad5820_init_controls(struct ad5820_device *coil)
  static int ad5820_registered(struct v4l2_subdev *subdev)
  {
  	struct ad5820_device *coil = to_ad5820_device(subdev);
-	struct i2c_client *client = v4l2_get_subdevdata(subdev);
-
-	coil->vana = regulator_get(&client->dev, "VANA");
-	if (IS_ERR(coil->vana)) {
-		dev_err(&client->dev, "could not get regulator for vana\n");
-		return -ENODEV;
-	}
 
  	return ad5820_init_controls(coil);
  }
@@ -367,10 +360,18 @@ static int ad5820_probe(struct i2c_client *client,
  	struct ad5820_device *coil;
  	int ret = 0;
 
-	coil = kzalloc(sizeof(*coil), GFP_KERNEL);
+	coil = devm_kzalloc(sizeof(*coil), GFP_KERNEL);
  	if (!coil)
  		return -ENOMEM;
 
+	coil->vana = devm_regulator_get(&client->dev, NULL);
+	if (IS_ERR(coil->vana)) {
+		ret = PTR_ERR(coil->vana);
+		if (ret != -EPROBE_DEFER)
+			dev_err(&client->dev, "could not get regulator for vana\n");
+		return ret;
+	}
+	
  	mutex_init(&coil->power_lock);
 
  	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
@@ -390,10 +391,6 @@ static int ad5820_probe(struct i2c_client *client,
 
  cleanup:
  	media_entity_cleanup(&coil->subdev.entity);
-
-free:
-	kfree(coil);
-
  	return ret;
  }
 
@@ -405,11 +402,6 @@ static int __exit ad5820_remove(struct i2c_client *client)
  	v4l2_device_unregister_subdev(&coil->subdev);
  	v4l2_ctrl_handler_free(&coil->ctrls);
  	media_entity_cleanup(&coil->subdev.entity);
-	if (coil->vana)
-		regulator_put(coil->vana);
-
-	kfree(coil);
-
  	return 0;
  }
 
#12 lore raw

PATCH v4 1/1 support for AD5820 camera auto-focus coil

In reply to Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
v4: remove header file.

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +438 -0

438 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#13 lore raw

Hi Pavel,

Thanks for your continued work on this! :-)

Some quite minor comments below. I think we're good then.

Quoted 47 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
v4: remove header file.

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +1 -0
new file mode 100644
index 0000000..f956bd3
@@ -0,0 +1,438 @@
+/*

drivers/media/i2c/ad5820.c line 11

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+ * drivers/media/i2c/ad5820.c
+ *
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * Copyright (C) 2008 Nokia Corporation
+ * Copyright (C) 2007 Texas Instruments
+ * Copyright (C) 2016 Pavel Machek <[email protected]>
+ *
+ * Contact: Tuukka Toivonen
+ *          Sakari Ailus

Could you put the e-mail addresses back, please?

Tuukka's e-mail is tuukkat76 at gmail.com .

Quoted 8 lines
drivers/media/i2c/ad5820.c new file +8 -0
+ *
+ * Based on af_d88.c by Texas Instruments.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but

drivers/media/i2c/ad5820.c line 29

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ */
+
+#include <linux/module.h>
+#include <linux/errno.h>
+#include <linux/i2c.h>
+#include <linux/kernel.h>
+#include <linux/regulator/consumer.h>

Alphabetical order would be nice. The same below.

Quoted 28 lines
drivers/media/i2c/ad5820.c new file +28 -0
+
+#include <media/v4l2-device.h>
+#include <media/v4l2-ctrls.h>
+#include <media/v4l2-subdev.h>
+
+#define AD5820_NAME		"ad5820"
+
+/* Register definitions */
+#define AD5820_POWER_DOWN		(1 << 15)
+#define AD5820_DAC_SHIFT		4
+#define AD5820_RAMP_MODE_LINEAR		(0 << 3)
+#define AD5820_RAMP_MODE_64_16		(1 << 3)
+
+#define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
+#define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
+
+#define to_ad5820_device(sd)	container_of(sd, struct ad5820_device, subdev)
+
+struct ad5820_device {
+	struct v4l2_subdev subdev;
+	struct ad5820_platform_data *platform_data;
+	struct regulator *vana;
+
+	struct v4l2_ctrl_handler ctrls;
+	u32 focus_absolute;
+	u32 focus_ramp_time;
+	u32 focus_ramp_mode;
+

drivers/media/i2c/ad5820.c line 67

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	struct mutex power_lock;
+	int power_count;
+
+	int standby : 1;
+};
+
+/**
+ * @brief I2C write using i2c_transfer().
+ * @param coil - the driver data structure
+ * @param data - register value to be written

This does not look entirely right. But you could just remove the entire comment. It's useless.

Quoted 53 lines
drivers/media/i2c/ad5820.c new file +53 -0
+ * @returns nonnegative on success, negative if failed
+ */
+static int ad5820_write(struct ad5820_device *coil, u16 data)
+{
+	struct i2c_client *client = v4l2_get_subdevdata(&coil->subdev);
+	struct i2c_msg msg;
+	int r;
+
+	if (!client->adapter)
+		return -ENODEV;
+
+	data = cpu_to_be16(data);
+	msg.addr  = client->addr;
+	msg.flags = 0;
+	msg.len   = 2;
+	msg.buf   = (u8 *)&data;
+
+	r = i2c_transfer(client->adapter, &msg, 1);
+	if (r < 0) {
+		dev_err(&client->dev, "write failed, error %d\n", r);
+		return r;
+	}
+
+	return 0;
+}
+
+/*
+ * Calculate status word and write it to the device based on current
+ * values of V4L2 controls. It is assumed that the stored V4L2 control
+ * values are properly limited and rounded.
+ */
+static int ad5820_update_hw(struct ad5820_device *coil)
+{
+	u16 status;
+
+	status = RAMP_US_TO_CODE(coil->focus_ramp_time);
+	status |= coil->focus_ramp_mode
+		? AD5820_RAMP_MODE_64_16 : AD5820_RAMP_MODE_LINEAR;
+	status |= coil->focus_absolute << AD5820_DAC_SHIFT;
+
+	if (coil->standby)
+		status |= AD5820_POWER_DOWN;
+
+	return ad5820_write(coil, status);
+}
+
+/*
+ * Power handling
+ */
+static int ad5820_power_off(struct ad5820_device *coil, int standby)
+{
+	int ret = 0;
+

drivers/media/i2c/ad5820.c line 130

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+	/*
+	 * Go to standby first as real power off my be denied by the hardware
+	 * (single power line control for both coil and sensor).
+	 */
+	if (standby) {
+		coil->standby = 1;
+		ret = ad5820_update_hw(coil);
+	}
+
+	ret |= regulator_disable(coil->vana);

This is actually an error code and you shouldn't use or to combine two error codes. The result will make no sense.

It might be the driver did this in the past but it should not be done. The right thing, as elsewhere, is to assign the value to ret and check it. The assigment in declaration may be dropped as well.

I think this happens in a few places in the driver.

Quoted 128 lines
drivers/media/i2c/ad5820.c new file +128 -0
+
+	return ret;
+}
+
+static int ad5820_power_on(struct ad5820_device *coil, int restore)
+{
+	int ret;
+
+	ret = regulator_enable(coil->vana);
+	if (ret < 0)
+		return ret;
+
+	if (restore) {
+		/* Restore the hardware settings. */
+		coil->standby = 0;
+		ret = ad5820_update_hw(coil);
+		if (ret)
+			goto fail;
+	}
+	return 0;
+
+fail:
+	coil->standby = 1;
+	regulator_disable(coil->vana);
+
+	return ret;
+}
+
+/*
+ * V4L2 controls
+ */
+static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
+{
+	struct ad5820_device *coil =
+		container_of(ctrl->handler, struct ad5820_device, ctrls);
+	u32 code;
+
+	switch (ctrl->id) {
+	case V4L2_CID_FOCUS_ABSOLUTE:
+		coil->focus_absolute = ctrl->val;
+		return ad5820_update_hw(coil);
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+		code = RAMP_US_TO_CODE(ctrl->val);
+		ctrl->val = CODE_TO_RAMP_US(code);
+		coil->focus_ramp_time = ctrl->val;
+		break;
+
+	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+		coil->focus_ramp_mode = ctrl->val;
+		break;
+	}
+
+	return 0;
+}
+
+static const struct v4l2_ctrl_ops ad5820_ctrl_ops = {
+	.s_ctrl = ad5820_set_ctrl,
+};
+
+static const char * const ad5820_focus_menu[] = {
+	"Linear ramp",
+	"64/16 ramp",
+};
+
+static const struct v4l2_ctrl_config ad5820_ctrls[] = {
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
+		.type		= V4L2_CTRL_TYPE_INTEGER,
+		.name		= "Focus ramping time [us]",
+		.min		= 0,
+		.max		= 3200,
+		.step		= 50,
+		.def		= 0,
+		.flags		= 0,
+	},
+	{
+		.ops		= &ad5820_ctrl_ops,
+		.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,
+		.type		= V4L2_CTRL_TYPE_MENU,
+		.name		= "Focus ramping mode",
+		.min		= 0,
+		.max		= ARRAY_SIZE(ad5820_focus_menu),
+		.step		= 0,
+		.def		= 0,
+		.flags		= 0,
+		.qmenu		= ad5820_focus_menu,
+	},
+};
+
+
+static int ad5820_init_controls(struct ad5820_device *coil)
+{
+	unsigned int i;
+
+	v4l2_ctrl_handler_init(&coil->ctrls, ARRAY_SIZE(ad5820_ctrls) + 1);
+
+	/*
+	 * V4L2_CID_FOCUS_ABSOLUTE
+	 *
+	 * Minimum current is 0 mA, maximum is 100 mA. Thus, 1 code is
+	 * equivalent to 100/1023 = 0.0978 mA. Nevertheless, we do not use [mA]
+	 * for focus position, because it is meaningless for user. Meaningful
+	 * would be to use focus distance or even its inverse, but since the
+	 * driver doesn't have sufficiently knowledge to do the conversion, we
+	 * will just use abstract codes here. In any case, smaller value = focus
+	 * position farther from camera. The default zero value means focus at
+	 * infinity, and also least current consumption.
+	 */
+	v4l2_ctrl_new_std(&coil->ctrls, &ad5820_ctrl_ops,
+			  V4L2_CID_FOCUS_ABSOLUTE, 0, 1023, 1, 0);
+
+	/* V4L2_CID_TEST_PATTERN and V4L2_CID_MODE_* */
+	for (i = 0; i < ARRAY_SIZE(ad5820_ctrls); ++i)
+		v4l2_ctrl_new_custom(&coil->ctrls, &ad5820_ctrls[i], NULL);
+
+	if (coil->ctrls.error)
+		return coil->ctrls.error;
+
+	coil->focus_absolute = 0;
+	coil->focus_ramp_time = 0;
+	coil->focus_ramp_mode = 0;
+
+	coil->subdev.ctrl_handler = &coil->ctrls;
+
+	return 0;
+}

drivers/media/i2c/ad5820.c line 268

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+
+/*
+ * V4L2 subdev operations
+ */
+static int ad5820_registered(struct v4l2_subdev *subdev)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");

Is there a reason not to acquire this in probe instead?

drivers/media/i2c/ad5820.c line 271

Quoted 3 lines
drivers/media/i2c/ad5820.c new file +3 -0
+	if (IS_ERR(coil->vana)) {
+		dev_err(&client->dev, "could not get regulator for vana\n");
+		return -ENODEV;

I wonder if -EPROBE_DEFER might be the right error code here.

Quoted 87 lines
drivers/media/i2c/ad5820.c new file +87 -0
+	}
+
+	return ad5820_init_controls(coil);
+}
+
+static int
+ad5820_set_power(struct v4l2_subdev *subdev, int on)
+{
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	int ret = 0;
+
+	mutex_lock(&coil->power_lock);
+
+	/*
+	 * If the power count is modified from 0 to != 0 or from != 0 to 0,
+	 * update the power state.
+	 */
+	if (coil->power_count == !on) {
+		ret = on ? ad5820_power_on(coil, 1) : ad5820_power_off(coil, 1);
+		if (ret < 0)
+			goto done;
+	}
+
+	/* Update the power count. */
+	coil->power_count += on ? 1 : -1;
+	WARN_ON(coil->power_count < 0);
+
+done:
+	mutex_unlock(&coil->power_lock);
+	return ret;
+}
+
+static int ad5820_open(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 1);
+}
+
+static int ad5820_close(struct v4l2_subdev *sd, struct v4l2_subdev_fh *fh)
+{
+	return ad5820_set_power(sd, 0);
+}
+
+static const struct v4l2_subdev_core_ops ad5820_core_ops = {
+	.s_power = ad5820_set_power,
+};
+
+static const struct v4l2_subdev_ops ad5820_ops = {
+	.core = &ad5820_core_ops,
+};
+
+static const struct v4l2_subdev_internal_ops ad5820_internal_ops = {
+	.registered = ad5820_registered,
+	.open = ad5820_open,
+	.close = ad5820_close,
+};
+
+/*
+ * I2C driver
+ */
+#ifdef CONFIG_PM
+
+static int ad5820_suspend(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_off(coil, 0);
+}
+
+static int ad5820_resume(struct device *dev)
+{
+	struct i2c_client *client = container_of(dev, struct i2c_client, dev);
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	if (!coil->power_count)
+		return 0;
+
+	return ad5820_power_on(coil, 1);
+}
+
+#else
+

drivers/media/i2c/ad5820.c line 368

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+#define ad5820_suspend	NULL
+#define ad5820_resume	NULL
+
+#endif /* CONFIG_PM */
+
+static int ad5820_probe(struct i2c_client *client,
+			const struct i2c_device_id *devid)
+{
+	struct ad5820_device *coil;
+	int ret = 0;

No need to assign ret here.

drivers/media/i2c/ad5820.c line 370

Quoted 2 lines
drivers/media/i2c/ad5820.c new file +2 -0
+
+	coil = kzalloc(sizeof(*coil), GFP_KERNEL);

You could use devm_kzalloc() here and drop kfree() below and in _remove().

The driver might be actually older than the devm_*() functions. Not sure. At least they were not widely used back then. :-)

Quoted 29 lines
drivers/media/i2c/ad5820.c new file +29 -0
+	if (!coil)
+		return -ENOMEM;
+
+	mutex_init(&coil->power_lock);
+
+	v4l2_i2c_subdev_init(&coil->subdev, client, &ad5820_ops);
+	coil->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
+	coil->subdev.internal_ops = &ad5820_internal_ops;
+	strcpy(coil->subdev.name, "ad5820 focus");
+
+	ret = media_entity_pads_init(&coil->subdev.entity, 0, NULL);
+	if (ret < 0)
+		goto free;
+
+	ret = v4l2_async_register_subdev(&coil->subdev);
+	if (ret < 0)
+		goto cleanup;
+
+	return ret;
+
+cleanup:
+	media_entity_cleanup(&coil->subdev.entity);
+
+free:
+	kfree(coil);
+
+	return ret;
+}
+

drivers/media/i2c/ad5820.c line 409

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+static int __exit ad5820_remove(struct i2c_client *client)
+{
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	v4l2_device_unregister_subdev(&coil->subdev);
+	v4l2_ctrl_handler_free(&coil->ctrls);
+	media_entity_cleanup(&coil->subdev.entity);
+	if (coil->vana)
+		regulator_put(coil->vana);

mutex_destroy(&coil->power_lock);

Here. And in probe() error paths as well.

Quoted 29 lines
drivers/media/i2c/ad5820.c new file +29 -0
+
+	kfree(coil);
+
+	return 0;
+}
+
+static const struct i2c_device_id ad5820_id_table[] = {
+	{ AD5820_NAME, 0 },
+	{ }
+};
+MODULE_DEVICE_TABLE(i2c, ad5820_id_table);
+
+static SIMPLE_DEV_PM_OPS(ad5820_pm, ad5820_suspend, ad5820_resume);
+
+static struct i2c_driver ad5820_i2c_driver = {
+	.driver		= {
+		.name	= AD5820_NAME,
+		.pm	= &ad5820_pm,
+	},
+	.probe		= ad5820_probe,
+	.remove		= __exit_p(ad5820_remove),
+	.id_table	= ad5820_id_table,
+};
+
+module_i2c_driver(ad5820_i2c_driver);
+
+MODULE_AUTHOR("Tuukka Toivonen");
+MODULE_DESCRIPTION("AD5820 camera lens driver");
+MODULE_LICENSE("GPL");
Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#14 lore raw

Hi!

Quoted 6 lines
Quoted 2 lines

+ * Contact: Tuukka Toivonen
+ * Sakari Ailus

Could you put the e-mail addresses back, please?

Tuukka's e-mail is tuukkat76 at gmail.com .

Ok.

Quoted 7 lines

drivers/media/i2c/ad5820.c line 29

Quoted 5 lines
drivers/media/i2c/ad5820.c new file +5 -0
+#include <linux/module.h>
+#include <linux/errno.h>
+#include <linux/i2c.h>
+#include <linux/kernel.h>
+#include <linux/regulator/consumer.h>

Alphabetical order would be nice. The same below.

I was afraid you'd ask. Ok.

Quoted 7 lines
Quoted 4 lines

+/**
+ * @brief I2C write using i2c_transfer().
+ * @param coil - the driver data structure
+ * @param data - register value to be written

This does not look entirely right. But you could just remove the entire comment. It's useless.

Ok.

Quoted 16 lines

drivers/media/i2c/ad5820.c line 130

Quoted 12 lines
drivers/media/i2c/ad5820.c new file +12 -0
+	int ret = 0;
+
+	/*
+	 * Go to standby first as real power off my be denied by the hardware
+	 * (single power line control for both coil and sensor).
+	 */
+	if (standby) {
+		coil->standby = 1;
+		ret = ad5820_update_hw(coil);
+	}
+
+	ret |= regulator_disable(coil->vana);

This is actually an error code and you shouldn't use or to combine two error codes. The result will make no sense.

Quoted 3 lines

It might be the driver did this in the past but it should not be done. The right thing, as elsewhere, is to assign the value to ret and check it. The assigment in declaration may be dropped as well.

Yeah, its broken. Let me fix it.

Quoted 1 line

I think this happens in a few places in the driver.

Actually this was the only place left.

Quoted 6 lines

drivers/media/i2c/ad5820.c line 268

Quoted 4 lines
drivers/media/i2c/ad5820.c new file +4 -0
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+	struct i2c_client *client = v4l2_get_subdevdata(subdev);
+
+	coil->vana = regulator_get(&client->dev, "VANA");

Is there a reason not to acquire this in probe instead?

Yeah, new version will do that (already done, Dmitry was faster).

Quoted 5 lines

drivers/media/i2c/ad5820.c line 271

Quoted 3 lines
drivers/media/i2c/ad5820.c new file +3 -0
+	if (IS_ERR(coil->vana)) {
+		dev_err(&client->dev, "could not get regulator for vana\n");
+		return -ENODEV;

I wonder if -EPROBE_DEFER might be the right error code here.

..and should handle PROBE_DEFER, too.

Quoted 7 lines

drivers/media/i2c/ad5820.c line 368

Quoted 5 lines
drivers/media/i2c/ad5820.c new file +5 -0
+static int ad5820_probe(struct i2c_client *client,
+			const struct i2c_device_id *devid)
+{
+	struct ad5820_device *coil;
+	int ret = 0;

No need to assign ret here.

Ok.

Quoted 7 lines

drivers/media/i2c/ad5820.c line 370

Quoted 2 lines
drivers/media/i2c/ad5820.c new file +2 -0
+
+	coil = kzalloc(sizeof(*coil), GFP_KERNEL);

You could use devm_kzalloc() here and drop kfree() below and in _remove().

The driver might be actually older than the devm_*() functions. Not sure. At least they were not widely used back then. :-)

Already done, Dmitry was faster.

Quoted 13 lines

drivers/media/i2c/ad5820.c line 409

Quoted 10 lines
drivers/media/i2c/ad5820.c new file +10 -0
+static int __exit ad5820_remove(struct i2c_client *client)
+{
+	struct v4l2_subdev *subdev = i2c_get_clientdata(client);
+	struct ad5820_device *coil = to_ad5820_device(subdev);
+
+	v4l2_device_unregister_subdev(&coil->subdev);
+	v4l2_ctrl_handler_free(&coil->ctrls);
+	media_entity_cleanup(&coil->subdev.entity);
+	if (coil->vana)
+		regulator_put(coil->vana);

mutex_destroy(&coil->power_lock);

Quoted 1 line

Here. And in probe() error paths as well.

Ok. Can do, altrough it is pretty much a NOP in the error paths.

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#15 lore raw

PATCH v5 1/1 support for AD5820 camera auto-focus coil

In reply to Sakari Ailus

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
v4: remove header file.
v5: switch to devm_ , style cleanups, fixes

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C

index 94f2c99..34434ae 100644

drivers/media/i2c/Makefile +1 -0
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +428 -0

428 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#16 lore raw

Hi Pavel,

Quoted 5 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

The patch looks good to me but then I came to think of a question I've missed so far: is there DT documentation somewhere for the properties used by the driver? I might put that to a separate patch, and cc the relevant list.

Whether we decide to have the module in DT or not is orthogonal to this.

Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#17 lore raw
Quoted 7 lines · Sakari Ailus

Hi Pavel,

Quoted 4 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Quoted 6 lines
Quoted 1 line

The patch looks good to me but then I came to think of a question I've missed so far: is there DT documentation somewhere for the properties used by the driver? I might put that to a separate patch, and cc the relevant list.

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#18 lore raw

Hi Pavel,

Quoted 15 lines · Pavel Machek
Quoted 7 lines · Sakari Ailus

Hi Pavel,

Quoted 4 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Quoted 6 lines
Quoted 1 line

The patch looks good to me but then I came to think of a question I've missed so far: is there DT documentation somewhere for the properties used by the driver? I might put that to a separate patch, and cc the relevant list.

Quoted 5 lines

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

It's an I2C device and it does use a regulator. Not a lot, though, these are both quite basic stuff. This should still be documented as the people who write the DT bindings (in general) aren't expected to read driver code as well. That's at least my understanding.

Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#19 lore raw
Quoted 5 lines · Sakari Ailus

Hi Pavel,

Quoted 3 lines

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Quoted 7 lines
Quoted 2 lines

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

It's an I2C device and it does use a regulator. Not a lot, though, these are both quite basic stuff. This should still be documented as the people who write the DT bindings (in general) aren't expected to read driver code as well. That's at least my understanding.

Yep, you are right, I forgot about the regulator. Something like this?

Thanks,
Pavel

Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +20 -0
new file mode 100644
index 0000000..87c98f1
@@ -0,0 +1,20 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
+Example:
+
+       /* D/A converter for auto-focus */
+       ad5820: dac at 0c {
+               compatible = "adi,ad5820";
+               reg = <0x0c>;
+
+               VANA-supply = <&vaux4>;
+       };
+
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#20 lore raw

Documentation/devicetree/bindings/media/i2c/ad5820.txt

Quoted 24 lines · Pavel Machek
Quoted 5 lines · Sakari Ailus

Hi Pavel,

Quoted 3 lines

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Quoted 7 lines
Quoted 2 lines

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

It's an I2C device and it does use a regulator. Not a lot, though, these are both quite basic stuff. This should still be documented as the people who write the DT bindings (in general) aren't expected to read driver code as well. That's at least my understanding.

Yep, you are right, I forgot about the regulator. Something like this?

Thanks,
Pavel

Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +0 -0
new file mode 100644
index 0000000..87c98f1

I might use the compatible string as such as a part of the file name. Up to you.

Quoted 4 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +3 -0
@@ -0,0 +1,20 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:

Documentation/devicetree/bindings/media/i2c/ad5820.txt line 13

Quoted 10 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +10 -0
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
+Example:
+
+       /* D/A converter for auto-focus */

There is definitely D/A conversion happening there but I'm not sure I'd characterise the device as such. They're typically called "voice coil drivers", perhaps because the devices are similar to a parts of a loudspeaker.

Quoted 9 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +7 -0
+       ad5820: dac at 0c {
+               compatible = "adi,ad5820";
+               reg = <0x0c>;
+
+               VANA-supply = <&vaux4>;
+       };
+
Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#21 lore raw
Quoted 20 lines · Sakari Ailus
Quoted 19 lines · Pavel Machek
Quoted 5 lines · Sakari Ailus

Hi Pavel,

Quoted 3 lines

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Quoted 7 lines
Quoted 2 lines

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

It's an I2C device and it does use a regulator. Not a lot, though, these are both quite basic stuff. This should still be documented as the people who write the DT bindings (in general) aren't expected to read driver code as well. That's at least my understanding.

Yep, you are right, I forgot about the regulator. Something like this?

Thanks,
Pavel

Quoted 8 lines

Documentation/devicetree/bindings/media/i2c/ad5820.txt

Quoted 5 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +0 -0
new file mode 100644
index 0000000..87c98f1

I might use the compatible string as such as a part of the file name. Up to you.

Sorry, can't do that, for consistency with other ad* files in the directory.

Quoted 11 lines
Quoted 11 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +10 -0
@@ -0,0 +1,20 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
Quoted 8 lines

Documentation/devicetree/bindings/media/i2c/ad5820.txt line 13

Quoted 3 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +3 -0
+Example:
+
+       /* D/A converter for auto-focus */

There is definitely D/A conversion happening there but I'm not sure I'd characterise the device as such. They're typically called "voice coil drivers", perhaps because the devices are similar to a parts of a loudspeaker.

Well, I'm pretty sure I did not invent that comment, but I can drop it.

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#22 lore raw
Quoted 52 lines · Pavel Machek
Quoted 20 lines · Sakari Ailus
Quoted 19 lines · Pavel Machek
Quoted 5 lines · Sakari Ailus

Hi Pavel,

Quoted 3 lines

Well, it does not use any dt properties. So there's not really much to discuss with dt people...

Quoted 7 lines
Quoted 2 lines

Maybe "ad5820" needs to go to list of simple i2c drivers somewhere, but...

It's an I2C device and it does use a regulator. Not a lot, though, these are both quite basic stuff. This should still be documented as the people who write the DT bindings (in general) aren't expected to read driver code as well. That's at least my understanding.

Yep, you are right, I forgot about the regulator. Something like this?

Thanks,
Pavel

Quoted 8 lines

Documentation/devicetree/bindings/media/i2c/ad5820.txt

Quoted 5 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +0 -0
new file mode 100644
index 0000000..87c98f1

I might use the compatible string as such as a part of the file name. Up to you.

Sorry, can't do that, for consistency with other ad* files in the directory.

Quoted 11 lines
Quoted 11 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +10 -0
@@ -0,0 +1,20 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
Quoted 8 lines

Documentation/devicetree/bindings/media/i2c/ad5820.txt line 13

Quoted 3 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +3 -0
+Example:
+
+       /* D/A converter for auto-focus */

There is definitely D/A conversion happening there but I'm not sure I'd characterise the device as such. They're typically called "voice coil drivers", perhaps because the devices are similar to a parts of a loudspeaker.

Quoted 2 lines

Well, I'm pretty sure I did not invent that comment, but I can drop it.

Both are fine for me.

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#23 lore raw

PATCH 1/1 device tree description for AD5820 camera auto-focus coil

In reply to Sakari Ailus

Add documentation for ad5820 device tree binding.

Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +19 -0
new file mode 100644
index 0000000..fb70ca5
@@ -0,0 +1,19 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
+Example:
+
+       ad5820: coil at 0c {
+               compatible = "adi,ad5820";
+               reg = <0x0c>;
+
+               VANA-supply = <&vaux4>;
+       };
+
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer Acked-by on v1 1/1
#24 lore raw

Re: [PATCH] device tree description for AD5820 camera auto-focus coil

Quoted 4 lines · Pavel Machek

Add documentation for ad5820 device tree binding.

Thanks, Pavel!!

Can I pick the two patches (this one + the driver) or would you like to send a pull request? In the latter case you can add:

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#25 lore raw

Re: [PATCH] device tree description for AD5820 camera auto-focus coil

Quoted 10 lines · Sakari Ailus
Quoted 4 lines · Pavel Machek

Add documentation for ad5820 device tree binding.

Thanks, Pavel!!

Can I pick the two patches (this one + the driver) or would you like to send a pull request? In the latter case you can add:

Yes please, pick up the two patches.

Best regards,
Pavel

Quoted 2 lines
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#26 lore raw

PATCH 1/1 userspace API definitions for auto-focus coil

In reply to Sakari Ailus

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +5 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME	(V4L2_CID_FOCUS_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE	(V4L2_CID_FOCUS_AD5820_BASE+1)
+
 #endif
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#27 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi,

Quoted 10 lines · Pavel Machek

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 983

Quoted 9 lines
include/uapi/linux/v4l2-controls.h +5 -0
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
  #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
  #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME	(V4L2_CID_FOCUS_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE	(V4L2_CID_FOCUS_AD5820_BASE+1)
+
  #endif

Sakari, what about adding those as standard camera controls? It seems ad5820 is not the only VCM driver to implement "antiringing" controls,
http://rohmfs.rohm.com/en/products/databook/datasheet/ic/motor/mobile_module/bu64241gwz-e.pdf
is another example I found by quick search.

What about:

#define V4L2_CID_FOCUS_STEP_MODE xxx
enum v4l2_cid_focus_step_mode {
V4L2_CID_FOCUS_STEP_MODE_DIRECT,
V4L2_CID_FOCUS_STEP_MODE_LINEAR,
V4L2_CID_FOCUS_STEP_MODE_AUTO
};
#define V4L2_CID_FOCUS_STEP_TIME xxx+1

Also, how the userspace(or the kernel) is notified by v4l that there is an event? The point is - I think it is a good idea to notify when VCM has completed its movement, we can start a timer based on the current position, mode, step time etc and notify after the pre-calculated movement time.

Here ftp://ftp.analog.com/pub/evalcd/AD5820_v1_0/AD5820_Quickstart.pdf can be found the modes/timings description for ad5820 along with the equations needed to calculate timings etc.

Ivo

#28 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi!

Quoted 13 lines · Pavel Machek
Quoted 12 lines

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 11 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 983

Quoted 7 lines
include/uapi/linux/v4l2-controls.h +5 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME	(V4L2_CID_FOCUS_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE	(V4L2_CID_FOCUS_AD5820_BASE+1)
+
 #endif

Sakari, what about adding those as standard camera controls? It seems ad5820
is not the only VCM driver to implement "antiringing" controls, http://rohmfs.rohm.com/en/products/databook/datasheet/ic/motor/mobile_module/bu64241gwz-e.pdf
is another example I found by quick search.

Well, standartized API may be good idea... but I'd really like the driver to go in, and it looks like camera application needs to know quite a lot of details about the autofocus subsystem.

Quoted 11 lines

What about:

#define V4L2_CID_FOCUS_STEP_MODE xxx
enum v4l2_cid_focus_step_mode {
V4L2_CID_FOCUS_STEP_MODE_DIRECT,
V4L2_CID_FOCUS_STEP_MODE_LINEAR,
V4L2_CID_FOCUS_STEP_MODE_AUTO
};
#define V4L2_CID_FOCUS_STEP_TIME xxx+1

Quoted 4 lines

Also, how the userspace(or the kernel) is notified by v4l that there is an event? The point is - I think it is a good idea to notify when VCM has completed its movement, we can start a timer based on the current position,

Why? Look at how fcam-dev/ works. It is not interested when movement is "done". It sets the focus to one distance, then says it to slowly refocus to another distance, and watches the stream for sharpness. When it is sharp, it computes likely lens position at the time of sharpness, and asks hardware to go back there.

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#29 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

In reply to Ivaylo Dimitrov

Hi Ivaylo,

Quoted 15 lines · Ivaylo Dimitrov

Hi,

Quoted 12 lines · Pavel Machek

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 2 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 2 lines
include/uapi/linux/v4l2-controls.h +2 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

Quoted 9 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 983

Quoted 5 lines
include/uapi/linux/v4l2-controls.h +3 -0
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME	(V4L2_CID_FOCUS_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE	(V4L2_CID_FOCUS_AD5820_BASE+1)
+
 #endif

Sakari, what about adding those as standard camera controls? It seems ad5820
is not the only VCM driver to implement "antiringing" controls, http://rohmfs.rohm.com/en/products/databook/datasheet/ic/motor/mobile_module/bu64241gwz-e.pdf
is another example I found by quick search.

These controls however seem to be related to some thing else --- configuring the driver to drive the lens little by little to the target using a pre-defined step time and size. I presume it is intended for something else, most likely for performing a full search for a regular AF algorithm. I also wonder how much this functionality is used nowadays, most devices use continuous AF algorithm that has little or no use for such. It also provides no help in synchronising lens movement to exposure of the AF window.

Now that I think about this, the original implementation in N900 very likely did not use either of the two controls; the device driver was still written to provide access to full capabilities of the chip. And that one had no continuous AF.

Quoted 10 lines

What about:

#define V4L2_CID_FOCUS_STEP_MODE xxx
enum v4l2_cid_focus_step_mode {
V4L2_CID_FOCUS_STEP_MODE_DIRECT,
V4L2_CID_FOCUS_STEP_MODE_LINEAR,
V4L2_CID_FOCUS_STEP_MODE_AUTO
};
#define V4L2_CID_FOCUS_STEP_TIME xxx+1

Quoted 4 lines

Also, how the userspace(or the kernel) is notified by v4l that there is an event? The point is - I think it is a good idea to notify when VCM has completed its movement, we can start a timer based on the current position, mode, step time etc and notify after the pre-calculated movement time.

You'd have to start modelling the movement of the lens somehow. And for that, we'd need to know about the lens and the spring in the kernel, too. I presume that's already a lot of the algorithm to get the lens moving, and supposing this is in the kernel, what else would go to the kernel?

These device provide very basic functionality for moving the lens; current is applied on a coil and that has the effect of moving the lens, bringing the focus distance closer as more current is applied but that's pretty much
it: there's no reliable way to focus at a particular distance for example.

I might as well drop the two controls, up to you. If someone ever needs them they can always be reintroduced. I'd be happy to get a new patch, the current driver patch does not compile (just tried) as the definitions of these controls are missing.

Ringing compensation functionality present in the other chip should be far more useful.

If there are AF experts reading this, feel free to challenge me. :-) I can't claim to be one.

Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#30 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi!

Quoted 9 lines
Quoted 6 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 6 lines
include/uapi/linux/v4l2-controls.h +2 -0
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

Let me see...

Quoted 4 lines

Now that I think about this, the original implementation in N900 very likely did not use either of the two controls; the device driver was still written to provide access to full capabilities of the chip. And that one had no continuous AF.

I'm not sure about the original implementation, but fcam-dev library (which is our best chance for usable camera) does use both:

pavel at duo:~/g/fcam-dev$ grep -ri RAMP_TIME . ./.svn/pristine/05/0574680922f59e07bd49e16a951d69421690a323.svn-base:
int val = ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_TIME, 1000000.0f/diopterRateToTickRate(speed));
./src/N900/Lens.cpp: int val =
ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_TIME, 1000000.0f/diopterRateToTickRate(speed));
pavel at duo:~/g/fcam-dev$ grep -ri RAMP_MODE . ./.svn/pristine/05/0574680922f59e07bd49e16a951d69421690a323.svn-base:
ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_MODE, 0);
./src/N900/Lens.cpp: ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_MODE, 0);
pavel at duo:~/g/fcam-dev$

Quoted 4 lines

I might as well drop the two controls, up to you. If someone ever needs them they can always be reintroduced. I'd be happy to get a new patch, the current driver patch does not compile (just tried) as the definitions of these controls are missing.

I'd prefer to keep the controls, as we have userspace using them. I got it to compile but have yet to get it to work (subdevs split, so it needs some modifications).

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#31 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi Pavel,

Quoted 35 lines · Pavel Machek

Hi!

Quoted 9 lines
Quoted 6 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 6 lines
include/uapi/linux/v4l2-controls.h +2 -0
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

Let me see...

Quoted 4 lines

Now that I think about this, the original implementation in N900 very likely did not use either of the two controls; the device driver was still written to provide access to full capabilities of the chip. And that one had no continuous AF.

I'm not sure about the original implementation, but fcam-dev library (which is our best chance for usable camera) does use both:

pavel at duo:~/g/fcam-dev$ grep -ri RAMP_TIME . ./.svn/pristine/05/0574680922f59e07bd49e16a951d69421690a323.svn-base:
int val = ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_TIME, 1000000.0f/diopterRateToTickRate(speed));
./src/N900/Lens.cpp: int val =
ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_TIME, 1000000.0f/diopterRateToTickRate(speed));
pavel at duo:~/g/fcam-dev$ grep -ri RAMP_MODE . ./.svn/pristine/05/0574680922f59e07bd49e16a951d69421690a323.svn-base:
ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_MODE, 0);
./src/N900/Lens.cpp: ioctlSet(V4L2_CID_FOCUS_AD5820_RAMP_MODE, 0);
pavel at duo:~/g/fcam-dev$

Quoted 8 lines
Quoted 4 lines

I might as well drop the two controls, up to you. If someone ever needs them they can always be reintroduced. I'd be happy to get a new patch, the current driver patch does not compile (just tried) as the definitions of these controls are missing.

I'd prefer to keep the controls, as we have userspace using them. I got it to compile but have yet to get it to work (subdevs split, so it needs some modifications).

Right. I didn't know Fcam used them. Still, using them is hardly an optimal way to control the lens (as far as camera functionality goes, using them requires less CPU time consumption though).

The flash control patches should receive a proper RFC that discusses the problem area and proposes a solution. I'll write one in the near future.

I think that for this particular controller it's relatively clear though: it provides very basic functionality that maps well to controls that I don't really see alternative options for that.

I don't object defining standard controls for ramp mode nor time either. But I expect you to write a patch in that case. :-)

Signature · 4 lines
Regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#32 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

In reply to Sakari Ailus

Hi!

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 5 lines
Quoted 2 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 2 lines
include/uapi/linux/v4l2-controls.h +2 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

So something like this?

Thanks,
Pavel

drivers/media/i2c/ad5820.c +5 -0
index 2efa5dc1..b04b471 100644
@@ -40,6 +40,11 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_USER_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
+
+
 #define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
 #define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
 
include/uapi/linux/v4l2-controls.h +4 -5
index 23011cc..4b24546 100644
@@ -181,6 +181,10 @@ enum v4l2_colorfx {
  * We reserve 16 controls for this driver. */
 #define V4L2_CID_USER_TC358743_BASE		(V4L2_CID_USER_BASE + 0x1080)
 
+/* The base for the ad5820 driver controls.
+ * We reserve 16 controls for this driver. */
+#define V4L2_CID_USER_AD5820_BASE		(V4L2_CID_USER_BASE + 0x1090)
+
 /* MPEG-class control IDs */
 /* The MPEG controls are applicable to all codec controls
  * and the 'MPEG' part of the define is historical */
@@ -986,9 +990,4 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_MODE_SENSITIVITY		(V4L2_CID_MODE_CLASS_BASE+6)
 #define V4L2_CID_MODE_OPSYSCLOCK		(V4L2_CID_MODE_CLASS_BASE+7)
 
-/* Control IDs specific to the AD5820 driver as defined by V4L2 */
-#define V4L2_CID_FOCUS_AD5820_BASE 		(V4L2_CTRL_CLASS_CAMERA | 0x10af)
-#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_FOCUS_AD5820_BASE+0)
-#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
-
 #endif
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#33 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi Pavel,

Quoted 30 lines · Pavel Machek

Hi!

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 5 lines
Quoted 2 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 2 lines
include/uapi/linux/v4l2-controls.h +2 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

So something like this?

Thanks,
Pavel

drivers/media/i2c/ad5820.c +0 -0
index 2efa5dc1..b04b471 100644

drivers/media/i2c/ad5820.c line 47

Quoted 8 lines
drivers/media/i2c/ad5820.c +5 -0
@@ -40,6 +40,11 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_USER_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
+
+

We could still define these in a header file that can be included by the user space. Please use V4L2_CID_AD5820 prefix.

A separate header file should be used, e.g. include/uapi/linux/ad5820.h.

Quoted 30 lines
drivers/media/i2c/ad5820.c +0 -0
 #define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
 #define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
 
include/uapi/linux/v4l2-controls.h +4 -5
index 23011cc..4b24546 100644
@@ -181,6 +181,10 @@ enum v4l2_colorfx {
  * We reserve 16 controls for this driver. */
 #define V4L2_CID_USER_TC358743_BASE		(V4L2_CID_USER_BASE + 0x1080)
 
+/* The base for the ad5820 driver controls.
+ * We reserve 16 controls for this driver. */
+#define V4L2_CID_USER_AD5820_BASE		(V4L2_CID_USER_BASE + 0x1090)
+
 /* MPEG-class control IDs */
 /* The MPEG controls are applicable to all codec controls
  * and the 'MPEG' part of the define is historical */
@@ -986,9 +990,4 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_MODE_SENSITIVITY		(V4L2_CID_MODE_CLASS_BASE+6)
 #define V4L2_CID_MODE_OPSYSCLOCK		(V4L2_CID_MODE_CLASS_BASE+7)
 
-/* Control IDs specific to the AD5820 driver as defined by V4L2 */
-#define V4L2_CID_FOCUS_AD5820_BASE 		(V4L2_CTRL_CLASS_CAMERA | 0x10af)
-#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_FOCUS_AD5820_BASE+0)
-#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
-
 #endif
Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#34 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Quoted 36 lines · Sakari Ailus

Hi Pavel,

Quoted 33 lines · Pavel Machek

Hi!

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 5 lines
Quoted 2 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 2 lines
include/uapi/linux/v4l2-controls.h +2 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

So something like this?

Thanks,
Pavel

drivers/media/i2c/ad5820.c +0 -0
index 2efa5dc1..b04b471 100644
@@ -40,6 +40,11 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
Quoted 8 lines

drivers/media/i2c/ad5820.c line 47

Quoted 5 lines
drivers/media/i2c/ad5820.c +5 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_USER_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
+
+

We could still define these in a header file that can be included by the user space. Please use V4L2_CID_AD5820 prefix.

Not V4L2_CID_USER_AD5820...?

Quoted 2 lines

A separate header file should be used,
e.g. include/uapi/linux/ad5820.h.

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

Something like this?

commit 8dd701d2580e41b06bb2285e6bd59a4f1702b4d8

Author: Pavel <[email protected]>
Date:   Mon Jun 13 21:17:15 2016 +0200

Userspace api, as Sakari asked.

drivers/media/i2c/ad5820.c +8 -4
index 2efa5dc1..ed3facc 100644
@@ -32,6 +32,8 @@
 #include <media/v4l2-device.h>
 #include <media/v4l2-subdev.h>
 
+#include <uapi/linux/ad5820.h>
+
 #define AD5820_NAME		"ad5820"
 
 /* Register definitions */
@@ -40,6 +42,8 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
+
+
 #define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
 #define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
 
@@ -165,13 +169,13 @@ static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
 		coil->focus_absolute = ctrl->val;
 		return ad5820_update_hw(coil);
 
-	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+	case V4L2_CID_AD5820_RAMP_TIME:
 		code = RAMP_US_TO_CODE(ctrl->val);
 		ctrl->val = CODE_TO_RAMP_US(code);
 		coil->focus_ramp_time = ctrl->val;
 		break;
 
-	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+	case V4L2_CID_AD5820_RAMP_MODE:
 		coil->focus_ramp_mode = ctrl->val;
 		break;
 	}
@@ -191,7 +195,7 @@ static const char * const ad5820_focus_menu[] = {
 static const struct v4l2_ctrl_config ad5820_ctrls[] = {
 	{
 		.ops		= &ad5820_ctrl_ops,
-		.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
+		.id		= V4L2_CID_AD5820_RAMP_TIME,
 		.type		= V4L2_CTRL_TYPE_INTEGER,
 		.name		= "Focus ramping time [us]",
 		.min		= 0,
@@ -202,7 +206,7 @@ static const struct v4l2_ctrl_config ad5820_ctrls[] = {
 	},
 	{
 		.ops		= &ad5820_ctrl_ops,
-		.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,
+		.id		= V4L2_CID_AD5820_RAMP_MODE,
 		.type		= V4L2_CTRL_TYPE_MENU,
 		.name		= "Focus ramping mode",
 		.min		= 0,
include/uapi/linux/ad5820.h new file +18 -0
new file mode 100644
index 0000000..d44ba9c
@@ -0,0 +1,18 @@
+/*
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ */
+
+#ifndef __LINUX_AD5820_H
+#define __LINUX_AD5820_H
+
+#include <linux/v4l2-controls.h>
+
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_AD5820_RAMP_TIME	(V4L2_CID_AD5820_BASE+0)
+#define V4L2_CID_AD5820_RAMP_MODE	(V4L2_CID_AD5820_BASE+1)
+
+#endif
include/uapi/linux/v4l2-controls.h +4 -5
index 23011cc..015e90b 100644
@@ -181,6 +181,10 @@ enum v4l2_colorfx {
  * We reserve 16 controls for this driver. */
 #define V4L2_CID_USER_TC358743_BASE		(V4L2_CID_USER_BASE + 0x1080)
 
+/* The base for the ad5820 driver controls.
+ * We reserve 16 controls for this driver. */
+#define V4L2_CID_AD5820_BASE			(V4L2_CID_USER_BASE + 0x1090)
+
 /* MPEG-class control IDs */
 /* The MPEG controls are applicable to all codec controls
  * and the 'MPEG' part of the define is historical */
@@ -986,9 +990,4 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_MODE_SENSITIVITY		(V4L2_CID_MODE_CLASS_BASE+6)
 #define V4L2_CID_MODE_OPSYSCLOCK		(V4L2_CID_MODE_CLASS_BASE+7)
 
-/* Control IDs specific to the AD5820 driver as defined by V4L2 */
-#define V4L2_CID_FOCUS_AD5820_BASE 		(V4L2_CTRL_CLASS_CAMERA | 0x10af)
-#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_FOCUS_AD5820_BASE+0)
-#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
-
 #endif
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#35 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Hi Pavel,

Quoted 46 lines · Pavel Machek
Quoted 36 lines · Sakari Ailus

Hi Pavel,

Quoted 33 lines · Pavel Machek

Hi!

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

Add userspace API definitions.

include/uapi/linux/v4l2-controls.h +0 -0
index b6a357a..23011cc 100644
@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
Quoted 5 lines
Quoted 2 lines

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 979

Quoted 2 lines
include/uapi/linux/v4l2-controls.h +2 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_BASE 	(V4L2_CTRL_CLASS_CAMERA | 0x10af)

Please check V4L2_CID_USER_*_BASE. That's how custom controls are handled nowadays.

So something like this?

Thanks,
Pavel

drivers/media/i2c/ad5820.c +0 -0
index 2efa5dc1..b04b471 100644
@@ -40,6 +40,11 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
Quoted 8 lines

drivers/media/i2c/ad5820.c line 47

Quoted 5 lines
drivers/media/i2c/ad5820.c +5 -0
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_USER_AD5820_BASE+0)
+#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
+
+

We could still define these in a header file that can be included by the user space. Please use V4L2_CID_AD5820 prefix.

Quoted 1 line

Not V4L2_CID_USER_AD5820...?

The rest of the controls have no USER as part of the macro name, so I wouldn't use it here either.

Quoted 6 lines
Quoted 3 lines

A separate header file should be used,
e.g. include/uapi/linux/ad5820.h.

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

That follows an existing pattern of how controls have been implemented in other drivers.

Quoted 2 lines

Something like this?

Yes. A few minor comments below.

Could you merge this with the driver patch? I've dropped that from my ad5820 branch as it does not compile.

Quoted 21 lines

commit 8dd701d2580e41b06bb2285e6bd59a4f1702b4d8

Author: Pavel <[email protected]>
Date:   Mon Jun 13 21:17:15 2016 +0200

Userspace api, as Sakari asked.

drivers/media/i2c/ad5820.c +2 -0
index 2efa5dc1..ed3facc 100644
@@ -32,6 +32,8 @@
 #include <media/v4l2-device.h>
 #include <media/v4l2-subdev.h>
 
+#include <uapi/linux/ad5820.h>
+
 #define AD5820_NAME		"ad5820"
 
 /* Register definitions */

drivers/media/i2c/ad5820.c line 46

Quoted 5 lines
drivers/media/i2c/ad5820.c +2 -0
@@ -40,6 +42,8 @@
 #define AD5820_RAMP_MODE_LINEAR		(0 << 3)
 #define AD5820_RAMP_MODE_64_16		(1 << 3)
 
+
+

Extra newlines.

Quoted 48 lines
drivers/media/i2c/ad5820.c +4 -4
 #define CODE_TO_RAMP_US(s)	((s) == 0 ? 0 : (1 << ((s) - 1)) * 50)
 #define RAMP_US_TO_CODE(c)	fls(((c) + ((c)>>1)) / 50)
 
@@ -165,13 +169,13 @@ static int ad5820_set_ctrl(struct v4l2_ctrl *ctrl)
 		coil->focus_absolute = ctrl->val;
 		return ad5820_update_hw(coil);
 
-	case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
+	case V4L2_CID_AD5820_RAMP_TIME:
 		code = RAMP_US_TO_CODE(ctrl->val);
 		ctrl->val = CODE_TO_RAMP_US(code);
 		coil->focus_ramp_time = ctrl->val;
 		break;
 
-	case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
+	case V4L2_CID_AD5820_RAMP_MODE:
 		coil->focus_ramp_mode = ctrl->val;
 		break;
 	}
@@ -191,7 +195,7 @@ static const char * const ad5820_focus_menu[] = {
 static const struct v4l2_ctrl_config ad5820_ctrls[] = {
 	{
 		.ops		= &ad5820_ctrl_ops,
-		.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
+		.id		= V4L2_CID_AD5820_RAMP_TIME,
 		.type		= V4L2_CTRL_TYPE_INTEGER,
 		.name		= "Focus ramping time [us]",
 		.min		= 0,
@@ -202,7 +206,7 @@ static const struct v4l2_ctrl_config ad5820_ctrls[] = {
 	},
 	{
 		.ops		= &ad5820_ctrl_ops,
-		.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,
+		.id		= V4L2_CID_AD5820_RAMP_MODE,
 		.type		= V4L2_CTRL_TYPE_MENU,
 		.name		= "Focus ramping mode",
 		.min		= 0,
include/uapi/linux/ad5820.h new file +5 -0
new file mode 100644
index 0000000..d44ba9c
@@ -0,0 +1,18 @@
+/*
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License

include/uapi/linux/ad5820.h line 15

Quoted 10 lines
include/uapi/linux/ad5820.h new file +10 -0
+ * version 2 as published by the Free Software Foundation.
+ */
+
+#ifndef __LINUX_AD5820_H
+#define __LINUX_AD5820_H
+
+#include <linux/v4l2-controls.h>
+
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_AD5820_RAMP_TIME	(V4L2_CID_AD5820_BASE+0)

(V4L2_CID_AD5820_BASE + 0)

Same below.

Quoted 30 lines
include/uapi/linux/ad5820.h new file +3 -0
+#define V4L2_CID_AD5820_RAMP_MODE	(V4L2_CID_AD5820_BASE+1)
+
+#endif
include/uapi/linux/v4l2-controls.h +4 -5
index 23011cc..015e90b 100644
@@ -181,6 +181,10 @@ enum v4l2_colorfx {
  * We reserve 16 controls for this driver. */
 #define V4L2_CID_USER_TC358743_BASE		(V4L2_CID_USER_BASE + 0x1080)
 
+/* The base for the ad5820 driver controls.
+ * We reserve 16 controls for this driver. */
+#define V4L2_CID_AD5820_BASE			(V4L2_CID_USER_BASE + 0x1090)
+
 /* MPEG-class control IDs */
 /* The MPEG controls are applicable to all codec controls
  * and the 'MPEG' part of the define is historical */
@@ -986,9 +990,4 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_MODE_SENSITIVITY		(V4L2_CID_MODE_CLASS_BASE+6)
 #define V4L2_CID_MODE_OPSYSCLOCK		(V4L2_CID_MODE_CLASS_BASE+7)
 
-/* Control IDs specific to the AD5820 driver as defined by V4L2 */
-#define V4L2_CID_FOCUS_AD5820_BASE 		(V4L2_CTRL_CLASS_CAMERA | 0x10af)
-#define V4L2_CID_FOCUS_AD5820_RAMP_TIME		(V4L2_CID_FOCUS_AD5820_BASE+0)
-#define V4L2_CID_FOCUS_AD5820_RAMP_MODE		(V4L2_CID_FOCUS_AD5820_BASE+1)
-
 #endif
Signature · 4 lines
Regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#36 lore raw

PATCH v4 1/1 support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe

v3: more cleanups, remove printk, add include

v4: add uapi definitions

drivers/media/i2c/Kconfig +7 -0
index 993dc50..77313a1 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..34434ae 100644
@@ -19,6 +20,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +430 -0

430 lines not on this page · raw message

include/uapi/linux/ad5820.h new file +18 -0
new file mode 100644
index 0000000..4e541e8
@@ -0,0 +1,18 @@
+/*
+ * AD5820 DAC driver for camera voice coil focus.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ */
+
+#ifndef __LINUX_AD5820_H
+#define __LINUX_AD5820_H
+
+#include <linux/v4l2-controls.h>
+
+/* Control IDs specific to the AD5820 driver as defined by V4L2 */
+#define V4L2_CID_AD5820_RAMP_TIME	(V4L2_CID_AD5820_BASE + 0)
+#define V4L2_CID_AD5820_RAMP_MODE	(V4L2_CID_AD5820_BASE + 1)
+
+#endif
include/uapi/linux/v4l2-controls.h +4 -0
index b6a357a..015e90b 100644
@@ -180,6 +181,10 @@ enum v4l2_colorfx {
  * We reserve 16 controls for this driver. */
 #define V4L2_CID_USER_TC358743_BASE		(V4L2_CID_USER_BASE + 0x1080)
 
+/* The base for the ad5820 driver controls.
+ * We reserve 16 controls for this driver. */
+#define V4L2_CID_AD5820_BASE			(V4L2_CID_USER_BASE + 0x1090)
+
 /* MPEG-class control IDs */
 /* The MPEG controls are applicable to all codec controls
  * and the 'MPEG' part of the define is historical */
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#37 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

In reply to Sakari Ailus

Hi!

Quoted 4 lines
Quoted 1 line

Not V4L2_CID_USER_AD5820...?

The rest of the controls have no USER as part of the macro name, so I wouldn't use it here either.

Ok.

Quoted 5 lines
Quoted 2 lines

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

That follows an existing pattern of how controls have been implemented in other drivers.

Ok.

Quoted 2 lines

Could you merge this with the driver patch? I've dropped that from my ad5820 branch as it does not compile.

Yes, merged patch should be in your inbox now.

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#38 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

Em Sat, 18 Jun 2016 17:38:46 +0200
Pavel Machek <[email protected]> escreveu:

Quoted 15 lines

Hi!

Quoted 4 lines
Quoted 1 line

Not V4L2_CID_USER_AD5820...?

The rest of the controls have no USER as part of the macro name, so I wouldn't use it here either.

Ok.

Quoted 5 lines
Quoted 2 lines

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

That follows an existing pattern of how controls have been implemented in other drivers.

Quoted 6 lines

Ok.

Quoted 2 lines

Could you merge this with the driver patch? I've dropped that from my ad5820 branch as it does not compile.

Yes, merged patch should be in your inbox now.

The V4L2 core changes should be on a separate patch. Btw, you'll also need to patch documentation to reflect such changes. We're right now moving from DocBook to ReST markup language. The patches for it are right now on a separate topic branch (docs-next), to be merged for Kernel 4.8 on the next merge window.

You should either base the patch on such branch or wait for it to be merged back mainstream to write such documentation additions.

Quoted 4 lines

Thanks,
Pavel

Signature · 2 lines
Thanks,
Mauro
#39 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

On Tue 2016-07-12 20:32:01, Mauro Carvalho Chehab wrote:
1;2802;0c> Em Sat, 18 Jun 2016 17:38:46 +0200

Quoted 24 lines

Pavel Machek <[email protected]> escreveu:

Quoted 15 lines

Hi!

Quoted 4 lines
Quoted 1 line

Not V4L2_CID_USER_AD5820...?

The rest of the controls have no USER as part of the macro name, so I wouldn't use it here either.

Ok.

Quoted 5 lines
Quoted 2 lines

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

That follows an existing pattern of how controls have been implemented in other drivers.

Quoted 6 lines

Ok.

Quoted 2 lines

Could you merge this with the driver patch? I've dropped that from my ad5820 branch as it does not compile.

Yes, merged patch should be in your inbox now.

Quoted 8 lines

The V4L2 core changes should be on a separate patch. Btw, you'll also need to patch documentation to reflect such changes. We're right now moving from DocBook to ReST markup language. The patches for it are right now on a separate topic branch (docs-next), to be merged for Kernel 4.8 on the next merge window.

You should either base the patch on such branch or wait for it to be merged back mainstream to write such documentation additions.

So how many iterations and how many releases does it take to get trivial driver into the tree?

I did what Sakari asked me to do. The driver is trivial. You can see pretty easily what I'm changing in the core... and it is not much. Can you just add your acked-by to it, merge it and me done with it?

If some more docs is required, I can do the docs, but stalling patch for months and then claiming "hey, we have these new rules you have to follow" is not a nice thing.

Thanks,

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#40 lore raw

Re: [PATCH] userspace API definitions for auto-focus coil

In reply to Mauro Carvalho Chehab
Quoted 23 lines · Mauro Carvalho Chehab

Em Sat, 18 Jun 2016 17:38:46 +0200
Pavel Machek <[email protected]> escreveu:

Quoted 20 lines

Hi!

Quoted 4 lines
Quoted 1 line

Not V4L2_CID_USER_AD5820...?

The rest of the controls have no USER as part of the macro name, so I wouldn't use it here either.

Ok.

Quoted 5 lines
Quoted 2 lines

Ok, separate header file for 2 lines seemed like a bit of overkill, but why not.

That follows an existing pattern of how controls have been implemented in other drivers.

Ok.

Quoted 2 lines

Could you merge this with the driver patch? I've dropped that from my ad5820 branch as it does not compile.

Quoted 7 lines
Quoted 1 line

Yes, merged patch should be in your inbox now.

The V4L2 core changes should be on a separate patch. Btw, you'll also need to patch documentation to reflect such changes. We're right now moving from DocBook to ReST markup language. The patches for it are right now on a separate topic branch (docs-next), to be merged for Kernel 4.8 on the next merge window.

What about: I drop all the functionality but FOCUS_ABSOLUTE, which is core functionality, anyway, and does not need core changes. When V4L2 core stabilizes, it can be reintroduced.

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer Acked-by on v1 1/1
#41 lore raw

Re: [PATCH] device tree description for AD5820 camera auto-focus coil

In reply to Pavel Machek
Quoted 14 lines · Pavel Machek

Add documentation for ad5820 device tree binding.

Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +3 -0
new file mode 100644
index 0000000..fb70ca5
@@ -0,0 +1,19 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:

Documentation/devicetree/bindings/media/i2c/ad5820.txt line 13

Quoted 10 lines
Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +10 -0
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
+Example:
+
+       ad5820: coil at 0c {

Drop the leading 0. With that,

#42 lore raw

PATCH v2 1/1 device tree description for AD5820 camera auto-focus coil

In reply to Pavel Machek

Add documentation for ad5820 device tree binding.

---

v2: Fixed nit in example, added acks.

Documentation/devicetree/bindings/media/i2c/ad5820.txt new file +19 -0
new file mode 100644
index 0000000..fb70ca5
@@ -0,0 +1,19 @@
+* Analog Devices AD5820 autofocus coil
+
+Required Properties:
+
+  - compatible: Must contain "adi,ad5820"
+
+  - reg: I2C slave address
+
+  - VANA-supply: supply of voltage for VANA pin
+
+Example:
+
+       ad5820: coil at c {
+               compatible = "adi,ad5820";
+               reg = <0x0c>;
+
+               VANA-supply = <&vaux4>;
+       };
+
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#43 lore raw

Re: [PATCHv2] device tree description for AD5820 camera auto-focus coil

Quoted 6 lines · Pavel Machek

Add documentation for ad5820 device tree binding.

Thanks!

I've replaced the patch in my tree, will send a pull req later.

Signature · 4 lines
Cheers,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#44 lore raw
In reply to Pavel Machek
reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree…

Hi,

[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.7-rc1 next-20160603]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Pavel-Machek/support-for-AD5820-camera-auto-focus-coil/20160528-045306
base:   git://linuxtv.org/media_tree.git master
config: tile-allyesconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 4.6.2

reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=tile

All errors (new ones prefixed by >>):

drivers/media/i2c/ad5820.c: In function 'ad5820_set_ctrl':
drivers/media/i2c/ad5820.c:168:7: error: 'V4L2_CID_FOCUS_AD5820_RAMP_TIME' undeclared (first use in this function) drivers/media/i2c/ad5820.c:168:7: note: each undeclared identifier is reported only once for each function it appears in

>> drivers/media/i2c/ad5820.c:174:7: error: 'V4L2_CID_FOCUS_AD5820_RAMP_MODE' undeclared (first use in this function)

drivers/media/i2c/ad5820.c: At top level:
drivers/media/i2c/ad5820.c:194:10: error: 'V4L2_CID_FOCUS_AD5820_RAMP_TIME' undeclared here (not in a function) drivers/media/i2c/ad5820.c:205:10: error: 'V4L2_CID_FOCUS_AD5820_RAMP_MODE' undeclared here (not in a function)

vim +/V4L2_CID_FOCUS_AD5820_RAMP_MODE +174 drivers/media/i2c/ad5820.c

162
163 switch (ctrl->id) {
164 case V4L2_CID_FOCUS_ABSOLUTE:
165 coil->focus_absolute = ctrl->val;
166 return ad5820_update_hw(coil);
167

 > 168		case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
   169			code = RAMP_US_TO_CODE(ctrl->val);
   170			ctrl->val = CODE_TO_RAMP_US(code);
   171			coil->focus_ramp_time = ctrl->val;
   172			break;
   173	
 > 174		case V4L2_CID_FOCUS_AD5820_RAMP_MODE:

175 coil->focus_ramp_mode = ctrl->val;
176 break;
177 }

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 43906 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160605/e107ca9e/attachment-0001.obj>

#45 lore raw
In reply to Pavel Machek
reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree…

Hi,

[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.7-rc1 next-20160603]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Pavel-Machek/support-for-AD5820-camera-auto-focus-coil/20160528-045306
base:   git://linuxtv.org/media_tree.git master
config: sh-allyesconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205

reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=sh

All errors (new ones prefixed by >>):

drivers/media/i2c/ad5820.c: In function 'ad5820_set_ctrl':

>> drivers/media/i2c/ad5820.c:168:7: error: 'V4L2_CID_FOCUS_AD5820_RAMP_TIME' undeclared (first use in this function)
     case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
          ^
   drivers/media/i2c/ad5820.c:168:7: note: each undeclared identifier is reported only once for each function it appears in
   drivers/media/i2c/ad5820.c:174:7: error: 'V4L2_CID_FOCUS_AD5820_RAMP_MODE' undeclared (first use in this function)
     case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
          ^
   drivers/media/i2c/ad5820.c: At top level:
>> drivers/media/i2c/ad5820.c:194:10: error: 'V4L2_CID_FOCUS_AD5820_RAMP_TIME' undeclared here (not in a function)
      .id  = V4L2_CID_FOCUS_AD5820_RAMP_TIME,
             ^
>> drivers/media/i2c/ad5820.c:205:10: error: 'V4L2_CID_FOCUS_AD5820_RAMP_MODE' undeclared here (not in a function)
      .id  = V4L2_CID_FOCUS_AD5820_RAMP_MODE,
             ^

drivers/media/i2c/ad5820.c:321:12: warning: 'ad5820_suspend' defined but not used [-Wunused-function]
static int ad5820_suspend(struct device *dev)
^
drivers/media/i2c/ad5820.c:333:12: warning: 'ad5820_resume' defined but not used [-Wunused-function]
static int ad5820_resume(struct device *dev)
^

vim +/V4L2_CID_FOCUS_AD5820_RAMP_TIME +168 drivers/media/i2c/ad5820.c

162
163 switch (ctrl->id) {
164 case V4L2_CID_FOCUS_ABSOLUTE:
165 coil->focus_absolute = ctrl->val;
166 return ad5820_update_hw(coil);
167

 > 168		case V4L2_CID_FOCUS_AD5820_RAMP_TIME:
   169			code = RAMP_US_TO_CODE(ctrl->val);
   170			ctrl->val = CODE_TO_RAMP_US(code);
   171			coil->focus_ramp_time = ctrl->val;
   172			break;
   173	
   174		case V4L2_CID_FOCUS_AD5820_RAMP_MODE:
   175			coil->focus_ramp_mode = ctrl->val;
   176			break;
   177		}
   178	
   179		return 0;
   180	}
   181	
   182	static const struct v4l2_ctrl_ops ad5820_ctrl_ops = {
   183		.s_ctrl = ad5820_set_ctrl,
   184	};
   185	
   186	static const char * const ad5820_focus_menu[] = {
   187		"Linear ramp",
   188		"64/16 ramp",
   189	};
   190	
   191	static const struct v4l2_ctrl_config ad5820_ctrls[] = {
   192		{
   193			.ops		= &ad5820_ctrl_ops,
 > 194			.id		= V4L2_CID_FOCUS_AD5820_RAMP_TIME,
   195			.type		= V4L2_CTRL_TYPE_INTEGER,
   196			.name		= "Focus ramping time [us]",
   197			.min		= 0,
   198			.max		= 3200,
   199			.step		= 50,
   200			.def		= 0,
   201			.flags		= 0,
   202		},
   203		{
   204			.ops		= &ad5820_ctrl_ops,
 > 205			.id		= V4L2_CID_FOCUS_AD5820_RAMP_MODE,

206 .type = V4L2_CTRL_TYPE_MENU,
207 .name = "Focus ramping mode",
208 .min = 0,

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 39262 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160605/d6e47d54/attachment-0001.obj>

#46 lore raw

PATCH 1/1 v4l: Add camera voice coil lens control class, current control

In reply to Pavel Machek

From: Sakari Ailus <[email protected]>

Add a V4L2 control class for voice coil lens driver devices. These are simple devices that are used to move a camera lens from its resting position.

---
Hi Pavel,

I also don't think the FOCUS_ABSOLUTE controls is a really good one for the voice coil lens current. I expect more voice coil lens controls (linear vs. PWM mode, ringing compensation...) to be needed so I think it's worth a new class.

Cc others, too...

Kind regards,
Sakari

 Documentation/DocBook/media/v4l/controls.xml | 55 +++++++++++++++++++++++++++-
 include/uapi/linux/v4l2-controls.h           |  7 ++++
 2 files changed, 61 insertions(+), 1 deletion(-)
Documentation/DocBook/media/v4l/controls.xml +54 -1
index e2e5484..aa7169c 100644
@@ -5502,4 +5502,57 @@ receiving given frequency when that control is set. This is a read-only control.
         </tgroup>
       </table>
     </section>
-</section>
+
+    <section id="voice-coil-controls">
+      <title>Voice Coil Control Reference</title>
+
+      <para>The Voice Coil class controls are used to control voice
+      coil lens devices. These are very simple devices that consist of
+      a voice coil, a spring and a lens. The current applied on a
+      voice coil is used to move the lens away from the resting
+      position which typically is (close to) infinity.</para>
+
+      <table pgwide="1" frame="none" id="voice-coil-control-id">
+      <title>Voice Coil Control IDs</title>
+
+      <tgroup cols="4">
+        <colspec colname="c1" colwidth="1*" />
+        <colspec colname="c2" colwidth="6*" />
+        <colspec colname="c3" colwidth="2*" />
+        <colspec colname="c4" colwidth="6*" />
+        <spanspec namest="c1" nameend="c2" spanname="id" />
+        <spanspec namest="c2" nameend="c4" spanname="descr" />
+        <thead>
+          <row>
+            <entry spanname="id" align="left">ID</entry>
+            <entry align="left">Type</entry>
+          </row><row rowsep="1"><entry spanname="descr" align="left">Description</entry>
+          </row>
+        </thead>
+        <tbody valign="top">
+          <row><entry></entry></row>
+          <row>
+            <entry spanname="id"><constant>V4L2_CID_VOICE_COIL_CLASS</constant>&nbsp;</entry>
+            <entry>class</entry>
+          </row><row><entry spanname="descr">The Voice Coil class
+descriptor. Calling &VIDIOC-QUERYCTRL; for this control will return a
+description of this control class.</entry>
+          </row>
+          <row>
+            <entry spanname="id"><constant>V4L2_CID_VOICE_COIL_CURRENT</constant>&nbsp;</entry>
+            <entry>integer</entry>
+          </row><row><entry spanname="descr">Current applied on a
+          voice coil. The more current is applied, the more is the
+          position of the lens moved from its resting position. Do
+          note that there may be a ringing effect; the lens will
+          oscillate after changing the current applied unless the
+          device implements ringing compensation.
+          </entry>
+          </row>
+        </tbody>
+      </tgroup>
+      </table>
+
+      </section>
+
+  </section>
include/uapi/linux/v4l2-controls.h +7 -0
index b6a357a..c6b1261 100644
@@ -62,6 +62,7 @@
 #define V4L2_CTRL_CLASS_FM_RX		0x00a10000	/* FM Receiver controls */
 #define V4L2_CTRL_CLASS_RF_TUNER	0x00a20000	/* RF tuner controls */
 #define V4L2_CTRL_CLASS_DETECT		0x00a30000	/* Detection controls */
+#define V4L2_CTRL_CLASS_VOICE_COIL	0x00a40000	/* Voice coil lens driver */
 
 /* User-class control IDs */
 
@@ -974,4 +975,10 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/*  Voice coil lens driver control IDs defined by V4L2 */
+#define V4L2_CID_VOICE_COIL_CLASS_BASE		(V4L2_CTRL_CLASS_VOICE_COIL | 0x900)
+#define V4L2_CID_VOICE_COIL_CLASS		(V4L2_CTRL_CLASS_VOICE_COIL | 1)
+
+#define V4L2_CID_VOICE_COIL_CURRENT		(V4L2_CID_VOICE_COIL_CLASS_BASE + 1)
+
 #endif
Signature · 1 line
2.1.4
#47 lore raw

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

Hi,

Quoted 6 lines · Sakari Ailus

From: Sakari Ailus <[email protected]>

Add a V4L2 control class for voice coil lens driver devices. These are simple devices that are used to move a camera lens from its resting position.

Quoted 9 lines

---
Hi Pavel,

I also don't think the FOCUS_ABSOLUTE controls is a really good one for the voice coil lens current. I expect more voice coil lens controls (linear vs. PWM mode, ringing compensation...) to be needed so I think it's worth a new class.

Right, I still think movement mode should be standard control :)

Quoted 15 lines

Cc others, too...

Kind regards,
Sakari

  Documentation/DocBook/media/v4l/controls.xml | 55 +++++++++++++++++++++++++++-
  include/uapi/linux/v4l2-controls.h           |  7 ++++
  2 files changed, 61 insertions(+), 1 deletion(-)
Documentation/DocBook/media/v4l/controls.xml +0 -0
index e2e5484..aa7169c 100644
@@ -5502,4 +5502,57 @@ receiving given frequency when that control is set. This is a read-only control.
          </tgroup>

Documentation/DocBook/media/v4l/controls.xml receiving given frequency when that control is set. This is a read-only control. · line 5511

Quoted 10 lines
Documentation/DocBook/media/v4l/controls.xml +7 -1
        </table>
      </section>
-</section>
+
+    <section id="voice-coil-controls">
+      <title>Voice Coil Control Reference</title>
+
+      <para>The Voice Coil class controls are used to control voice
+      coil lens devices. These are very simple devices that consist of
+      a voice coil, a spring and a lens. The current applied on a

There should be a magnet as well.

Quoted 22 lines
Documentation/DocBook/media/v4l/controls.xml +22 -0
+      voice coil is used to move the lens away from the resting
+      position which typically is (close to) infinity.</para>
+
+      <table pgwide="1" frame="none" id="voice-coil-control-id">
+      <title>Voice Coil Control IDs</title>
+
+      <tgroup cols="4">
+        <colspec colname="c1" colwidth="1*" />
+        <colspec colname="c2" colwidth="6*" />
+        <colspec colname="c3" colwidth="2*" />
+        <colspec colname="c4" colwidth="6*" />
+        <spanspec namest="c1" nameend="c2" spanname="id" />
+        <spanspec namest="c2" nameend="c4" spanname="descr" />
+        <thead>
+          <row>
+            <entry spanname="id" align="left">ID</entry>
+            <entry align="left">Type</entry>
+          </row><row rowsep="1"><entry spanname="descr" align="left">Description</entry>
+          </row>
+        </thead>
+        <tbody valign="top">
+          <row><entry></entry></row>

Documentation/DocBook/media/v4l/controls.xml receiving given frequency when that control is set. This is a read-only control. · line 5543

Quoted 10 lines
Documentation/DocBook/media/v4l/controls.xml +10 -0
+          <row>
+            <entry spanname="id"><constant>V4L2_CID_VOICE_COIL_CLASS</constant>&nbsp;</entry>
+            <entry>class</entry>
+          </row><row><entry spanname="descr">The Voice Coil class
+descriptor. Calling &VIDIOC-QUERYCTRL; for this control will return a
+description of this control class.</entry>
+          </row>
+          <row>
+            <entry spanname="id"><constant>V4L2_CID_VOICE_COIL_CURRENT</constant>&nbsp;</entry>
+            <entry>integer</entry>

I think this is no better than FOCUS_ABSOLUTE - nor "absolute" neither "current" give any idea where is the lens (relatively to the rest position) without userspace doing some calculations. What about V4L2_CID_VOICE_COIL_POSITION, 0.000%-100.000% (pcm units)?

Quoted 29 lines
Documentation/DocBook/media/v4l/controls.xml +15 -0
+          </row><row><entry spanname="descr">Current applied on a
+          voice coil. The more current is applied, the more is the
+          position of the lens moved from its resting position. Do
+          note that there may be a ringing effect; the lens will
+          oscillate after changing the current applied unless the
+          device implements ringing compensation.
+          </entry>
+          </row>
+        </tbody>
+      </tgroup>
+      </table>
+
+      </section>
+
+  </section>
include/uapi/linux/v4l2-controls.h +1 -0
index b6a357a..c6b1261 100644
@@ -62,6 +62,7 @@
  #define V4L2_CTRL_CLASS_FM_RX		0x00a10000	/* FM Receiver controls */
  #define V4L2_CTRL_CLASS_RF_TUNER	0x00a20000	/* RF tuner controls */
  #define V4L2_CTRL_CLASS_DETECT		0x00a30000	/* Detection controls */
+#define V4L2_CTRL_CLASS_VOICE_COIL	0x00a40000	/* Voice coil lens driver */
 
  /* User-class control IDs */
 

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 984

Quoted 10 lines
include/uapi/linux/v4l2-controls.h +6 -0
@@ -974,4 +975,10 @@ enum v4l2_detect_md_mode {
  #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
  #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/*  Voice coil lens driver control IDs defined by V4L2 */
+#define V4L2_CID_VOICE_COIL_CLASS_BASE		(V4L2_CTRL_CLASS_VOICE_COIL | 0x900)
+#define V4L2_CID_VOICE_COIL_CLASS		(V4L2_CTRL_CLASS_VOICE_COIL | 1)
+
+#define V4L2_CID_VOICE_COIL_CURRENT		(V4L2_CID_VOICE_COIL_CLASS_BASE + 1)
+
  #endif

Ivo

#48 lore raw

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

Hi!

Quoted 4 lines
Quoted 4 lines

I also don't think the FOCUS_ABSOLUTE controls is a really good one for the voice coil lens current. I expect more voice coil lens controls (linear vs. PWM mode, ringing compensation...) to be needed so I think it's worth a new class.

Well, I do agree that that the new class is fine (and have no problem with your proposal), but I'd like to understand why FOCUS_ABSOLUTE is unsuitable. I'm actually thinking about writing very simple userspace camera, without autofocus, where user would just select "infinity"/"1m"/"50cm" ... and for that FOCUS_ABSOLUTE is equivalent to VOICE_COIL_CURRENT...

Quoted 1 line

Right, I still think movement mode should be standard control :)

What options would you like to see for movement mode?

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#49 lore raw

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

Hello,

Quoted 14 lines · On Saturday 18 Jun 2016 00:11:49 Pavel Machek wrote:

Hi!

Quoted 4 lines
Quoted 4 lines

I also don't think the FOCUS_ABSOLUTE controls is a really good one for the voice coil lens current. I expect more voice coil lens controls (linear vs. PWM mode, ringing compensation...) to be needed so I think it's worth a new class.

Well, I do agree that that the new class is fine (and have no problem with your proposal), but I'd like to understand why FOCUS_ABSOLUTE is unsuitable. I'm actually thinking about writing very simple userspace camera, without autofocus, where user would just select "infinity"/"1m"/"50cm" ... and for that FOCUS_ABSOLUTE is equivalent to VOICE_COIL_CURRENT...

Quoted 3 lines
Quoted 1 line

Right, I still think movement mode should be standard control :)

What options would you like to see for movement mode?

I've discussed this with Sakari offline a few days ago. I won't nack this patch, but to ack it I'd like to have a better understanding of the big picture when it comes to focus and lens control. The proposed new control can make sense when taken in isolation, but I can't tell whether it still would when associated with the other controls that would be needed to properly control a voice coil lens.

If someone has analyzed the existing voice coil lens controllers and could share the result, in term of what parameters need to be controlled by the system and how they should be controlled, that would be very appreciated. Even better would be a real userspace implementation of a voice coil lens control algorithm.

Signature · 3 lines
Regards,

Laurent Pinchart
#50 lore raw

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

Hi!

Quoted 5 lines

If someone has analyzed the existing voice coil lens controllers and could share the result, in term of what parameters need to be controlled by the system and how they should be controlled, that would be very appreciated. Even better would be a real userspace implementation of a voice coil lens control algorithm.

Userspace implementation exists, it is called fcam-dev. What it does... Starts capture, selects focus speed, makes it go through focus range, looks for the sharpest image in the stream.

Then it computes time when the image was sharpest and thus lens position, and goes back there.

So for ad5820, we need basically focus position and focus speed. (And some 16/64 option).

Other coil drivers also have PWM vs. linear option.

Best regards,

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#51 lore raw

Re: [PATCH 1/1] v4l: Add camera voice coil lens control class, current control

In reply to Sakari Ailus

Hi!

Documentation/DocBook/media/v4l/controls.xml receiving given frequency when that control is set. This is a read-only control. · line 5511

Quoted 8 lines

-</section>

Documentation/DocBook/media/v4l/controls.xml +7 -0
+
+    <section id="voice-coil-controls">
+      <title>Voice Coil Control Reference</title>
+
+      <para>The Voice Coil class controls are used to control voice
+      coil lens devices. These are very simple devices that consist of
+      a voice coil, a spring and a lens. The current applied on a

"on the"?

Documentation/DocBook/media/v4l/controls.xml receiving given frequency when that control is set. This is a read-only control. · line 5513

Quoted 2 lines
Documentation/DocBook/media/v4l/controls.xml +2 -0
+      voice coil is used to move the lens away from the resting
+      position which typically is (close to) infinity.</para>

Insert explanation that this all is for autofocus somewhere?

include/uapi/linux/v4l2-controls.h enum v4l2_detect_md_mode { · line 978

Quoted 7 lines

/* User-class control IDs */

include/uapi/linux/v4l2-controls.h +1 -0
@@ -974,4 +975,10 @@ enum v4l2_detect_md_mode {
 #define V4L2_CID_DETECT_MD_THRESHOLD_GRID	(V4L2_CID_DETECT_CLASS_BASE + 3)
 #define V4L2_CID_DETECT_MD_REGION_GRID		(V4L2_CID_DETECT_CLASS_BASE + 4)
 
+/*  Voice coil lens driver control IDs defined by V4L2 */

Too many spaces after '/*'.

Otherwise, you have my "acked-by".

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#52 lore raw

PATCH v6 1/1 support for AD5820 camera auto-focus coil

In reply to Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
v4: remove header file.
v5: switch to devm_ , style cleanups, fixes
v6: remove new userspace APIs.

Can we finally get the patch in, please?

drivers/media/i2c/Kconfig +7 -0
index 993dc50..20e8e89 100644
@@ -279,6 +279,13 @@ config VIDEO_ML86V7667
 	  To compile this driver as a module, choose M here: the
 	  module will be called ml86v7667.
 
+config VIDEO_AD5820
+	tristate "AD5820 lens voice coil support"
+	depends on I2C && VIDEO_V4L2 && MEDIA_CONTROLLER
+	---help---
+	  This is a driver for the AD5820 camera lens voice coil.
+	  It is used for example in Nokia N900 (RX-51).
+
 config VIDEO_SAA7110
 	tristate "Philips SAA7110 video decoder"
 	depends on VIDEO_V4L2 && I2C
drivers/media/i2c/Makefile +1 -0
index 94f2c99..0216af0 100644
@@ -19,6 +19,7 @@ obj-$(CONFIG_VIDEO_SAA717X) += saa717x.o
 obj-$(CONFIG_VIDEO_SAA7127) += saa7127.o
 obj-$(CONFIG_VIDEO_SAA7185) += saa7185.o
 obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
+obj-$(CONFIG_VIDEO_AD5820)  += ad5820.o
 obj-$(CONFIG_VIDEO_ADV7170) += adv7170.o
 obj-$(CONFIG_VIDEO_ADV7175) += adv7175.o
 obj-$(CONFIG_VIDEO_ADV7180) += adv7180.o
drivers/media/i2c/ad5820.c new file +380 -0

380 lines not on this page · raw message

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Acked-by on v6 1/1
#53 lore raw
Quoted 5 lines · On Friday 05 August 2016 12:26:11 Pavel Machek wrote:

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Quoted 8 lines

---
v2: simple cleanups, fix error paths, simplify probe
v3: more cleanups, remove printk, add include
v4: remove header file.
v5: switch to devm_ , style cleanups, fixes
v6: remove new userspace APIs.

Can we finally get the patch in, please?

This patch is on ML for months or years, right?
Please merge it...

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
maintainer
#54 lore raw
In reply to Pavel Machek
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Signature · 4 lines
Cheers,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#55 lore raw
Quoted 9 lines · On Monday 08 August 2016 11:09:56 Sakari Ailus wrote:
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

Ok, and what with AD5820_RAMP_TIME and AD5820_RAMP_MODE?

Quoted 1 line

I've applied this to ad5820 branch in my tree.

Are you going to finally send this patch to media tree or pull request to Linus?

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
#56 lore raw
Quoted 6 lines · Pali Roh?r
Quoted 5 lines · On Monday 08 August 2016 11:09:56 Sakari Ailus wrote:
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Quoted 6 lines
Quoted 4 lines

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

Ok, and what with AD5820_RAMP_TIME and AD5820_RAMP_MODE?

Lets forget about those for now. I'll wait till current support works in the Linus' tree, then I can write the docs and re-add the ioctls.

Best regards,
Pavel

(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

maintainer
#57 lore raw
In reply to Pali Rohár
Quoted 11 lines · Pali Roh?r
Quoted 9 lines · On Monday 08 August 2016 11:09:56 Sakari Ailus wrote:
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

Quoted 6 lines

Ok, and what with AD5820_RAMP_TIME and AD5820_RAMP_MODE?

Quoted 1 line

I've applied this to ad5820 branch in my tree.

Are you going to finally send this patch to media tree or pull request to Linus?

That'll be through media-tree.

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#58 lore raw
In reply to Sakari Ailus
Quoted 11 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#59 lore raw
Quoted 8 lines · Pavel Machek
Quoted 7 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Quoted 8 lines
Quoted 4 lines

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#60 lore raw
Quoted 12 lines · Sakari Ailus
Quoted 11 lines · Pavel Machek
Quoted 10 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

Best regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#61 lore raw
Quoted 19 lines · Pavel Machek
Quoted 18 lines · Sakari Ailus
Quoted 16 lines · Pavel Machek
Quoted 11 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Quoted 6 lines
Quoted 1 line

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

N900. What else could it be? :-) :-)

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#62 lore raw
Quoted 20 lines · Sakari Ailus
Quoted 19 lines · Pavel Machek
Quoted 18 lines · Sakari Ailus
Quoted 16 lines · Pavel Machek
Quoted 11 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Quoted 8 lines
Quoted 6 lines
Quoted 1 line

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

N900. What else could it be? :-) :-)

Heh. Basically anything is easier to develop for than n900 :-(.

Ok, for real testing, Ivaylo's camera patchset is useful, so that you have picture to work with, plus your subdevs for omap3 patchset (which needs a forward port).

I have patches against v4.7, if you are interested.

I guess subdevs for omap3 should be merged at this point. Do you have any plans to do that, or should I take a look?

Best regards,

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
maintainer
#63 lore raw

Hi Pavel,

Quoted 23 lines · Pavel Machek
Quoted 22 lines · Sakari Ailus
Quoted 21 lines · Pavel Machek
Quoted 19 lines · Sakari Ailus
Quoted 8 lines · Pavel Machek
Quoted 7 lines · Sakari Ailus
Quoted 3 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Quoted 8 lines
Quoted 4 lines

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

N900. What else could it be? :-) :-)

Heh. Basically anything is easier to develop for than n900 :-(.

Is it?

I actually find the old Nokia devices very practical. It's easy to boot your own kernel and things just work... until musb broke a bit recently. It requires reconnecting the usb cable again to function.

I have to admit I mostly use an N9.

Quoted 6 lines

Ok, for real testing, Ivaylo's camera patchset is useful, so that you have picture to work with, plus your subdevs for omap3 patchset (which needs a forward port).

I have patches against v4.7, if you are interested.

They should be pretty close to mainline. The rebase should be very easy.

Patches against media-tree master branch would always be better naturally. :-)

Quoted 3 lines

I guess subdevs for omap3 should be merged at this point. Do you have any plans to do that, or should I take a look?

What's still missing? I think I've yet to check the et8ek8 driver and the device tree description is missing. That's what comes to mind right now.

Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#64 lore raw

Hi!

Quoted 9 lines
Quoted 1 line

Heh. Basically anything is easier to develop for than n900 :-(.

Is it?

I actually find the old Nokia devices very practical. It's easy to boot your own kernel and things just work... until musb broke a bit recently. It requires reconnecting the usb cable again to function.

I have to admit I mostly use an N9.

Well, yes, I guess it sucks less than most phones, but...

I wish I had working .5TB drive, and CPU fast enough to compile kernel in say hour, and enough memory to run emacs and g++ at the same time, ethernet connection, working RTC and real keyboard and monitor...

Development would be way easier if I could just disconnect the N900 peripherals and connect them to the PC. Ok, I can dream, right?

Quoted 5 lines
Quoted 2 lines

I guess subdevs for omap3 should be merged at this point. Do you have any plans to do that, or should I take a look?

What's still missing? I think I've yet to check the et8ek8 driver and the device tree description is missing. That's what comes to mind right now.

et8ek8 driver is important, yes. But there's the support for parsing sub-devices from the dt missing, too. This stuff (I believe it is originally from you).

Best regards,
Pavel

drivers/media/platform/omap3isp/isp.c +95 -23
index 5d54e2c..23d484c 100644
@@ -2098,10 +2151,51 @@ static int isp_of_parse_node(struct device *dev, struct device_node *node,
 	return 0;
 }
 
+static int isp_of_parse_node(struct device *dev, struct device_node *node,
+			     struct v4l2_async_notifier *notifier,
+			     u32 group_id, bool link)
+{
+	struct isp_async_subdev *isd;
+
+	isd = devm_kzalloc(dev, sizeof(*isd), GFP_KERNEL);
+	if (!isd) {
+		of_node_put(node);
+		return -ENOMEM;
+	}
+
+	notifier->subdevs[notifier->num_subdevs] = &isd->asd;
+
+	if (link) {
+		if (isp_of_parse_node_endpoint(dev, node, isd)) {
+			of_node_put(node);
+			return -EINVAL;
+		}
+
+		isd->asd.match.of.node = of_graph_get_remote_port_parent(node);
+		of_node_put(node);
+	} else {
+		isd->asd.match.of.node = node;
+	}
+
+	if (!isd->asd.match.of.node) {
+		dev_warn(dev, "bad remote port parent\n");
+		return -EINVAL;
+	}
+
+	isd->asd.match_type = V4L2_ASYNC_MATCH_OF;
+	isd->group_id = group_id;
+	notifier->num_subdevs++;
+
+	return 0;
+}
+
 static int isp_of_parse_nodes(struct device *dev,
 			      struct v4l2_async_notifier *notifier)
 {
 	struct device_node *node = NULL;
+	int ret;
+	unsigned int flash = 0;
+	u32 group_id = 0;
 
 	notifier->subdevs = devm_kcalloc(
 		dev, ISP_MAX_SUBDEVS, sizeof(*notifier->subdevs), GFP_KERNEL);
@@ -2110,30 +2204,57 @@ static int isp_of_parse_nodes(struct device *dev,
 
 	while (notifier->num_subdevs < ISP_MAX_SUBDEVS &&
 	       (node = of_graph_get_next_endpoint(dev->of_node, node))) {
-		struct isp_async_subdev *isd;
+		ret = isp_of_parse_node(dev, node, notifier, group_id++, true);
+		if (ret)
+			return ret;
+	}
 
-		isd = devm_kzalloc(dev, sizeof(*isd), GFP_KERNEL);
-		if (!isd) {
-			of_node_put(node);
-			return -ENOMEM;
-		}
+	while (notifier->num_subdevs < ISP_MAX_SUBDEVS &&
+	       (node = of_parse_phandle(dev->of_node, "ti,camera-flashes",
+					flash++))) {
+		struct device_node *sensor_node =
+			of_parse_phandle(dev->of_node, "ti,camera-flashes",
+					 flash++);
+		unsigned int i;
+		u32 flash_group_id;
+
+		if (!sensor_node)
+			return -EINVAL;
 
-		notifier->subdevs[notifier->num_subdevs] = &isd->asd;
+		for (i = 0; i < notifier->num_subdevs; i++) {
+			struct isp_async_subdev *isd = container_of(
+				notifier->subdevs[i], struct isp_async_subdev,
+				asd);
 
-		if (isp_of_parse_node(dev, node, isd)) {
-			of_node_put(node);
-			return -EINVAL;
+			if (!isd->bus)
+				continue;
+
+			dev_dbg(dev, "match \"%s\", \"%s\"\n",sensor_node->name,
+				isd->asd.match.of.node->name);
+
+			if (sensor_node != isd->asd.match.of.node)
+				continue;
+
+			dev_dbg(dev, "found\n");
+
+			flash_group_id = isd->group_id;
+			break;
 		}
 
-		isd->asd.match.of.node = of_graph_get_remote_port_parent(node);
-		of_node_put(node);
-		if (!isd->asd.match.of.node) {
-			dev_warn(dev, "bad remote port parent\n");
-			return -EINVAL;
+		/*
+		 * No sensor was found --- complain and allocate a new
+		 * group ID.
+		 */
+		if (i == notifier->num_subdevs) {
+			dev_warn(dev, "no device node \"%s\" was found",
+				 sensor_node->name);
+			flash_group_id = group_id++;
 		}
 
-		isd->asd.match_type = V4L2_ASYNC_MATCH_OF;
-		notifier->num_subdevs++;
+		ret = isp_of_parse_node(dev, node, notifier, flash_group_id,
+					false);
+		if (ret)
+			return ret;
 	}
 
 	return notifier->num_subdevs;
@@ -2146,8 +2267,9 @@ static int isp_subdev_notifier_bound(struct v4l2_async_notifier *async,
 	struct isp_async_subdev *isd =
 		container_of(asd, struct isp_async_subdev, asd);
 
+//	subdev->entity.group_id = isd->group_id;
 	isd->sd = subdev;
-	isd->sd->host_priv = &isd->bus;
+	isd->sd->host_priv = isd->bus;
 
 	return 0;
 }
@@ -2350,12 +2472,15 @@ static int isp_probe(struct platform_device *pdev)
 	if (ret < 0)
 		goto error_register_entities;
 
-	isp->notifier.bound = isp_subdev_notifier_bound;
-	isp->notifier.complete = isp_subdev_notifier_complete;
+	if (IS_ENABLED(CONFIG_OF) && pdev->dev.of_node) {
+		isp->notifier.bound = isp_subdev_notifier_bound;
+		isp->notifier.complete = isp_subdev_notifier_complete;
 
-	ret = v4l2_async_notifier_register(&isp->v4l2_dev, &isp->notifier);
-	if (ret)
-		goto error_register_entities;
+		ret = v4l2_async_notifier_register(&isp->v4l2_dev,
+						   &isp->notifier);
+		if (ret)
+			goto error_register_entities;
+	}
 
 	isp_core_init(isp, 1);
 	omap3isp_put(isp);
drivers/media/platform/omap3isp/isp.h +2 -1
index 7e6f663..639b3ca 100644
@@ -228,8 +228,9 @@ struct isp_device {
 
 struct isp_async_subdev {
 	struct v4l2_subdev *sd;
-	struct isp_bus_cfg bus;
+	struct isp_bus_cfg *bus;
 	struct v4l2_async_subdev asd;
+	u32 group_id;
 };
 
 #define v4l2_dev_to_isp_device(dev) \
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#65 lore raw
In reply to Sakari Ailus

Hi!

Quoted 11 lines
Quoted 10 lines
Quoted 8 lines
Quoted 6 lines
Quoted 1 line

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

N900. What else could it be? :-) :-)

Heh. Basically anything is easier to develop for than n900 :-(.

Quoted 7 lines

Is it?

I actually find the old Nokia devices very practical. It's easy to boot your own kernel and things just work... until musb broke a bit recently. It requires reconnecting the usb cable again to function.

I have to admit I mostly use an N9.

Well, if you compare that to development on PC, I prefer PC.

Even arm development boards are usually easier, as they don't need too complex userspace, and do have working serial ports.

But I do have a serial adapter for N900 now (thanks, sre), so my main problem now is that N900 takes a lot of time to boot into usable state.

Best regards,
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161103/fd30267c/attachment.sig>
maintainer
#66 lore raw
Quoted 21 lines · Pavel Machek

Hi!

Quoted 11 lines
Quoted 10 lines
Quoted 8 lines
Quoted 6 lines
Quoted 1 line

Yeah. I just compiled it but haven't tested it. I presume it'll work. :-)

I'm testing it on n900. I guess simpler hardware with ad5820 would be better for the test...

What hardware do you have?

N900. What else could it be? :-) :-)

Heh. Basically anything is easier to develop for than n900 :-(.

Quoted 7 lines

Is it?

I actually find the old Nokia devices very practical. It's easy to boot your own kernel and things just work... until musb broke a bit recently. It requires reconnecting the usb cable again to function.

I have to admit I mostly use an N9.

Quoted 8 lines

Well, if you compare that to development on PC, I prefer PC.

Even arm development boards are usually easier, as they don't need too complex userspace, and do have working serial ports.

But I do have a serial adapter for N900 now (thanks, sre), so my main problem now is that N900 takes a lot of time to boot into usable state.

Yeah... I just upgraded my Debian installation (armel over NFS) a few major numbers and I find it a lot slower than it used to do. I presume that's mostly because of systemd...

Signature · 2 lines
Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#67 lore raw

Hi!

Quoted 7 lines
Quoted 7 lines
Quoted 1 line

I have to admit I mostly use an N9.

Well, if you compare that to development on PC, I prefer PC.

Even arm development boards are usually easier, as they don't need too complex userspace, and do have working serial ports.

Quoted 7 lines
Quoted 3 lines

But I do have a serial adapter for N900 now (thanks, sre), so my main problem now is that N900 takes a lot of time to boot into usable state.

Yeah... I just upgraded my Debian installation (armel over NFS) a few major numbers and I find it a lot slower than it used to do. I presume that's mostly because of systemd...

I'm not sure if systemd is to blame. (I'm booting into full GUI...)

And yes, I noticed the slowdown in Debian 7 -> 8 transition, so I'm basically staying at Debian 7 as far as I can.

Best regards,
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161104/7f029ae6/attachment.sig>
#68 lore raw
Quoted 13 lines · Pavel Machek

Hi!

Quoted 11 lines
Quoted 10 lines
Quoted 1 line

I have to admit I mostly use an N9.

Well, if you compare that to development on PC, I prefer PC.

Even arm development boards are usually easier, as they don't need too complex userspace, and do have working serial ports.

But I do have a serial adapter for N900 now (thanks, sre), so my main problem now is that N900 takes a lot of time to boot into usable state.

Quoted 8 lines
Quoted 3 lines

Yeah... I just upgraded my Debian installation (armel over NFS) a few major numbers and I find it a lot slower than it used to do. I presume that's mostly because of systemd...

I'm not sure if systemd is to blame. (I'm booting into full GUI...)

And yes, I noticed the slowdown in Debian 7 -> 8 transition, so I'm basically staying at Debian 7 as far as I can.

Maybe it's the armel vs armhf causing the slowdown?

Regards,

Tony

#69 lore raw
In reply to Pavel Machek
Quoted 10 lines · On Monday 08 August 2016 23:41:32 Pavel Machek wrote:
Quoted 9 lines · Sakari Ailus
Quoted 2 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

Quoted 8 lines
Quoted 1 line

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Best regards,
Pavel

Was DTS patch merged into 4.9? At least I do not see updated that dts file omap3-n900.dts in linus tree...

Signature · 9 lines
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161214/d8addaf7/attachment-0001.sig>
#70 lore raw
Quoted 17 lines · Pali Roh?r
Quoted 16 lines · On Monday 08 August 2016 23:41:32 Pavel Machek wrote:
Quoted 10 lines · Sakari Ailus
Quoted 2 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Quoted 5 lines
Quoted 2 lines

Best regards,
Pavel

Was DTS patch merged into 4.9? At least I do not see updated that dts file omap3-n900.dts in linus tree...

If it's not in current mainline or next, it's off my radar so sounds like I've somehow missed it and needs resending..

Tony

maintainer
#71 lore raw

Hi Pali and Tony,

Quoted 18 lines · Tony Lindgren
Quoted 17 lines · Pali Roh?r
Quoted 16 lines · On Monday 08 August 2016 23:41:32 Pavel Machek wrote:
Quoted 10 lines · Sakari Ailus
Quoted 2 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Best regards,
Pavel

Was DTS patch merged into 4.9? At least I do not see updated that dts file omap3-n900.dts in linus tree...

If it's not in current mainline or next, it's off my radar so sounds like I've somehow missed it and needs resending..

Where's this patch? I remember seeing the driver patch and the DT documentation but no actual DT source patch for the N900.

Signature · 4 lines
Kind regards,

Sakari Ailus
e-mail: sakari.ailus at iki.fi	XMPP: sailus at retiisi.org.uk
#72 lore raw

Hi!

Quoted 23 lines

Hi Pali and Tony,

Quoted 21 lines · Tony Lindgren
Quoted 20 lines · Pali Roh?r
Quoted 18 lines · On Monday 08 August 2016 23:41:32 Pavel Machek wrote:
Quoted 10 lines · Sakari Ailus
Quoted 2 lines · Pavel Machek

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone.

Thanks, Pavel!

Let's use V4L2_CID_FOCUS_ABSOLUTE, as is in the patch. If we get something better in the future, we'll switch to that then.

I've applied this to ad5820 branch in my tree.

Thanks. If I understands things correctly, both DTS patch and this patch are waiting in your tree, so we should be good to go for 4.9 (unless some unexpected problems surface)?

Best regards,
Pavel

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Was DTS patch merged into 4.9? At least I do not see updated that dts file omap3-n900.dts in linus tree...

If it's not in current mainline or next, it's off my radar so sounds like I've somehow missed it and needs resending..

Where's this patch? I remember seeing the driver patch and the DT documentation but no actual DT source patch for the N900.

The patch was not yet submitted. Autofocus coil is not too useful withou camera support, and we don't yet have support for v4l subdevs for omap3. I have it in the camera tree, but there are still pieces to be done before this is useful.

Best regards,
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161219/39969b35/attachment.sig>