From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Gerald Loacker <gerald.loacker@wolfvision.net>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 0/2] media: imx415: Add more clock configurations
Date: Fri, 19 Jan 2024 14:21:32 +0100 [thread overview]
Message-ID: <3602834.R56niFO833@steina-w> (raw)
In-Reply-To: <20240108105242.GC20868@pendragon.ideasonboard.com>
Hi Laurent,
Am Montag, 8. Januar 2024, 11:52:42 CET schrieb Laurent Pinchart:
> On Tue, Dec 12, 2023 at 08:26:35AM +0100, Alexander Stein wrote:
> > Hi,
> >
> > this small series converts the driver to using CCI helpers.
> > On top of that more clock setups are added to the driver.
> > These are all taken from the datasheet. I suspect they all can be
> > calculated dynamically later on.
> > Tested on TQMa8MPxL + MBa8MPxL + ISP + Vision Components IMX415 camera.
> >
> > While working on the driver I notived that imx415 sets mbus code to
> > MEDIA_BUS_FMT_SGBRG10_1X10, while imx290 uses MEDIA_BUS_FMT_SRGGB10_1X10.
> > But the datasheets show the same color coding pattern. But both settings
> > seem to be correct, e.g. the resulting image has correct colors.
>
> The difference may be in the crop settings, of possibly flipping.
I checked the flip ("inverted operation") settings on both sensors. The
readout direction seems to be identical. Cropping areas are a bit different,
and currently unconfigured. But left margin is 12, so I don't see how that
could effect color order.
Best regards,
Alexander
> > I had to remove the identity check locally. I suspect that Vision
> > Components interjects reading some registers.
> :
> :-(
>
> I'm getting increasingly annoyed by vendors who play such tricks.
>
> > Changes in v2:
> > * Removed explicit selection of REGMAP_I2C
> > * Dropped patch 3 for now. Mode selection shall be done by dynamic
> > VMAX/HMAX>
> > calculations later on
> >
> > Best regards,
> > Alexander
> >
> > Alexander Stein (2):
> > media: i2c: imx415: Convert to new CCI register access helpers
> > media: i2c: imx415: Add more clock configurations
> >
> > drivers/media/i2c/Kconfig | 1 +
> > drivers/media/i2c/imx415.c | 651 +++++++++++++++++++++++--------------
> > 2 files changed, 416 insertions(+), 236 deletions(-)
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
prev parent reply other threads:[~2024-01-19 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 7:26 [PATCH v2 0/2] media: imx415: Add more clock configurations Alexander Stein
2023-12-12 7:26 ` [PATCH v2 1/2] media: i2c: imx415: Convert to new CCI register access helpers Alexander Stein
2024-01-08 10:50 ` Laurent Pinchart
2024-01-10 7:29 ` Alexander Stein
2023-12-12 7:26 ` [PATCH v2 2/2] media: i2c: imx415: Add more clock configurations Alexander Stein
2023-12-12 7:36 ` [PATCH v2 0/2] media: " Alexander Stein
2024-01-08 10:52 ` Laurent Pinchart
2024-01-19 13:21 ` Alexander Stein [this message]
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=3602834.R56niFO833@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=gerald.loacker@wolfvision.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@wolfvision.net \
--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