From: khalasa@piap.pl (Krzysztof Hałasa)
To: Fabio Estevam <festevam@gmail.com>
Cc: Steve Longerbeam <slongerbeam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media <linux-media@vger.kernel.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH][MEDIA]i.MX6 CSI: Fix MIPI camera operation in RAW/Bayer mode
Date: Tue, 17 Oct 2017 15:26:19 +0200 [thread overview]
Message-ID: <m3376hlxc4.fsf@t19.piap.pl> (raw)
In-Reply-To: <CAOMZO5A6PYfXz6T4ZTs7M3rtUZLKOjf636i-v6uCjxNfxETQyQ@mail.gmail.com> (Fabio Estevam's message of "Tue, 17 Oct 2017 09:33:08 -0200")
Fabio Estevam <festevam@gmail.com> writes:
>> --- a/drivers/staging/media/imx/imx-media-csi.c
>> +++ b/drivers/staging/media/imx/imx-media-csi.c
>> @@ -340,7 +340,7 @@ static int csi_idmac_setup_channel(struct csi_priv *priv)
>> case V4L2_PIX_FMT_SGBRG8:
>> case V4L2_PIX_FMT_SGRBG8:
>> case V4L2_PIX_FMT_SRGGB8:
>> - burst_size = 8;
>> + burst_size = 16;
>> passthrough = true;
>> passthrough_bits = 8;
>> break;
>
> Russell has sent the same fix and Philipp made a comment about the
> possibility of using 32-byte or 64-byte bursts:
> http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2017-October/111960.html
Great.
Sometimes I wonder how many people are working on exactly the same
stuff.
--
Krzysztof Halasa
Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next prev parent reply other threads:[~2017-10-17 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 6:27 [PATCH][MEDIA]i.MX6 CSI: Fix MIPI camera operation in RAW/Bayer mode Krzysztof Hałasa
2017-10-17 11:33 ` Fabio Estevam
2017-10-17 13:26 ` Krzysztof Hałasa [this message]
2017-10-17 13:53 ` Russell King - ARM Linux
2017-10-17 14:27 ` Fabio Estevam
2017-10-17 15:24 ` Philipp Zabel
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=m3376hlxc4.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=slongerbeam@gmail.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.