From: Sakari Ailus <sakari.ailus@iki.fi>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: devicetree@vger.kernel.org, c.barrett@framos.com,
linux-kernel@vger.kernel.org, a.brela@framos.com,
robh+dt@kernel.org, mchehab@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3 2/3] media: i2c: Add IMX290 CMOS image sensor driver
Date: Thu, 3 Oct 2019 10:16:46 +0300 [thread overview]
Message-ID: <20191003071646.GZ896@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <20191003053338.GA7868@Mani-XPS-13-9360>
Hi Manivannan,
On Thu, Oct 03, 2019 at 11:03:38AM +0530, Manivannan Sadhasivam wrote:
....
> > > > > +static int imx290_set_gain(struct imx290 *imx290, u32 value)
> > > > > +{
> > > > > + int ret;
> > > > > +
> > > > > + u32 adjusted_value = (value * 10) / 3;
> > > >
> > > > What's the purpose of this? Why not to use the value directly?
> > > >
> > >
> > > The gain register accepts the value 10/3 of the actual gain required. Hence,
> > > we need to manually do the calculation before updating the value. I can
> > > add a comment here to clarify.
> >
> > It's better to use the register value directly. Otherwise the granularity
> > won't be available to the user space.
> >
>
> The sensor datasheet clearly defines that the 10/3'rd of the expected gain
> should be set to this register. So, IMO we should be setting the value as
The unit of that gain is decibels, but the controls do not have a unit.
Register value is really preferred here.
> mentioned in the datasheet. I agree that we are missing the userspace
> granularity here but sticking to the device limitation shouldn't be a problem.
> As I said, I'll add a comment here to clarify.
The comment isn't visible in the uAPI.
>
> > >
> > > > > +
> > > > > + ret = imx290_write_buffered_reg(imx290, IMX290_GAIN, 1, adjusted_value);
> > > > > + if (ret)
> > > > > + dev_err(imx290->dev, "Unable to write gain\n");
> > > > > +
> > > > > + return ret;
> > > > > +}
> > > > > +
> > > > > +static int imx290_set_power_on(struct imx290 *imx290)
> > > > > +{
> > > > > + int ret;
> > > > > +
> > > > > + ret = clk_prepare_enable(imx290->xclk);
> > > >
> > > > Please move the code from this function to the runtime PM runtime suspend
> > > > callback. The same for imx290_set_power_off().
> > > >
> > >
> > > May I know why? I think since this is being used only once, you're suggesting
> > > to move to the callback function itself but please see the comment below. I
> > > will reuse this function to power on the device during probe.
> >
> > Yes, you can call the same function from probe, even if it's used as a
> > runtime PM callback.
> >
> > There's no need to have a function that acts as a wrapper for calling it
> > with a different type of an argument.
> >
>
> You mean directly calling imx290_runtime_resume() from probe is fine?
Yes. Feel free to call it e.g. imx290_power_on or something.
--
Regards,
Sakari Ailus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-03 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 9:19 [PATCH v3 0/3] Add IMX290 CMOS image sensor support Manivannan Sadhasivam
2019-08-30 9:19 ` [PATCH v3 1/3] dt-bindings: media: i2c: Add IMX290 CMOS sensor binding Manivannan Sadhasivam
2019-08-30 9:19 ` [PATCH v3 2/3] media: i2c: Add IMX290 CMOS image sensor driver Manivannan Sadhasivam
2019-09-23 9:22 ` Sakari Ailus
2019-10-01 18:42 ` Manivannan Sadhasivam
2019-10-02 10:37 ` Sakari Ailus
2019-10-03 5:33 ` Manivannan Sadhasivam
2019-10-03 7:16 ` Sakari Ailus [this message]
2019-10-03 7:26 ` Manivannan Sadhasivam
2019-10-03 14:22 ` Sakari Ailus
2019-08-30 9:19 ` [PATCH v3 3/3] MAINTAINERS: Add entry for " Manivannan Sadhasivam
2019-09-23 9:07 ` Sakari Ailus
2019-10-01 18:43 ` Manivannan Sadhasivam
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=20191003071646.GZ896@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=a.brela@framos.com \
--cc=c.barrett@framos.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).