From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Todor Tomov <todor.tomov@linaro.org>,
mchehab@kernel.org, hansverk@cisco.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] [media] ov5645: I2C address change
Date: Wed, 04 Oct 2017 13:47:22 +0300 [thread overview]
Message-ID: <3073637.dhNDna4gKQ@avalon> (raw)
In-Reply-To: <20171004103008.g7azpn4a3hfj4fs2@valkosipuli.retiisi.org.uk>
CC'ing the I2C mainling list and the I2C maintainer.
On Wednesday, 4 October 2017 13:30:08 EEST Sakari Ailus wrote:
> Hi Todor,
>
> On Mon, Oct 02, 2017 at 04:28:45PM +0300, Todor Tomov wrote:
> > As soon as the sensor is powered on, change the I2C address to the one
> > specified in DT. This allows to use multiple physical sensors connected
> > to the same I2C bus.
> >
> > Signed-off-by: Todor Tomov <todor.tomov@linaro.org>
>
> The smiapp driver does something similar and I understand Laurent might be
> interested in such functionality as well.
>
> It'd be nice to handle this through the I²C framework instead and to define
> how the information is specified through DT. That way it could be made
> generic, to work with more devices than just this one.
>
> What do you think?
>
> Cc Laurent.
>
> > ---
> >
> > drivers/media/i2c/ov5645.c | 42 ++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 42 insertions(+)
> >
> > diff --git a/drivers/media/i2c/ov5645.c b/drivers/media/i2c/ov5645.c
> > index d28845f..8541109 100644
> > --- a/drivers/media/i2c/ov5645.c
> > +++ b/drivers/media/i2c/ov5645.c
> > @@ -33,6 +33,7 @@
> > #include <linux/i2c.h>
> > #include <linux/init.h>
> > #include <linux/module.h>
> > +#include <linux/mutex.h>
> > #include <linux/of.h>
> > #include <linux/of_graph.h>
> > #include <linux/regulator/consumer.h>
> > @@ -42,6 +43,8 @@
> > #include <media/v4l2-fwnode.h>
> > #include <media/v4l2-subdev.h>
> >
> > +static DEFINE_MUTEX(ov5645_lock);
> > +
> > #define OV5645_VOLTAGE_ANALOG 2800000
> > #define OV5645_VOLTAGE_DIGITAL_CORE 1500000
> > #define OV5645_VOLTAGE_DIGITAL_IO 1800000
> > @@ -590,6 +593,31 @@ static void ov5645_regulators_disable(struct ov5645
> > *ov5645)
> > dev_err(ov5645->dev, "io regulator disable failed\n");
> > }
> >
> > +static int ov5645_write_reg_to(struct ov5645 *ov5645, u16 reg, u8 val,
> > + u16 i2c_addr)
> > +{
> > + u8 regbuf[3] = {
> > + reg >> 8,
> > + reg & 0xff,
> > + val
> > + };
> > + struct i2c_msg msgs = {
> > + .addr = i2c_addr,
> > + .flags = 0,
> > + .len = 3,
> > + .buf = regbuf
> > + };
> > + int ret;
> > +
> > + ret = i2c_transfer(ov5645->i2c_client->adapter, &msgs, 1);
> > + if (ret < 0)
> > + dev_err(ov5645->dev,
> > + "%s: write reg error %d on addr 0x%x: reg=0x%x, val=0x%x\n",
> > + __func__, ret, i2c_addr, reg, val);
> > +
> > + return ret;
> > +}
> > +
> > static int ov5645_write_reg(struct ov5645 *ov5645, u16 reg, u8 val)
> > {
> > u8 regbuf[3];
> > @@ -729,10 +757,24 @@ static int ov5645_s_power(struct v4l2_subdev *sd,
> > int on)
> > */
> > if (ov5645->power_count == !on) {
> > if (on) {
> > + mutex_lock(&ov5645_lock);
> > +
> > ret = ov5645_set_power_on(ov5645);
> > if (ret < 0)
> > goto exit;
> >
> > + ret = ov5645_write_reg_to(ov5645, 0x3100,
> > + ov5645->i2c_client->addr, 0x78);
> > + if (ret < 0) {
> > + dev_err(ov5645->dev,
> > + "could not change i2c address\n");
> > + ov5645_set_power_off(ov5645);
> > + mutex_unlock(&ov5645_lock);
> > + goto exit;
> > + }
> > +
> > + mutex_unlock(&ov5645_lock);
> > +
> > ret = ov5645_set_register_array(ov5645,
> > ov5645_global_init_setting,
> > ARRAY_SIZE(ov5645_global_init_setting));
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-10-04 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 13:28 [PATCH] [media] ov5645: I2C address change Todor Tomov
2017-10-04 10:30 ` Sakari Ailus
2017-10-04 10:47 ` Laurent Pinchart [this message]
2017-10-09 8:36 ` Todor Tomov
2017-10-09 9:34 ` Sakari Ailus
2017-10-09 12:52 ` Laurent Pinchart
2017-10-09 16:18 ` Todor Tomov
2017-10-09 19:13 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3073637.dhNDna4gKQ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hansverk@cisco.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=todor.tomov@linaro.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.