From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Ricardo Ribalda Delgado <ribalda@kernel.org>
Cc: git@apitzsch.eu, Mauro Carvalho Chehab <mchehab@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: Re: [PATCH v2 01/13] media: i2c: imx214: Fix link frequency
Date: Fri, 1 Nov 2024 09:09:54 +0000 [thread overview]
Message-ID: <ZySa4gBDjJS7q-yI@kekkonen.localdomain> (raw)
In-Reply-To: <CAPybu_0o+csbkyS7bbMUjB+VSUwj2DK_STy=wubCT_frH0DzgA@mail.gmail.com>
Hi Ricardo, André,
On Wed, Oct 30, 2024 at 12:25:25PM +0100, Ricardo Ribalda Delgado wrote:
> Hi Andre
>
> On Mon, Oct 21, 2024 at 12:14 AM André Apitzsch via B4 Relay
> <devnull+git.apitzsch.eu@kernel.org> wrote:
> >
> > From: André Apitzsch <git@apitzsch.eu>
> >
> > The driver defines IMX214_DEFAULT_LINK_FREQ 480000000, and then
> > IMX214_DEFAULT_PIXEL_RATE ((IMX214_DEFAULT_LINK_FREQ * 8LL) / 10),
> > which works out as 384MPix/s. (The 8 is 4 lanes and DDR.)
> >
> > Parsing the PLL registers with the defined 24MHz input. We're in single
> > PLL mode, so MIPI frequency is directly linked to pixel rate. VTCK ends
> > up being 1200MHz, and VTPXCK and OPPXCK both are 120MHz. Section 5.3
> > "Frame rate calculation formula" says "Pixel rate
> > [pixels/s] = VTPXCK [MHz] * 4", so 120 * 4 = 480MPix/s, which basically
> > agrees with my number above.
> >
> > 3.1.4. MIPI global timing setting says "Output bitrate = OPPXCK * reg
> > 0x113[7:0]", so 120MHz * 10, or 1200Mbit/s. That would be a link
> > frequency of 600MHz due to DDR.
> > That also matches to 480MPix/s * 10bpp / 4 lanes / 2 for DDR.
> >
> I think your calculations are correct and the value should be 600M...
> but if we land this change, there will be boards that will stop
> working until they update their dts.
> Not sure if we allow that.
>
> Can we move this change to the last one of the series and add something like:
>
> diff --git a/drivers/media/i2c/imx214.c b/drivers/media/i2c/imx214.c
> index 2aca3d88a0a7..8b4ded4cb5ce 100644
> --- a/drivers/media/i2c/imx214.c
> +++ b/drivers/media/i2c/imx214.c
> @@ -1281,13 +1281,9 @@ static int imx214_parse_fwnode(struct device
> *dev, struct imx214 *imx214)
> if (bus_cfg.link_frequencies[i] == IMX214_DEFAULT_LINK_FREQ)
> break;
>
> - if (i == bus_cfg.nr_of_link_frequencies) {
> - dev_err_probe(dev, -EINVAL,
> - "link-frequencies %d not supported,
> Please review your DT\n",
> + if (i == bus_cfg.nr_of_link_frequencies)
> + dev_warn(dev, "link-frequencies %d not supported,
> Please review your DT. Continuing anyway\n",
> IMX214_DEFAULT_LINK_FREQ);
I'd also add a check it's the frequency supported by the driver previously,
not any frequency. There will be problems if 480 MHz will be actually
supported in the future.
> - ret = -EINVAL;
> - goto done;
> - }
>
>
>
> > Signed-off-by: André Apitzsch <git@apitzsch.eu>
> > ---
> > drivers/media/i2c/imx214.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/i2c/imx214.c b/drivers/media/i2c/imx214.c
> > index 4962cfe7c83d62425aeccb46a400fa93146f14ea..5d411452d342fdb177619cd1c9fd9650d31089bb 100644
> > --- a/drivers/media/i2c/imx214.c
> > +++ b/drivers/media/i2c/imx214.c
> > @@ -24,7 +24,7 @@
> > #define IMX214_MODE_STREAMING 0x01
> >
> > #define IMX214_DEFAULT_CLK_FREQ 24000000
> > -#define IMX214_DEFAULT_LINK_FREQ 480000000
> > +#define IMX214_DEFAULT_LINK_FREQ 600000000
> > #define IMX214_DEFAULT_PIXEL_RATE ((IMX214_DEFAULT_LINK_FREQ * 8LL) / 10)
> > #define IMX214_FPS 30
> > #define IMX214_MBUS_CODE MEDIA_BUS_FMT_SRGGB10_1X10
> >
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-11-01 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 22:13 [PATCH v2 00/13] media: i2c: imx214: Miscellaneous cleanups and improvements André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 01/13] media: i2c: imx214: Fix link frequency André Apitzsch via B4 Relay
2024-10-30 11:25 ` Ricardo Ribalda Delgado
2024-11-01 9:09 ` Sakari Ailus [this message]
2024-10-20 22:13 ` [PATCH v2 02/13] media: i2c: imx214: Use subdev active state André Apitzsch via B4 Relay
2024-10-30 11:36 ` Ricardo Ribalda Delgado
2024-12-01 18:41 ` André Apitzsch
2024-10-20 22:13 ` [PATCH v2 03/13] media: i2c: imx214: Simplify with dev_err_probe() André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 04/13] media: i2c: imx214: Convert to CCI register access helpers André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 05/13] media: i2c: imx214: Replace register addresses with macros André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 06/13] media: i2c: imx214: Drop IMX214_REG_EXPOSURE from mode reg arrays André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 07/13] media: i2c: imx214: Check number of lanes from device tree André Apitzsch via B4 Relay
2024-10-30 11:38 ` Ricardo Ribalda Delgado
2024-10-30 21:17 ` André Apitzsch
2024-10-20 22:13 ` [PATCH v2 08/13] media: i2c: imx214: Add vblank and hblank controls André Apitzsch via B4 Relay
2024-10-30 11:57 ` Ricardo Ribalda Delgado
2024-10-20 22:13 ` [PATCH v2 09/13] media: i2c: imx214: Extract format and crop settings André Apitzsch via B4 Relay
2024-10-30 12:10 ` Ricardo Ribalda Delgado
2024-11-20 20:07 ` André Apitzsch
2024-11-20 21:22 ` Ricardo Ribalda Delgado
2024-11-22 10:43 ` Sakari Ailus
2024-12-01 18:23 ` André Apitzsch
2024-10-20 22:13 ` [PATCH v2 10/13] media: i2c: imx214: Implement vflip/hflip controls André Apitzsch via B4 Relay
2024-10-30 12:13 ` Ricardo Ribalda Delgado
2024-10-20 22:13 ` [PATCH v2 11/13] media: i2c: imx214: Add analogue/digital gain control André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 12/13] media: i2c: imx214: Verify chip ID André Apitzsch via B4 Relay
2024-10-20 22:13 ` [PATCH v2 13/13] media: i2c: imx214: Add test pattern control André Apitzsch via B4 Relay
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=ZySa4gBDjJS7q-yI@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=git@apitzsch.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=ribalda@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®