public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Daniel Scally <djrscally@gmail.com>
Cc: paul.kocialkowski@bootlin.com, ezequiel@collabora.com,
	hverkuil-cisco@xs4all.nl, linux-media@vger.kernel.org,
	yong.zhi@intel.com, bingbu.cao@intel.com, tian.shu.qiu@intel.com,
	kevin.lhopital@bootlin.com, yang.lee@linux.alibaba.com,
	andy.shevchenko@gmail.com, laurent.pinchart@ideasonboard.com,
	kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v2 04/12] media: i2c: Support 19.2MHz input clock in ov8865
Date: Wed, 11 Aug 2021 00:49:18 +0300	[thread overview]
Message-ID: <20210810214918.GL3@paasikivi.fi.intel.com> (raw)
In-Reply-To: <711e4f6d-f539-0a69-fe78-d5e32eecb673@gmail.com>

On Tue, Aug 10, 2021 at 10:37:35PM +0100, Daniel Scally wrote:
> Hi Sakari - thanks for all the comments

You're welcome!

Nice patches btw.

> 
> On 10/08/2021 14:34, Sakari Ailus wrote:
> > Hi Daniel,
> >
> > Thanks for the set.
> >
> > On Mon, Aug 09, 2021 at 11:58:37PM +0100, Daniel Scally wrote:
> >> The ov8865 driver as written expects a 24MHz input clock, but the sensor
> >> is sometimes found on x86 platforms with a 19.2MHz input clock supplied.
> >> Add a set of PLL configurations to the driver to support that rate too.
> >> As ACPI doesn't auto-configure the clock rate, check for a clock-frequency
> >> during probe and set that rate if one is found.
> >>
> >> Signed-off-by: Daniel Scally <djrscally@gmail.com>
> >> ---
> >> Changes in v2:
> >>
> >> 	- Added an enum defining the possible frequency rates to index the
> >> 	  array (Andy)
> >>
> >>  drivers/media/i2c/ov8865.c | 164 +++++++++++++++++++++++++++----------
> >>  1 file changed, 121 insertions(+), 43 deletions(-)
> >>
> >> diff --git a/drivers/media/i2c/ov8865.c b/drivers/media/i2c/ov8865.c
> >> index fe700787bfb9..1382b16d1a09 100644
> >> --- a/drivers/media/i2c/ov8865.c
> >> +++ b/drivers/media/i2c/ov8865.c
> >> @@ -21,10 +21,6 @@
> >>  #include <media/v4l2-image-sizes.h>
> >>  #include <media/v4l2-mediabus.h>
> >>  
> >> -/* Clock rate */
> >> -
> >> -#define OV8865_EXTCLK_RATE			24000000
> >> -
> >>  /* Register definitions */
> >>  
> >>  /* System */
> >> @@ -567,6 +563,19 @@ struct ov8865_sclk_config {
> >>  	unsigned int sclk_div;
> >>  };
> >>  
> >> +/* Clock rate */
> >> +
> >> +enum extclk_rate {
> >> +	OV8865_19_2_MHZ,
> >> +	OV8865_24_MHZ,
> >> +	OV8865_NUM_SUPPORTED_RATES,
> >> +};
> >> +
> >> +static const unsigned long supported_extclk_rates[] = {
> >> +	[OV8865_19_2_MHZ] = 19200000,
> >> +	[OV8865_24_MHZ] = 24000000,
> >> +};
> >> +
> >>  /*
> >>   * General formulas for (array-centered) mode calculation:
> >>   * - photo_array_width = 3296
> >> @@ -665,6 +674,9 @@ struct ov8865_sensor {
> >>  	struct regulator *avdd;
> >>  	struct regulator *dvdd;
> >>  	struct regulator *dovdd;
> >> +
> >> +	unsigned long extclk_rate;
> >> +	enum extclk_rate extclk_rate_idx;
> >>  	struct clk *extclk;
> >>  
> >>  	struct v4l2_fwnode_endpoint endpoint;
> >> @@ -680,49 +692,83 @@ struct ov8865_sensor {
> >>  /* Static definitions */
> >>  
> >>  /*
> >> - * EXTCLK = 24 MHz
> >>   * PHY_SCLK = 720 MHz
> >>   * MIPI_PCLK = 90 MHz
> >>   */
> >> -static const struct ov8865_pll1_config ov8865_pll1_config_native = {
> >> -	.pll_pre_div_half	= 1,
> >> -	.pll_pre_div		= 0,
> >> -	.pll_mul		= 30,
> >> -	.m_div			= 1,
> >> -	.mipi_div		= 3,
> >> -	.pclk_div		= 1,
> >> -	.sys_pre_div		= 1,
> >> -	.sys_div		= 2,
> >> +
> >> +static const struct ov8865_pll1_config ov8865_pll1_configs_native[] = {
> >> +	{ /* 19.2 MHz input clock */
> >> +		.pll_pre_div_half	= 1,
> >> +		.pll_pre_div		= 2,
> >> +		.pll_mul		= 75,
> >> +		.m_div			= 1,
> >> +		.mipi_div		= 3,
> >> +		.pclk_div		= 1,
> >> +		.sys_pre_div		= 1,
> >> +		.sys_div		= 2,
> >> +	},
> >> +	{ /* 24MHz input clock */
> >> +		.pll_pre_div_half	= 1,
> >> +		.pll_pre_div		= 0,
> >> +		.pll_mul		= 30,
> >> +		.m_div			= 1,
> >> +		.mipi_div		= 3,
> >> +		.pclk_div		= 1,
> >> +		.sys_pre_div		= 1,
> >> +		.sys_div		= 2,
> >> +	},
> > Could you instead add a struct specific to the clock frequency with
> > pointers to these? See e.g. the ov8856 driver how this could otherwise end
> > up...
> 
> 
> You mean something like
> 
> 
> static struct ov8865_pll_configs_19_2_mhz {
> 
>     .pll1_config_native = &ov8865_pll1_config_native,
> 
>     ...
> 
> };
> 
> 
> 
> static struct ov8865_pll_configs_24_mhz {
> 
>     .pll1_config_native = &ov8865_pll1_config_native,
> 
>     ...
> 
> };
> 
> 
> or am I misunderstanding?

Yes, please --- ov8865_pll1_config_native above is thus the PLL
configuration for the 24 MHz clock.

-- 
Sakari Ailus

  reply	other threads:[~2021-08-10 21:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 22:58 [PATCH v2 00/12] Extensions to ov8865 driver Daniel Scally
2021-08-09 22:58 ` [PATCH v2 01/12] media: i2c: Add ACPI support to ov8865 Daniel Scally
2021-08-10 12:57   ` Andy Shevchenko
2021-08-09 22:58 ` [PATCH v2 02/12] media: i2c: Fix incorrect value in comment Daniel Scally
2021-08-09 22:58 ` [PATCH v2 03/12] media: i2c: Defer probe if not endpoint found Daniel Scally
2021-08-09 22:58 ` [PATCH v2 04/12] media: i2c: Support 19.2MHz input clock in ov8865 Daniel Scally
2021-08-10 13:04   ` Andy Shevchenko
2021-08-10 21:46     ` Daniel Scally
2021-08-10 13:34   ` Sakari Ailus
2021-08-10 21:37     ` Daniel Scally
2021-08-10 21:49       ` Sakari Ailus [this message]
2021-09-07 22:44         ` Daniel Scally
2021-09-08  6:52           ` Sakari Ailus
2021-08-09 22:58 ` [PATCH v2 05/12] media: i2c: Add .get_selection() support to ov8865 Daniel Scally
2021-08-10 13:38   ` Sakari Ailus
2021-08-24 23:17     ` Daniel Scally
2021-08-25  7:16       ` Sakari Ailus
2021-08-25  8:04         ` Laurent Pinchart
2021-08-25  8:29           ` Sakari Ailus
2021-08-09 22:58 ` [PATCH v2 06/12] media: i2c: Switch control to V4L2_CID_ANALOGUE_GAIN Daniel Scally
2021-08-10 13:48   ` Sakari Ailus
2021-08-09 22:58 ` [PATCH v2 07/12] media: i2c: Add vblank control to ov8865 Daniel Scally
2021-08-09 22:58 ` [PATCH v2 08/12] media: i2c: Add hblank " Daniel Scally
2021-08-10 13:10   ` Andy Shevchenko
2021-08-10 14:29   ` Sakari Ailus
2021-08-10 22:07     ` Daniel Scally
2021-08-13  3:05       ` Laurent Pinchart
2021-08-13  9:45         ` Daniel Scally
2021-08-14 20:56           ` Laurent Pinchart
2021-09-09 22:36             ` Daniel Scally
2021-10-09 23:10               ` Daniel Scally
2021-08-09 22:58 ` [PATCH v2 09/12] media: i2c: cap exposure at height + vblank in ov8865 Daniel Scally
2021-08-10 14:30   ` Sakari Ailus
2021-08-09 22:58 ` [PATCH v2 10/12] media: i2c: Add controls from fwnode to ov8865 Daniel Scally
2021-08-09 22:58 ` [PATCH v2 11/12] media: i2c: Switch exposure control unit to lines Daniel Scally
2021-08-09 22:58 ` [PATCH v2 12/12] media: ipu3-cio2: Add INT347A to cio2-bridge Daniel Scally
2021-08-10 13:12   ` Andy Shevchenko

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=20210810214918.GL3@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bingbu.cao@intel.com \
    --cc=djrscally@gmail.com \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=kevin.lhopital@bootlin.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=tian.shu.qiu@intel.com \
    --cc=yang.lee@linux.alibaba.com \
    --cc=yong.zhi@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