All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org, jacopo@jmondi.org
Subject: Re: Re: Re: Re: hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2
Date: Wed, 06 Jul 2022 15:12:01 +0200	[thread overview]
Message-ID: <3706363.QJadu78ljV@steina-w> (raw)
In-Reply-To: <YsWJBEPhp9WhiYe1@p310.k.g>

Am Mittwoch, 6. Juli 2022, 15:07:16 CEST schrieb Petko Manolov:
> On 22-07-06 08:18:20, Alexander Stein wrote:
> > Thanks! Indeed at a first glance it looks straight forward. I was trying
> > to
> > get an imx327 running on a imx8mm, called TQMa8MxML. See [1] for some
> > details. The cover letter describes the config setup. The media-ctl
> > commands might help your setup. Note the settle times are an ugly bitch
> > and are crucial to be set on my board, but I'm not sure why they have to
> > be that way. Patch 1-8 are obsolete by now with the updates to
> > drivers/media/platform/nxp/
> > imx-mipi-csis.c. Patch 9 might help you configure the DT.
> 
> Right, media-ctl is it.  In fact the pipelines have been properly set up so
> i only had to change the format.  The attached media graph is below
> 
> Now, there are two problems i'm stumbling upon.  One is related to the
> capture device not actually supporting imx492 format(s), which are:
> 
> 	MEDIA_BUS_FMT_SGBRG10_1X10
> 	MEDIA_BUS_FMT_SGBRG12_1X12
> 
> which i guess is why i am being greeted with (when using v4l2-ctl):
> 
> 	imx7-csi 32e20000.csi: capture format not valid

In your media topology in entity 1 (csi) "colorspace:srgb xfer:srgb" is set 
for both sink and source. In my case it's "colorspace:raw xfer:none". The 
imx327 is also a bayer pattern camera, so I would expect these kind of 
settings have to be the same. But again I'm no expert which is pretty annoying 
if you don't know which component/driver/configuration you can trust.

best regards,
Alexander






  reply	other threads:[~2022-07-06 13:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  7:55 hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2 Petko Manolov
2022-06-29  8:28 ` Laurent Pinchart
2022-06-29  8:45   ` Petko Manolov
2022-06-30  0:50     ` Laurent Pinchart
2022-06-30 18:52       ` Petko Manolov
2022-06-30 19:42         ` Laurent Pinchart
2022-07-05  9:43           ` Petko Manolov
2022-07-05 12:30             ` Petko Manolov
2022-07-05 14:42             ` Alexander Stein
2022-07-05 15:13               ` Petko Manolov
2022-07-06  6:18                 ` Alexander Stein
2022-07-06 13:07                   ` Petko Manolov
2022-07-06 13:12                     ` Alexander Stein [this message]
2022-07-06 13:51                     ` Laurent Pinchart
2022-07-06 19:26                       ` Petko Manolov
2022-07-06 20:07                         ` Petko Manolov
2022-07-06 21:48                           ` Laurent Pinchart
2022-07-07 12:20                             ` Petko Manolov
2022-07-06 21:47                         ` Laurent Pinchart
2022-07-07 12:17                           ` Petko Manolov
2022-07-07 21:47                             ` Laurent Pinchart

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=3706363.QJadu78ljV@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=petko.manolov@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.