From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 1/2] media: platform: transfer format translations to soc_mediabus
Date: Wed, 06 Apr 2016 08:43:15 +0200 [thread overview]
Message-ID: <8760vvutj0.fsf@belgarion.home> (raw)
In-Reply-To: <Pine.LNX.4.64.1604060549100.12238@axis700.grange> (Guennadi Liakhovetski's message of "Wed, 6 Apr 2016 05:53:36 +0200 (CEST)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
Hi Guennadi,
> Not sure I understand, what should the purpose of this patch be?
See in [1].
> Why do you want to move some function(s) from one file to another? And you
> aren't even calling the new soc_mbus_build_fmts_xlate() function
I'm calling it in pxa_camera_build_formats() in patch 2/2.
> and you aren't replacing the currently used analogous
> soc_camera_init_user_formats() function.
I'm doing that in patch 2/2.
> Or was this patch not-to-be-reviewed?
Actually these 2 patches are designed to be discussion openers :)
For me, their purpose is to expose the transition of pxa_camera out of
soc_camera and see if the chosen path is good, or if there exists a better one.
In other words, these patches show that :
- in a first stage, soc_mediabus should be kept [1]
=> at least for formats translation (soc_mbus_build_fmts_xlate())
=> and for used formats by sensors
=> this is why patch 1/1 exists
- the conversion almost doesn't touch the pxa_camera_() core functions (IP
manipulation), which is good, and only touch the upper layer
- that soc_mediabus adherence removal will be another task
- the amount of code which is shifted from soc_camera to pxa_camera
- the functionalities that are lost through conversion which should be readded
later
=> cropping is one
=> pixel clock sensing is another one
All in all, before submitting patch for real, ie. not in RFC mode, I wanted to
be sure the proposed conversion is sound, and compare to other drivers
conversion to see if we were going in the same direction.
As to whether this patch should be reviewed or not, I'd say that I was just
expecting to have an "that might be the way to go" or "NAK, wrong patch, let's
do something else instead".
Cheers.
--
Robert
next prev parent reply other threads:[~2016-04-06 6:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 14:26 [PATCH RFC v2 0/2] pxa_camera transition to v4l2 standalone device Robert Jarzmik
2016-04-02 14:26 ` [PATCH RFC v2 1/2] media: platform: transfer format translations to soc_mediabus Robert Jarzmik
2016-04-06 3:53 ` Guennadi Liakhovetski
2016-04-06 6:43 ` Robert Jarzmik [this message]
2016-07-04 9:23 ` Hans Verkuil
2016-07-12 17:14 ` Robert Jarzmik
2016-04-02 14:26 ` [PATCH RFC v2 2/2] media: platform: pxa_camera: make a standalone v4l2 device Robert Jarzmik
2016-07-04 9:40 ` Hans Verkuil
2016-07-31 15:03 ` Robert Jarzmik
2016-08-01 8:02 ` Hans Verkuil
2016-04-03 17:47 ` [PATCH RFC v2 0/2] pxa_camera transition to v4l2 standalone device Hans Verkuil
2016-04-04 6:20 ` Robert Jarzmik
2016-07-04 9:15 ` Hans Verkuil
2016-07-04 16:05 ` Robert Jarzmik
2016-07-04 9:44 ` Hans Verkuil
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=8760vvutj0.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox