V2. Fixed issues pointed by Mauro.
regards
Antti
The following changes since commit c02ef64aab828d80040b5dce934729312e698c33:
[media] cx23885: add DVBSky T982(Dual DVB-T2/T/C) support (2014-11-14
18:28:41 -0200)
are available in the git repository at:
git://linuxtv.org/anttip/media_tree
Load SDR sub-driver in order to support SDR for devices having
this tuner too.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
b/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
ind
Implement partial PIP mode to carry TS from slave demodulator,
through that master demodulator. RTL2832 demod has TS input
interface to connected another demodulator TS output.
Signed-off-by: Antti Palosaari
---
drivers/media/dvb-frontends/rtl2832.c | 60 +--
driv
That logic was duplicated from rtl2832_sdr.h in order to avoid hard
dependency for staging directory. rtl2832_sdr is moved to media, so
we could remove that code now.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 20 +---
1 file changed, 1 insertion
Better to rename tuner I2C to something which clearly says it is
for tuner as there is now multiple different I2C clients used.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 6 +++---
drivers/media/usb/dvb-usb-v2/rtl28xxu.h | 2 +-
2 files changed, 4 insertions(+),
There is RTL2832P devices having extra MN88472 demodulator. This
patch add support for such configuration. Logically MN88472 slave
demodulator is connected to RTL2832 master demodulator, both I2C
bus and TS input. RTL2832 is integrated to RTL2832U and RTL2832P
chips. Chip version RTL2832P has extra
There is RTL2832P devices having extra MN88473 demodulator. This
patch add support for such configuration. Logically MN88473 slave
demodulator is connected to RTL2832 master demodulator, both I2C
bus and TS input. RTL2832 is integrated to RTL2832U and RTL2832P
chips. Chip version RTL2832P has extra
On Tue, Nov 18, 2014 at 07:40:15AM +0200, Sakari Ailus wrote:
> since v2:
This obviously should have been v1.
Also a spelling fix in documentation has been included, as Hans suggested.
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk
--
To unsubscribe from this list:
The SMIA compatible sensors only need a single clock.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers/media/i2c/smiapp/smiapp-core.c
index ba05d97..b02f
Register and unregister async sub-device for DT.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers/media/i2c/smiapp/smiapp-core.c
index a
Remove FSF's address information from the license header in the smiapp
driver and the smiapp-pll PLL calculator. This should no longer be needed,
and would be rendered outdated in case the FSF chooses to relocate its
office.
Signed-off-by: Sakari Ailus
Cc: Timo Ahonen
---
drivers/media/i2c/smia
This is part of the smiapp driver.
Signed-off-by: Sakari Ailus
---
MAINTAINERS |1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a6288ca..2378a5f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8618,6 +8618,7 @@ F:drivers/media/i2c/smiapp/
F: incl
The registered callback is called by the V4L2 async framework after the
bound callback. This allows separating the functionality in the registered
callback so that on DT based systems only sub-device registration is done
there.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core
Signed-off-by: Sakari Ailus
---
include/media/smiapp.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/media/smiapp.h b/include/media/smiapp.h
index 0b8f124..268a3cd 100644
--- a/include/media/smiapp.h
+++ b/include/media/smiapp.h
@@ -65,19 +65,19 @@ struc
Hi folks,
This patchset adds support for Device tree in the smiapp driver. Platform
data support is retained as well. The actual DT related changes are
prepended by a few simple cleanups.
In the case of platform data, ISPs that provide clocks to the sensor must
probe before the sensor does. Accessing the sensor does require the clocks,
and thus, probe cannot access the sensor in such a system.
This limitation does not exist in the case of the DT. Perform all
initialisation except M
Document the smiapp device tree properties.
Signed-off-by: Sakari Ailus
Cc: devicet...@vger.kernel.org
---
.../devicetree/bindings/media/i2c/nokia,smia.txt | 68
MAINTAINERS|1 +
2 files changed, 69 insertions(+)
create mode 1
link-frequency is a 64-bit unsigned integer array of allowed link
frequencies.
Signed-off-by: Sakari Ailus
Cc: devicet...@vger.kernel.org
---
Documentation/devicetree/bindings/media/video-interfaces.txt |3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/m
struct device has a forward declaration in the header already. The header is
only needed in the .c file.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp-pll.c |1 +
drivers/media/i2c/smiapp-pll.h |2 --
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/media/
Platform data support is retained.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 100 +++-
1 file changed, 98 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers/media/i2c/smiapp/smiapp-core.c
index
The V4L2_SEL_TGT_NATIVE_SIZE target is used to denote e.g. the size of a
sensor's pixel array.
Signed-off-by: Sakari Ailus
---
Documentation/DocBook/media/v4l/selections-common.xml | 10 ++
include/uapi/linux/v4l2-common.h |2 ++
2 files changed, 12 insertions(
The sub-device format documentation documented scaling configuration through
formats. Instead the compose selection rectangle is elsewhere documented to
be used for the purpose. Remove scaling related part of the documentation.
Signed-off-by: Sakari Ailus
---
Documentation/DocBook/media/v4l/dev-
Add input and output capability flags for setting native size of the device,
and document them.
Signed-off-by: Sakari Ailus
---
Documentation/DocBook/media/v4l/vidioc-enuminput.xml |8
Documentation/DocBook/media/v4l/vidioc-enumoutput.xml |8
include/uapi/linux/videode
Hi all,
This small set cleans up sub-device format documentation --- the
documentation noted the source format is used to configure scaling, which
was contradicting what was said right after on the selections on
sub-devices. This part was written before the s
The fields were previously uninitialised, leaving the returned values to
where the user had set them. This was never the intention.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
Add support for selection target V4L2_SEL_TGT_NATIVE_SIZE. It is equivalent
of what V4L2_SEL_TGT_CROP_BOUNDS used to be. Support for
V4L2_SEL_TGT_CROP_BOUNDS is still supported by the driver as a compatibility
interface.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c |
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Tue Nov 18 04:00:15 CET 2014
git branch: test
git hash: c02ef64aab828d80040b5dce934729312e698c33
gcc versio
Signed-off-by: Dean Anderson
---
drivers/media/usb/s2255/s2255drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/s2255/s2255drv.c
b/drivers/media/usb/s2255/s2255drv.c
index a56a05b..82014bb 100644
--- a/drivers/media/usb/s2255/s2255drv.c
+++ b/drivers/med
Hi Robert,
On Mon, Nov 17, 2014 at 4:55 PM, Robert Schwebel
wrote:
> Philipp is on vacation this week, he can have a look when he is back in
> the office next monday.
Thanks for letting me know.
> Just a wild guess - we usually test here with dmabuf capable devices and
> without X. As you are
Hi Fabio,
On Mon, Nov 17, 2014 at 03:29:17PM -0200, Fabio Estevam wrote:
> I am running linux-next 20141117 on a mx6qsabresd board and trying to
> play a mp4 video via Gstreamer 1.4.1, but I am getting the following
> error:
>
> root@imx6qsabresd:/mnt/nfs# gst-play-1.0 sample.mp
Hi Andrey,
On Mon, Nov 17, 2014 at 3:48 PM, Andrey Utkin
wrote:
> could you give `lspci -v` so that i see what module is a driver for
> that component?
I am using a mx6 processor that has a built-in hardware video
encoder/decoder. The driver is located at drivers/media/platform/coda/
Thanks
--
Hi Nicolas,
On Mon, Nov 17, 2014 at 3:45 PM, Nicolas Dufresne
wrote:
> Note, I'm only commenting about the GStreamer side...
>
> Le 2014-11-17 12:29, Fabio Estevam a écrit :
>> Hi,
>>
>> I am running linux-next 20141117 on a mx6qsabresd board and trying to
>>
could you give `lspci -v` so that i see what module is a driver for
that component?
Try playing to same device with recent ffmpeg: ffmpeg -i sample.mp4
-codec copy -f v4l2 -y /dev/videoWhatYouHave
and check if you have the same kernel warning.
--
Bluecherry developer.
--
To unsubscribe from this
Note, I'm only commenting about the GStreamer side...
Le 2014-11-17 12:29, Fabio Estevam a écrit :
> Hi,
>
> I am running linux-next 20141117 on a mx6qsabresd board and trying to
> play a mp4 video via Gstreamer 1.4.1, but I am getting the following
> error:
You should upd
On 11/17/2014 05:47 PM, Andrey Utkin wrote:
> Dear linux-media maintainers, I fail to do `git am` on mbox-formatted
> patch downloadable from https://patchwork.linuxtv.org/patch/26970/
> so i worry if the Krzyztof's patch i resubmitted is well-formed, and
> whether you are fine with integration of
Hi,
I am running linux-next 20141117 on a mx6qsabresd board and trying to
play a mp4 video via Gstreamer 1.4.1, but I am getting the following
error:
root@imx6qsabresd:/mnt/nfs# gst-play-1.0 sample.mp4
Volume: 100%
Now playing /mnt/nfs/sample.mp4
[ 506.983809] [ cut here
Signed-off-by: Andrey Utkin
---
MAINTAINERS | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index bb38f02..f5cef1b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8787,7 +8787,9 @@ S:Maintained
F: drivers/leds/leds-net48xx.c
SOFTLOGI
Dear linux-media maintainers, I fail to do `git am` on mbox-formatted
patch downloadable from https://patchwork.linuxtv.org/patch/26970/
so i worry if the Krzyztof's patch i resubmitted is well-formed, and
whether you are fine with integration of this patch to media_tree and
further to upstream. Pl
I have a Terratec S7 USB device(actually an Elgato EyeTV Sat). This
works fine on a Mac Mini running EyeTV. It doesn't seem to scan DVB-S2
channels at all under Linux-DVB. I've noticed numerous messages in the
mailing list archive documenting problems with this device in regards to
S2. The only mai
This happens always, and I noticed it quite long time ago. At the
moment I have 1 mbit internet link, but AFAIR it was the same with
much bigger bandwidth.
20:17:06krieger@zver /usr/local/src/linux-next
$ git remote add verk_media_tree git://linuxtv.org/hverkuil/media_tree.git
[OK]
20:17:16kriege
Hi Olli,
re ' we start to have quite a list of chips there in the printouts
(Si2147/Si2148/Si2157/Si2158) and
more is coming -...
Should we just say "Si214x/Si215x" there or something?'
I'd see merit to show the supported chips explicitly as otherwise users
may be confused if a new unsupported ch
On Thu, Nov 6, 2014 at 12:29 AM, Grazvydas Ignotas wrote:
> On Wed, Nov 5, 2014 at 4:05 PM, Laurent Pinchart
> wrote:
>> Hi Rémi,
>>
>> On Tuesday 04 November 2014 22:41:44 Rémi Denis-Courmont wrote:
>>> Le mardi 04 novembre 2014, 15:42:37 Rémi Denis-Courmont a écrit :
>>> > Le 2014-11-04 14:58,
Hi Boris,
On Sun, Nov 16, 2014 at 09:24:38AM +0100, Boris Brezillon wrote:
> Add RGB444_1X12 and RGB565_1X16 format definitions and update the
> documentation.
>
> Signed-off-by: Boris Brezillon
> Acked-by: Mauro Carvalho Chehab
> ---
> Changes since v1:
> - keep BPP and bits per sample orderin
On Monday 17 November 2014 16:06:17 Tony Lindgren wrote:
> * Pali Rohár [141117 07:03]:
> > On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> > > There's nothing stopping us from initializing the camera
> > > code from pdata-quirks.c for now to keep it working.
> > > Certainly the binding
Hi Hans,
On Mon, Nov 17, 2014 at 10:34:37AM +0100, Hans Verkuil wrote:
> On 11/16/2014 05:40 PM, Sakari Ailus wrote:
> > Hi Hans,
> >
> > Thank you for the review.
> >
> > On Fri, Nov 14, 2014 at 09:46:54AM +0100, Hans Verkuil wrote:
> >> On 11/09/2014 12:04 AM, Sakari Ailus wrote:
> >>> The V4L
On Monday 17 November 2014 16:04:07 Sakari Ailus wrote:
> Hi Pali,
>
> On Mon, Nov 17, 2014 at 04:01:31PM +0100, Pali Rohár wrote:
> > On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> > > * Pavel Machek [141117 02:17]:
> > > > On Mon 2014-11-17 11:09:45, Pali Rohár wrote:
> > > > > On M
* Pali Rohár [141117 07:03]:
> On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> >
> > There's nothing stopping us from initializing the camera code
> > from pdata-quirks.c for now to keep it working. Certainly the
> > binding should be added to the driver, but that removes a
> > depende
Hi Pali,
On Mon, Nov 17, 2014 at 04:01:31PM +0100, Pali Rohár wrote:
> On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> > * Pavel Machek [141117 02:17]:
> > > On Mon 2014-11-17 11:09:45, Pali Rohár wrote:
> > > > On Monday 17 November 2014 11:05:19 Pavel Machek wrote:
> > > > > Hi!
> >
On Monday 17 November 2014 15:55:46 Tony Lindgren wrote:
> * Pavel Machek [141117 02:17]:
> > On Mon 2014-11-17 11:09:45, Pali Rohár wrote:
> > > On Monday 17 November 2014 11:05:19 Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > On Mon 2014-11-17 09:43:19, Pali Rohár wrote:
> > > > > On Sunday 1
Hi Pavel,
On Sun, Nov 16, 2014 at 08:59:28AM +0100, Pavel Machek wrote:
> For device tree people: Yes, I know I'll have to create file in
> documentation, but does the binding below look acceptable?
>
> I'll clean up driver code a bit more, remove the printks. Anything
> else obviously wrong?
Ja
Em Sun, 9 Nov 2014 21:35:17 +
Sean Young escreveu:
> On Thu, Nov 06, 2014 at 08:56:47AM -0500, Andy Walls wrote:
> > On November 6, 2014 8:54:28 AM EST, Andy Walls
> > wrote:
> > >Sean,
> > >
> > >Ir-kbd-i2c was never intended for Tx.
> > >
> > >You can transmit *short* arbitrary pulse-spac
* Pavel Machek [141117 02:17]:
> On Mon 2014-11-17 11:09:45, Pali Rohár wrote:
> > On Monday 17 November 2014 11:05:19 Pavel Machek wrote:
> > > Hi!
> > >
> > > On Mon 2014-11-17 09:43:19, Pali Rohár wrote:
> > > > On Sunday 16 November 2014 08:59:28 Pavel Machek wrote:
> > > > > For device tree
While trying to debug a particularly recalcitrant segfault on entering
GStreamer, I found all this on dmesg. I don't know if it is connected,
but I haven't seen it before. I'm using a Dazzle DVC 100 Rev 1.1.
I get it across several different platforms (this is an Asus Zen
laptop). The opera
On 08/01/2014 05:02 PM, Jean-Marc VOLLE wrote:
> From: vollejm
>
> UHD video content may be encoded using a new color space (BT2020). This patch
> adds it to the v4l2_colorspace enum
FYI: I've just posted a patch series that enhances V4L2 colorspace support to
include BT.2020 (among others).
S
Hi Hans,
On Mon, Nov 17, 2014 at 09:57:24AM +0100, Hans Verkuil wrote:
> On 11/15/2014 06:44 PM, Sakari Ailus wrote:
> > Hi,
> >
> > On Sat, Nov 15, 2014 at 04:18:59PM +0200, Sakari Ailus wrote:
> > ...
> >>> union {
> >>> __s32 value;
> >>> __s64 value64;
> >>> @@ -1294,6 +
On 11/17/2014 03:16 PM, Hans Verkuil wrote:
> This patch series improves the V4L2 colorspace support. Specifically
> it adds support for AdobeRGB and BT.2020 (UHDTV) colorspaces and it allows
> configuring the Y'CbCr encoding and the quantization explicitly if
> non-standard methods are used.
>
>
From: Hans Verkuil
Add AdobeRGB and BT.2020 support.
The colorspace control now orders the colorspaces according to how often
they are used. So rarely used colorspaces are moved to the end. This makes
it more logical when testing colorspace support.
Signed-off-by: Hans Verkuil
---
drivers/med
From: Hans Verkuil
Implement controls to set the YCbCr encoding and the quantization
range for the colorspace.
Signed-off-by: Hans Verkuil
---
drivers/media/platform/vivid/vivid-core.h | 2 +
drivers/media/platform/vivid/vivid-ctrls.c | 86 +
drivers/media/p
From: Hans Verkuil
Add support for the new AdobeRGB and BT.2020 colorspaces. Also support
explicit Y'CbCr and quantization settings.
Signed-off-by: Hans Verkuil
---
drivers/media/platform/vivid/vivid-tpg.c | 327 +--
drivers/media/platform/vivid/vivid-tpg.h | 38 ++
From: Hans Verkuil
Log the new ycbcr_enc and quantization fields. Note that it now
also logs the flags field for the multiplanar buffer type. This was
forgotten when the flags field was added.
Signed-off-by: Hans Verkuil
---
drivers/media/v4l2-core/v4l2-ioctl.c | 11 +++
1 file changed
From: Hans Verkuil
Add and copy the new ycbcr_enc and quantization fields.
Signed-off-by: Hans Verkuil
---
include/media/v4l2-mediabus.h | 4
include/uapi/linux/v4l2-mediabus.h | 6 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/include/media/v4l2-mediabus.h b/i
From: Hans Verkuil
Add support for the new AdobeRGB and BT.2020 colorspaces as needed for
HDMI 2.0.
Add support to specify the Y'CbCr encoding and quantization range explicitly.
Signed-off-by: Hans Verkuil
---
include/uapi/linux/videodev2.h | 99 +-
1 f
From: Hans Verkuil
This extends the precalculated tpg_csc_colors matrix with AdobeRGB and BT.2020
colorspace support.
It also adds two precalculated tables that convert between linear RGB and
non-linear
Rec.709 R'G'B' values, i.e. the Rec. 709 transfer function. This is needed to
efficiently ha
From: Hans Verkuil
The colorspace chapter in the V4L2 Specification was always poorly
written. This patch rewrites it, documenting the new Y'CbCr encoding
and quantization defines and going into much more detail with respect
to how colorspaces are used and what it all means.
Signed-off-by: Hans
This patch series improves the V4L2 colorspace support. Specifically
it adds support for AdobeRGB and BT.2020 (UHDTV) colorspaces and it allows
configuring the Y'CbCr encoding and the quantization explicitly if
non-standard methods are used.
It's almost identical to the version shown during the mi
Add myself as the maintainer for the Imagination Technologies Infrared
Decoder driver.
Signed-off-by: James Hogan
Cc: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ea4d0058fd1b..814c
From: Dylan Rajaratnam
A problem was found on Polaris where if the unit it booted via the power
button on the infrared remote then the next button press on the remote
would return the key code used to power on the unit.
The sequence is:
- The polaris powered off but with the powerdown controlle
Don't bother setting .owner = THIS_MODULE, since it's already handled by
the platform_driver_register macro.
Signed-off-by: James Hogan
Cc: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
---
drivers/media/rc/img-ir/img-ir-core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/
The ImgTec Infrared decoder block which img-ir drives is only used in
IMGWorks SoCs so far, such as the TZ1090 (Meta based) and the upcoming
Pistachio (MIPS based). Therefore make the driver depend on METAG (for
TZ1090) or MIPS (for Pistachio) or COMPILE_TEST (so that it is included
in x86 allmodco
The img_ir_register_decoder() and img_ir_unregister_decoder() functions
were dropped prior to the img-ir driver being applied to simplify the
protocol decoder setup. However the declarations of these functions in
img-ir-hw.h were still included. Delete them since they're completely
unused.
Signed-
Here are a few fixes for the img-ir RC driver.
Patch 1 is the important one. I've tagged it for stable.
The other 4 are minor fixes/improvements that don't need backporting to
stable.
Dylan Rajaratnam (1):
img-ir/hw: Always read data to clear buffer
James Hogan (4):
img-ir/hw: Drop [un]regi
On 22 October 2014 15:12, Hans Verkuil wrote:
> How to submit patches for a stable kernel
> =
>
> The standard method is to add this tag:
>
> Cc: sta...@vger.kernel.org
>
> possibly with a comment saying to which versions it should be applied, like:
Hi Sakari,
On 09/22/2014 05:21 PM, Jacek Anaszewski wrote:
This patch adds helper functions for registering/unregistering
LED class flash devices as V4L2 subdevs. The functions should
be called from the LED subsystem device driver. In case the
support for V4L2 Flash sub-devices is disabled in th
Hi Sakari,
On Mon, Nov 17, 2014 at 10:53 AM, Sakari Ailus
wrote:
> Hi Prabhakar,
>
> Thank you for the patch.
>
> Lad, Prabhakar wrote:
>>
>> this patch removes the guard CONFIG_VIDEO_V4L2_SUBDEV_API
>> for v4l2_subdev_get_try_*() functions.
>> In cases where a subdev using v4l2_subdev_get_try_*(
Hi Prabhakar,
Thank you for the patch.
Lad, Prabhakar wrote:
this patch removes the guard CONFIG_VIDEO_V4L2_SUBDEV_API
for v4l2_subdev_get_try_*() functions.
In cases where a subdev using v4l2_subdev_get_try_*() calls
internally and the bridge using subdev pad ops which is
not MC aware forces t
this patch removes the guard CONFIG_VIDEO_V4L2_SUBDEV_API
for v4l2_subdev_get_try_*() functions.
In cases where a subdev using v4l2_subdev_get_try_*() calls
internally and the bridge using subdev pad ops which is
not MC aware forces to select MEDIA_CONTROLLER, as
VIDEO_V4L2_SUBDEV_API is dependent
On Mon 2014-11-17 11:09:45, Pali Rohár wrote:
> On Monday 17 November 2014 11:05:19 Pavel Machek wrote:
> > Hi!
> >
> > On Mon 2014-11-17 09:43:19, Pali Rohár wrote:
> > > On Sunday 16 November 2014 08:59:28 Pavel Machek wrote:
> > > > For device tree people: Yes, I know I'll have to create
> > >
Em Mon, 17 Nov 2014 12:51:46 +0300
Барт Гопник escreveu:
> (Where) can I find the the full list of the (key) differences between
> SAA7113 and GM7113?
I've no idea. Perhaps you would need to get both datasheets and compare
them.
> If it is not hard to do it, can anybody please implement it?
Th
On Monday 17 November 2014 11:05:19 Pavel Machek wrote:
> Hi!
>
> On Mon 2014-11-17 09:43:19, Pali Rohár wrote:
> > On Sunday 16 November 2014 08:59:28 Pavel Machek wrote:
> > > For device tree people: Yes, I know I'll have to create
> > > file in documentation, but does the binding below look
> >
Hi!
On Mon 2014-11-17 09:43:19, Pali Rohár wrote:
> On Sunday 16 November 2014 08:59:28 Pavel Machek wrote:
> > For device tree people: Yes, I know I'll have to create file
> > in documentation, but does the binding below look acceptable?
> >
> > I'll clean up driver code a bit more, remove the p
(Where) can I find the the full list of the (key) differences between
SAA7113 and GM7113?
If it is not hard to do it, can anybody please implement it?
Unfortunately, I'm not very good with system drivers programming.
I'm interesting only in sharpness control because the image quality
(sharpness)
On 11/17/2014 10:31 AM, Sakari Ailus wrote:
> Hi Hans,
>
> On Mon, Nov 17, 2014 at 10:02:03AM +0100, Hans Verkuil wrote:
>> On 11/15/2014 10:10 PM, Sakari Ailus wrote:
@@ -197,6 +207,8 @@ struct v4l2_ctrl {
u32 nr_of_dims;
u16 nr_of_stores;
u16 store;
+ DECLARE_B
Hi Hans,
On Mon, Nov 17, 2014 at 10:02:03AM +0100, Hans Verkuil wrote:
> On 11/15/2014 10:10 PM, Sakari Ailus wrote:
> > Hi Hans,
> >
> > A few comments below.
> >
> > On Sun, Sep 21, 2014 at 04:48:25PM +0200, Hans Verkuil wrote:
> >> From: Hans Verkuil
> >>
> >> Sometimes you want to apply a v
On 11/16/2014 05:40 PM, Sakari Ailus wrote:
> Hi Hans,
>
> Thank you for the review.
>
> On Fri, Nov 14, 2014 at 09:46:54AM +0100, Hans Verkuil wrote:
>> On 11/09/2014 12:04 AM, Sakari Ailus wrote:
>>> The V4L2_SEL_TGT_NATIVE_SIZE target is used to denote e.g. the size of a
>>> sensor's pixel arr
Hi Pawel,
On 11/16/2014 02:13 PM, Pawel Osciak wrote:
> On Mon, Nov 10, 2014 at 8:49 PM, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Require that dma-sg also uses an allocation context. This is in preparation
>> for adding prepare/finish memops to sync the memory between DMA and CPU.
>>
>> S
On 11/15/2014 10:10 PM, Sakari Ailus wrote:
> Hi Hans,
>
> A few comments below.
>
> On Sun, Sep 21, 2014 at 04:48:25PM +0200, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Sometimes you want to apply a value every time v4l2_ctrl_apply_store
>> is called, and sometimes you want to apply that v
On 11/15/2014 06:44 PM, Sakari Ailus wrote:
> Hi,
>
> On Sat, Nov 15, 2014 at 04:18:59PM +0200, Sakari Ailus wrote:
> ...
>>> union {
>>> __s32 value;
>>> __s64 value64;
>>> @@ -1294,6 +1294,10 @@ struct v4l2_ext_control {
>>> };
>>> } __attribute__ ((packed));
>>>
On 11/15/2014 03:18 PM, Sakari Ailus wrote:
> Hi Hans,
>
> On Sun, Sep 21, 2014 at 04:48:24PM +0200, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Replace reserved2 by a flags field. This is used to tell whether
>> setting a new store value is applied only once or every time that
>> v4l2_ctrl_a
On 11/14/2014 04:44 PM, Sakari Ailus wrote:
> Hi Hans,
>
> Some comments below.
>
> On Sun, Sep 21, 2014 at 04:48:22PM +0200, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Signed-off-by: Hans Verkuil
>> ---
>> drivers/media/v4l2-core/v4l2-ctrls.c | 150
>> +--
On Sunday 16 November 2014 08:59:28 Pavel Machek wrote:
> For device tree people: Yes, I know I'll have to create file
> in documentation, but does the binding below look acceptable?
>
> I'll clean up driver code a bit more, remove the printks.
> Anything else obviously wrong?
>
> Signed-off-by:
On 11/14/2014 04:35 PM, Sakari Ailus wrote:
> Hi Hans,
>
> One more comment...
>
> On Sun, Sep 21, 2014 at 04:48:21PM +0200, Hans Verkuil wrote:
>> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
>> index 83ef28a..2ca44ed 100644
>> --- a/include/uapi/linux/videodev2.h
On 11/14/2014 03:42 PM, Sakari Ailus wrote:
> Hi Hans,
>
> On Sun, Sep 21, 2014 at 04:48:21PM +0200, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> When queuing buffers allow for passing the configuration store ID that
>> should be associated with this buffer. Use the 'reserved2' field for this.
92 matches
Mail list logo
