All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacopo mondi <jacopo@jmondi.org>
To: Adam Ford <aford173@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	steve_longerbeam@mentor.com,
	Jagan Teki <jagan@amarulasolutions.com>,
	p.zabel@pengutronix.de, Fabio Estevam <fabio.estevam@nxp.com>,
	gstreamer-devel@lists.freedesktop.org,
	linux-media@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux
Date: Tue, 6 Nov 2018 09:27:27 +0100	[thread overview]
Message-ID: <20181106082727.GW15991@w540> (raw)
In-Reply-To: <CAHCN7xKs=wO9dxVAo=yxjWm10jH6TmAfgYwAfAd=J2uBT3rK1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2474 bytes --]

Hi Adam,

On Mon, Nov 05, 2018 at 04:32:33PM -0600, Adam Ford wrote:
> On Mon, Oct 29, 2018 at 8:49 AM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > Hi Adam,
> >
> > On Sun, Oct 28, 2018 at 3:58 PM Adam Ford <aford173@gmail.com> wrote:
> >
> > > Does anyone know when the media branch get's merged into the mainline
> > > kernel?  I assume we're in the merge window with 4.19 just having been
> > > released.  Once these have been merged into the mainline, I'll go
> > > through and start requesting they get pulled into 4.19 and/or 4.14
> > > if/when appropriate.
> >
> > This should happen in 4.20-rc1, which will probably be out next  Sunday.
> I sent an e-mail to stable with a list of a variety of patches for the
> ov5640 to be applied to 4.19.y  So far all looks pretty good, but I
> think I found on minor bug:

Thanks!

>
> If I attempt to change just the resolution, it doesn't take.
>
> Initial read
> media-ctl --get-v4l2 "'ov5640 2-0010':0"
> [fmt:UYVY8_2X8/640x480@1/30 field:none colorspace:srgb xfer:srgb
> ycbcr:601 quantization:full-range]
>
> Change resolution
> # media-ctl --set-v4l2 "'ov5640 2-0010':0[fmt:UYVY2X8/720x480 field:none]"
>
> Read it back
> # media-ctl --get-v4l2 "'ov5640 2-0010':0"
> [fmt:UYVY8_2X8/640x480@1/30 field:none colorspace:srgb xfer:srgb
> ycbcr:601 quantization:full-range]
>
> However, if I change the resolution AND the format to something other
> than UYVY2x8, the resolution changes. I can then change the format
> back to UYVY and capture and stream video at 1080p and 720x480.
> I can work around this, but I thought I'd mention it.  I was trying to
> figure out a patch to apply to the mailing list myself, but I wasn't
> able to fix it quickly.

Thanks, you are right, this is a known issue :(

There have been patches to address this issue floating around the
mailing list, none of them has yet made it up to inclusion.

Sam has sent a patch to fix this:
https://patchwork.linuxtv.org/patch/52489/

Hugues had something similar I cannot find, if I'm not wrong, and I
carry myself the patch I posted in the patchwork discussion in my
trees.

Feel free to go through the media list and comment. One more report on
this would help to increase chances to have one of those patches
re-sent and then included.

Also, bug reports are always very welcome, but to maximize the chances
they receive the required attention, could you make a new email thread
next time and drop this one please?

Thanks
  j

>
> adam
> adam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2018-11-06  8:27 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 15:09 i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux Jagan Teki
2018-05-31 16:10 ` Nicolas Dufresne
2018-05-31 16:25   ` Jagan Teki
2018-05-31 19:06 ` Philipp Zabel
2018-06-01  5:19   ` Jagan Teki
2018-06-01  9:53     ` Sakari Ailus
2018-06-01 11:41       ` Jagan Teki
2018-06-29 21:46     ` Fabio Estevam
2018-06-29 21:46       ` Fabio Estevam
2018-07-03 18:41       ` jacopo mondi
2018-07-03 18:41         ` jacopo mondi
2018-07-04  0:18         ` Fabio Estevam
2018-07-04  0:18           ` Fabio Estevam
2018-07-04  5:18         ` Jagan Teki
2018-07-04  5:18           ` Jagan Teki
2018-07-04  6:57           ` Jagan Teki
2018-07-04  6:57             ` Jagan Teki
2018-07-04 14:26             ` Fabio Estevam
2018-07-04 14:26               ` Fabio Estevam
     [not found]           ` <588A2275-4D45-442D-8B38-7A17C27BED10@gmail.com>
2018-07-04  6:59             ` Jagan Teki
2018-07-04  6:59               ` Jagan Teki
2018-07-04  7:11               ` chain256
2018-07-04  7:11                 ` chain256
2018-09-20 14:56 ` jacopo mondi
2018-09-20 14:56   ` jacopo mondi
2018-10-16 19:46   ` Adam Ford
2018-10-17  0:13     ` Steve Longerbeam
2018-10-17  8:01       ` jacopo mondi
2018-10-19 13:45         ` Adam Ford
2018-10-19 19:42           ` Adam Ford
2018-10-22 11:33             ` jacopo mondi
2018-10-22 12:25               ` Adam Ford
2018-10-22 12:40                 ` Fabio Estevam
2018-10-22 12:40                   ` Fabio Estevam
2018-10-23 15:19                   ` Adam Ford
2018-10-23 16:36                     ` Steve Longerbeam
2018-10-23 17:34                       ` Adam Ford
2018-10-23 17:39                         ` Steve Longerbeam
2018-10-23 17:54                           ` Adam Ford
2018-10-23 18:11                             ` Steve Longerbeam
2018-10-23 23:03                             ` jacopo mondi
2018-10-24 13:53                               ` Adam Ford
2018-10-24 14:08                                 ` jacopo mondi
2018-10-24 14:17                                   ` Adam Ford
2018-10-28 18:57                                     ` Adam Ford
2018-10-29 13:49                                       ` Fabio Estevam
2018-10-29 13:49                                         ` Fabio Estevam
2018-11-05 22:32                                         ` Adam Ford
2018-11-06  8:27                                           ` jacopo mondi [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=20181106082727.GW15991@w540 \
    --to=jacopo@jmondi.org \
    --cc=aford173@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=gstreamer-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=steve_longerbeam@mentor.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.