From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>,
linux-media@vger.kernel.org, a.hajda@samsung.com,
sakari.ailus@iki.fi, hverkuil@xs4all.nl,
kyungmin.park@samsung.com, sw0312.kim@samsung.com
Subject: Re: Media_build broken by [PATCH RFC v3 5/5] m5mols: Implement .get_frame_desc subdev callback
Date: Tue, 09 Oct 2012 13:38:20 +0200 [thread overview]
Message-ID: <50740CAC.2040009@samsung.com> (raw)
In-Reply-To: <2290105.hTRlMPSUYP@avalon>
Hi Laurent
On 10/08/2012 10:42 PM, Laurent Pinchart wrote:
> Hi,
>
> When did the {get,set}_frame_desc subdev operations reach mainline ? Last I
> knew is that they were an RFC, and they're now suddenly in, without even one
> ack from an embedded v4l developer :-S I'm not totally happy with that.
Sorry to hear now you have issues with those patches. I've sent a pull request
on last Wednesday [1], after 3 RFC versions of the whole change set. I've Cced
many people on these patches, including you and Sakari. I have addressed comments
to some patches you raised and I felt you're generally OK or don't have
objections (since there was no comments on some patches and I explicitly
mentioned there I'd like to get them in v3.7). I'm sorry if it was otherwise.
The problem I'm trying to address with those patches have been there for us for
over _one year_ [1], making JPEG capture with s5p-fimc effectively unusable in
the mainline kernel.
We've decided extending struct v4l2_mbus_framefmt was not an option, since it
is exposed to user-space now. Also using controls turned out to not be helpful,
since multiple values need to be passed, where there are multiple logical
streams transmitted by e.g. CSI-2 transmitter in single video frame [2].
It seemed like there is a general agreement on LMML to use the frame
descriptor callbacks instead. These callbacks are all in-kernel API and can
be changed any time. I'll be happy adapt the drivers to whatever sane changes
are proposed. I've stated in the commit description it's just an preliminary
form. And it at least let's us to move forward and carry on with more serious
problems.
I'll try to do better on letting people know, when sending things upstream
in future.
--
Regards,
Sylwester
[1] http://patchwork.linuxtv.org/patch/14875
[2] https://patchwork.kernel.org/patch/1365451
prev parent reply other threads:[~2012-10-09 11:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 15:54 [PATCH RFC v3 0/5] s5p-fimc: Add interleaved image data capture support Sylwester Nawrocki
2012-09-26 15:54 ` [PATCH RFC v3 1/5] V4L: Add V4L2_MBUS_FMT_S5C_UYVY_JPEG_1X8 media bus format Sylwester Nawrocki
2012-09-26 15:54 ` [PATCH RFC v3 2/5] V4L: Add V4L2_PIX_FMT_S5C_UYVY_JPG fourcc definition Sylwester Nawrocki
2012-09-27 11:10 ` Laurent Pinchart
[not found] ` <50648A55.9020100@gmail.com>
2012-09-27 23:22 ` Laurent Pinchart
2012-09-26 15:54 ` [PATCH RFC v3 3/5] s5p-csis: Add support for non-image data packets capture Sylwester Nawrocki
2012-09-26 15:54 ` [PATCH RFC v3 4/5] s5p-fimc: Add support for V4L2_PIX_FMT_S5C_UYVY_JPG fourcc Sylwester Nawrocki
2012-09-26 15:54 ` [PATCH RFC v3 5/5] m5mols: Implement .get_frame_desc subdev callback Sylwester Nawrocki
2012-10-06 15:24 ` Media_build broken by " Jan Hoogenraad
2012-10-06 18:23 ` Sylwester Nawrocki
2012-10-06 18:43 ` Jan Hoogenraad
2012-10-06 21:34 ` Sylwester Nawrocki
2012-10-07 1:19 ` Michael West
2012-10-07 9:55 ` Hans Verkuil
2012-10-07 11:13 ` Sylwester Nawrocki
2012-10-08 13:03 ` Hans Verkuil
2012-10-10 1:05 ` Mauro Carvalho Chehab
2012-10-10 6:27 ` Hans Verkuil
2012-10-10 9:34 ` Sylwester Nawrocki
2012-10-10 10:39 ` Mauro Carvalho Chehab
2012-10-10 10:52 ` Hans Verkuil
2012-10-10 10:57 ` Mauro Carvalho Chehab
2012-10-08 20:42 ` Laurent Pinchart
2012-10-09 11:38 ` Sylwester Nawrocki [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=50740CAC.2040009@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.hajda@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=jan-conceptronic@hoogenraad.net \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sw0312.kim@samsung.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.