This patch removes the field description of fields that no
longer exists, along side aligns the field description of
fields.
Signed-off-by: Lad, Prabhakar
---
include/media/tvp514x.h |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/include/media/tvp514x.h b/include/
No functional changes here. Just re-organizes the functions
inside the file.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 217 +
1 file changed, 115 insertions(+), 102 deletions(-)
diff --git a/drivers/media/dvb-frontends/mb86
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drivers/media/dvb-frontends/mb86a20s.c
index 06e5d35..e069c9b 100644
--- a/drivers/media/dvb-frontends/mb
Also add some additional debug and error messages when needed.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 156 +++--
1 file changed, 111 insertions(+), 45 deletions(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drive
The read/write errors are not handled well on get_frontend. Fix it,
by letting the frontend cached values to represent the DVB properties
that were successfully retrieved.
While here, use "c" for dtv_frontend_properties cache, instead of
"p", as this is more common.
Signed-off-by: Mauro Carvalho
The DVBv3 quality parameters are limited on several ways:
- Doesn't provide any way to indicate the used measure,
so userspace need to guess how to calculate the measure;
- Only a limited set of stats are supported;
- Can't be called in a way to require them to
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drivers/media/dvb-frontends/mb86a20s.c
index e73f66d..c4bf428 100644
--- a/drivers/media/dvb-frontends/mb
Get the proper bits from the TMCC table registers.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drivers/media/dvb-frontends/mb86a20s.c
index e0
As global BER stat is already summing both BER counters, it should
not be incremented with its previous value.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/dvb-frontends/mb86a
Add the logic to poll, reset counters and report the QoS stats
to the end user.
The idea is that the core will periodically poll the frontend for
the stats. The frontend may return -EBUSY, if the previous collect
didn't finish, or it may fill the cached data.
The value returned to the end user is
Reduce the bit count from 2^24-1 to 2^16-1 to speedup
BER measurement;
Do a per-layer reset, instead of waiting for data on all
layers;
Global stats now start to appear as soon as the first layer
(e. g. the one with the biggest number of segments) start to
have collected data.
Signed-off-by: Mau
Due to statistics, we should update the DVB API version.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/DocBook/media/dvb/dvbapi.xml | 2 +-
include/uapi/linux/dvb/version.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/DocBook/media/dvb/d
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drivers/media/dvb-frontends/mb86a20s.c
index c4bf428..21e7e68 100644
--- a/drivers/media/dvb-frontends/mb
If an error happens, restore tuner I2C gate to the right
value.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/mb86a20s.c
b/drivers/media/dvb-frontends/mb86a20s.
Do a better job on setting the bit error counters, in order to
have all layer measures to happen in a little less than one
second.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/mb86a20s.c | 204 +
1 file changed, 179 insertions(+), 25 deleti
Instead of providing separate callbacks to read the several FE
status properties, the better seems to use just one method that will:
- Read lock status;
- Read signal strength;
- if locked, get TMCC data;
- if locked, get DVB status.
As the DVB frontend thread will call this metho
Add DVBv5 methods to retrieve QoS statistics.
Those methods allow per-layer and global statistics.
Implemented 2 QoS statistics on mb86a20s, one global only
(signal strengh), and one per layer (BER).
Tested with a modified version of dvbv5-zap, that allows monitoring
those stats. Test data follo
Quoting Laurent Pinchart (2013-01-08 05:43:52)
> Hello,
>
> Now that the OMAP3 supports the common clock framework, clock rate
> back-propagation is available for the ISP clocks. Instead of setting the
> cam_mclk parent clock rate to control the cam_mclk clock rate, we can mark the
> dpll4_m5x2_ck
On 01/14/2013 10:45 AM, Hans Verkuil wrote:
On Mon January 14 2013 00:14:39 Sylwester Nawrocki wrote:
...
I've checked the datasheets and the gain ceiling control is supported by
virtually every Omnivision sensor: OV2655, OV3640, OV5630, OV9650, OV9655,
OV7690, with even identical range 2x...12
usb 1-2.2: DVB: registering adapter 1 frontend 0 (Realtek RTL2832 (DVB-T))...
i2c i2c-4: fc2580: FCI FC2580 successfully identified
usb 1-2.2: dvb_usb_v2: 'Digivox Micro Hd' successfully initialized and connected
On Mon, Jan 14, 2013 at 11:21 PM, Eddi De Pieri wrote:
> Add support for Digivox Min
If the remote video sensor reports an interlaced video mode, the CCDC block
should configure itself appropriately.
This patch reintroduces code with was removed in commit
cf7a3d91ade6c56bfd860b377f84bd58132f7a81, but in a way that is compatible
with the new media pipeline work.
This patch also cl
Add support for Digivox Mini HD (rtl2832)
The tuner works, but with worst performance then realtek linux driver,
due to incomplete implementation of fc2580.c
Signed-off-by: Eddi De Pieri
Tested-by: Lorenzo Dongarrà
diff --git a/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
b/drivers/media/usb/dvb-us
On 01/09/2013 02:35 PM, Laurent Pinchart wrote:
On Tuesday 08 January 2013 14:49:41 William Swanson wrote:
I believe the data is combined in a single buffer, with alternate fields
interleaved.
Could you please double-check that ? I'd like to be sure, not just believe :-)
Sorry for the delay
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:Mon Jan 14 19:00:15 CET 2013
git hash:3151d14aa6e983aa36d51a80d0477859f9ba12af
gcc version: i686-linux-gcc (GCC
On Saturday 12 January 2013 21:24:50 Ondrej Zary wrote:
> Partially working: FM radio
> Radio seems to be a long-standing problem with saa7134 cards using silicon
> tuners (according to various mailing lists).
>
> On this card, GPIO11 controls 74HC4052 MUX. It switches two things:
> something at TD
This kind of memcpy() is error-prone. Its replacement with a struct
assignment is prefered because it's type-safe and much easier to read.
Cc: Laurent Pinchart
Signed-off-by: Peter Senna Tschudin
Signed-off-by: Ezequiel Garcia
---
Changes from v1:
* Replaced a memcpy() in ucv_ctrl_add_info(),
On Mon, Jan 14, 2013 at 1:01 PM, nise.design wrote:
> After google search I think the problem may be come from connection between
> DMB-TH drivers and dvb_frontend.c broken. I wanted to know any example code
> or instruction about DVBv3 driver connect to dvb_frontend.c. Thank you for
> any advice
Hello,
I'm a Ubuntu and DMB-TH digital TV USB dongle user. The USB
dongle working flawlessly in Ubuntu 10.XX, but it failed after migrate
to latest Ubuntu 12.10. Then I using google to find out the problem and
suspect the problem come from DVBv3 migrate to DVBv5. Because of
creator
Improved patch follows:
--HPS
>From a88d72d2108f92f004a3f050a708d9b7f661f924 Mon Sep 17 00:00:00 2001
From: Hans Petter Selasky
Date: Mon, 14 Jan 2013 13:53:21 +0100
Subject: [PATCH] Correctly initialize data for USB request.
Found-by: Jan Beich
Signed-off-by: Hans Petter Selasky
---
drivers/
>From 89326793e2429dc55d951f336b3e3e3b73bedb95 Mon Sep 17 00:00:00 2001
From: Hans Petter Selasky
Date: Mon, 14 Jan 2013 13:53:21 +0100
Subject: [PATCH] Correctly set data for USB request in case of a previous
failure.
Found-by: Jan Beich
Signed-off-by: Hans Petter Selasky
---
drivers/input/ta
Hello Sean,
Thanks for reviewing the patch.
On Sat, Jan 12, 2013 at 1:30 AM, Sean Paul wrote:
> On Fri, Jan 11, 2013 at 5:35 AM, Leela Krishna Amudala
> wrote:
>> The Exynos DP transmitter is treated as an end entity in the display pipeline
>> and made this RFC patch compliant with CDF.
>>
>> An
Hi Mauro,
Here are a bunch of validation fixes and control documentation improvements.
Patchwork commands:
pwclient -u 'accepted' 16216
pwclient -u 'accepted' 16217
pwclient -u 'accepted' 16218
Regards,
Hans
The following changes since commit 73ec66c000e9816806c7380ca3420f4e0638c40e:
On Mon January 14 2013 11:09:41 Sachin Kamat wrote:
> Fixes the following warning:
> drivers/media/platform/s5p-mfc/s5p_mfc_opr.c:56:27: warning:
> Using plain integer as NULL pointer
>
> Signed-off-by: Sachin Kamat
Acked-by: Hans Verkuil
> ---
> drivers/media/platform/s5p-mfc/s5p_mfc_opr.c |
Fixes the following warning:
drivers/media/platform/s5p-mfc/s5p_mfc_opr.c:56:27: warning:
Using plain integer as NULL pointer
Signed-off-by: Sachin Kamat
---
drivers/media/platform/s5p-mfc/s5p_mfc_opr.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/platf
On cold boot the device does not initialize until the first packet is
received, and that packet is not processed.
Signed-off-by: Sean Young
---
drivers/media/rc/iguanair.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/media/rc/iguanair.c
On Mon January 14 2013 00:14:39 Sylwester Nawrocki wrote:
> Hi Hans,
>
> Thank you for the review!
>
> On 01/07/2013 02:38 PM, Hans Verkuil wrote:
> >> +
> >> +/* V4L2 private controls */
> >> +
> >> +/* Auto exposure frame reference area */
> >> +#define V4L2_CID_EXPOSURE_REFERENCE_AREA (V4L2_CT
Not all drivers use monotonic timestamps. This patch adds a way to set the
timestamp type per every queue.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
drivers/media/v4l2-core/videobuf2-core.c |5 +++--
include/media/videobuf2-core.h |1 +
2 files changed, 4 in
Define video buffer flag for the COPY timestamp. In this case the timestamp
value is copied from the OUTPUT to the corresponding CAPTURE buffer.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
Documentation/DocBook/media/v4l/io.xml |6 ++
include/uapi/linux/videodev2.h
Set proper timestamp type in drivers that I am sure that use either
MONOTONIC or COPY timestamps. Other drivers will correctly report
UNKNOWN timestamp type instead of assuming that all drivers use monotonic
timestamps.
Signed-off-by: Kamil Debski
Signed-off-by: Kyungmin Park
---
drivers/media/
Hi,
The recent addition of timestamp types (and monotonic timestamp) left some room
for improvement. First of all not all drivers use monotonic timestamp. There are
for example mem2mem drivers that copy the timestamp from the OUTPUT buffer to
the corresponding CAPTURE buffer. Some videobuf2 driver
On Sun January 13 2013 13:50:50 Frank Schäfer wrote:
> Signed-off-by: Frank Schäfer
> ---
> drivers/media/usb/em28xx/em28xx-video.c |8
> 1 Datei geändert, 8 Zeilen hinzugefügt(+)
>
> diff --git a/drivers/media/usb/em28xx/em28xx-video.c
> b/drivers/media/usb/em28xx/em28xx-video.c
>
41 matches
Mail list logo