Linux Media Controller development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] media: i2c: IMX296 camera sensor driver
Date: Tue, 5 Nov 2019 22:41:23 +0200	[thread overview]
Message-ID: <20191105204123.GG4869@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20191105150355.GA674@Mani-XPS-13-9360>

Hi Mani,

On Tue, Nov 05, 2019 at 08:33:55PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Nov 04, 2019 at 03:42:06PM +0200, Laurent Pinchart wrote:
> > On Fri, Nov 01, 2019 at 08:22:46PM +0530, Manivannan Sadhasivam wrote:
> >> On Thu, Oct 31, 2019 at 03:23:09PM +0200, Laurent Pinchart wrote:
> >>> The IMX296LLR is a monochrome 1.60MP CMOS sensor from Sony. The driver
> >>> supports cropping and binning (but not both at the same time due to
> >>> hardware limitations) and exposure, gain, vertical blanking and test
> >>> pattern controls.
> >>> 
> >>> Preliminary support is also included for the color IMX296LQR sensor.
> >>> 
> >>> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >>> ---
> >>> This driver is a parallel implementation of IMX296 support, compatible
> >>> with the DT bindings submitted by Mani in
> >>> https://lore.kernel.org/linux-media/20191030094902.32582-1-manivannan.sadhasivam@linaro.org/.
> >>> 
> >>>  drivers/media/i2c/Kconfig  |   12 +
> >>>  drivers/media/i2c/Makefile |    1 +
> >>>  drivers/media/i2c/imx296.c | 1026 ++++++++++++++++++++++++++++++++++++
> >>>  3 files changed, 1039 insertions(+)
> >>>  create mode 100644 drivers/media/i2c/imx296.c

[snip]

> >>> diff --git a/drivers/media/i2c/imx296.c b/drivers/media/i2c/imx296.c
> >>> new file mode 100644
> >>> index 000000000000..4140637983fd
> >>> --- /dev/null
> >>> +++ b/drivers/media/i2c/imx296.c

[snip]

> >>> +struct imx296 {
> >>> +	struct device *dev;
> >>> +	struct clk *clk;
> >>> +	struct regulator *supply;
> >> 
> >> Any plan to use 3 power supplies as discussed in bindings patch?
> > 
> > I'd like to reach a conclusion on that discussion first :-) Do you think
> > we should add them right away, or only when needed ? There's no issue
> > with backward compatibility, if we start with one power supply only the
> > next two would be optional.
> 
> The use of single power supply still doesn't look good to me. Could you please
> add all of them?

I can give this a try. I'm annoyed that it will make my DT more complex
as I have a single controllable power supply from which the three sensor
supplies are derived. Could you share the sensor DT fragment for your
platform to give me a second example ?

[snip]

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2019-11-05 20:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 13:23 [PATCH] media: i2c: IMX296 camera sensor driver Laurent Pinchart
2019-10-31 14:25 ` Sakari Ailus
2019-11-04 13:33   ` Laurent Pinchart
2019-11-04 15:20     ` Sakari Ailus
2019-11-04 18:59     ` Laurent Pinchart
2019-11-04 21:30       ` Sakari Ailus
2019-11-05 20:36         ` Laurent Pinchart
2019-11-05 20:59           ` Sakari Ailus
2019-11-01 14:52 ` Manivannan Sadhasivam
2019-11-01 17:37   ` Sakari Ailus
2019-11-04 13:42   ` Laurent Pinchart
2019-11-04 21:08     ` Rob Herring
2019-11-04 22:03       ` Laurent Pinchart
2019-11-04 22:15         ` Rob Herring
2019-11-05 15:03     ` Manivannan Sadhasivam
2019-11-05 17:24       ` Sakari Ailus
2019-11-05 20:38         ` Laurent Pinchart
2019-11-05 20:41       ` Laurent Pinchart [this message]
2020-11-26 15:59 ` 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=20191105204123.GG4869@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /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