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: Thu Dec 31 04:00:20 CET 2015
git branch: test
git hash: 768acf46e1320d6c41ed1b7c4952bab41c1cde79
gcc versio
Hi all,
I try to get a Terratec S7 (which seems to be a Elgato EyeTV Sat)
working a my new VDR setup based on yaVDR 0.6. Unfortunately, compared
to the also installed DD cineS2 tuners, the Terratec S7 tuner does not
seem to work with DVB-S2 channels while the DVB-S channels work.
There has b
On Wed, Dec 16, 2015 at 9:37 AM, Marek Szyprowski
wrote:
> This patch allows device drivers to initialize more than one reserved
> memory region assigned to given device. When driver needs to use more
> than one reserved memory region, it should allocate child devices and
> initialize regions by i
At least on Zotac CI321 ACPI provides an ioport range for the wake up part
but accessing these ioports has no effect.
Instead the ioport base address is set to another value already
(0xa20 in my case) and accessing this ioport range works.
Therefore set a new ioport base address only if the curren
Most likely a copy & paste error.
The wakeup interrupt supports less triggering events.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.h | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.h b/drivers/media/rc/nuvoton-cir.h
index
Add locking to nvt_enable_wake calls.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index 252804d..c3294fb 100644
--- a/driv
Extend the locking to protect more critical actions like register accesses
in the interrupt handlers.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/
Only handle an interrupt if at least one combination of event bit
and related interrupt bit is set.
Previously it was just checked that at least one event bit and
at least one interrupt bit are set.
This fixes issues like the following which was caused by
interrupt sharing:
An interrupt intended f
Selecting the logical device in the interrupt handler is not needed
as no configuration register is accessed.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
i
Calling nvt_set_cir_iren separately is not needed as this is done
by nvt_cir_regs_init.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index e01fdc8..252804d 1
Only enable the logical devices after the registers have been initialized.
The call to nvt_enable_logical_dev in nvt_resume is not needed as this is
done implicitely by nvt_cir_regs_init now.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 21 -
1 file ch
Check for the case that no Nuvoton chip is found on either EFM port.
Also move the position of nvt_efm_disable to reduce the time the
EFM ports are locked.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 17 +
drivers/media/rc/nuvoton-cir.h | 3 ++-
2 files c
Factor out disabling of a logical device.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index f661eff..ceb6b95 100644
Use nvt_cr_write to simplify nvt_select_logical_ dev.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index 62c82c5..2539d4f 100644
--- a/driver
At least on NVT6779D clearing the wake fifo works in learning mode only
(although this condition is not mentioned in the chip spec).
Setting the clear fifo bit has no effect in wake up mode.
Even if clearing the wake fifo should work in wake up mode on other
chips this workaround doesn't hurt.
If n
Simplify nvt_cir_tx_inactive.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index 2539d4f..f661eff 100644
--- a/drivers/media/rc/nuvoton-cir
Factor out enabling of a logical device.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index ceb6b95..8ed8011 100644
--
Switch to using the recently introduced IR default timeout value
(IR_DEFAULT_TIMEOUT) and consider the value of SAMPLE_PERIOD
when calculating the limit count register value.
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-cir.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(
Heiner Kallweit (16):
media: rc: nuvoton-cir: use request_muxed_region for accessing EFM registers
media: rc: nuvoton-cir: simplify nvt_select_logical_ dev
media: rc: nuvoton-cir: simplify nvt_cir_tx_inactive
media: rc: nuvoton-cir: factor out logical device disabling
media: rc: nuvoton-
The two EFM ioports are accessed by drivers for other parts of the Nuvoton
Super-IO chips too. Therefore access to these ioports needs to be
protected by using request_muxed_region (like it's implemented e.g. in
hwmon/nct6775 already).
Signed-off-by: Heiner Kallweit
---
drivers/media/rc/nuvoton-
To whom it may concern...
Added this device to em28xx-cards.c and used
"EM2860_BOARD_HT_VIDBOX_NW03" as ID
because it's the only device listed there that has the same chips as my
hardware.
Recompiled the module and it works!
--- /usr/src/linux/drivers/media/usb/em28xx/em28xx-cards.c 2015-11-2
Devices like mxl111sf-based WinTV Aero-m have multiple
frontends, all linked on the same demod. Currently, the
dvb_create_graph() function is not smart enough to create
multiple links. Fix it.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-core/dvbdev.c | 57 +
Several pure digital TV devices have a frontend with the tuner
integrated on it. Add the RF connector when dvb_create_media_graph()
is called on such devices.
Tested with siano and dvb_usb_mxl111sf drivers.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb-main.c|
Sometimes, it is desired to create 1:n and n:1 or even
n:n links between different entities with the same
function.
This is actually needed to support DVB devices that
have multiple frontends. While we could do a function
like that internally at the DVB core, such function is
generic enough to be
While mxl111sf may have multiple frontends, it has just one
tuner. Reflect that on the media graph.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-core/dvbdev.h | 6 ++
drivers/media/usb/dvb-usb-v2/mxl111sf.c | 20
drivers/media/usb/dvb-usb-v2/mxl111
This patch series is the result of some additional tests with the media
controller and
several different pure digital TV devices, using the dvb-usb, dvb-usb-v2 core
and
the siano driver.
It addresses some minor issues, and improves the graph representation of
those devices. In particular, the
We should not remove the media_device until its last usage,
or we may have use after free troubles.
So, move the per-adapter media_device removal to happen at
the end of the adapter removal code.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c | 2 +-
1 file
Those functions are used only if CONFIG_MEDIA_CONTROLLER_DVB.
Without that, if !CONFIG_MEDIA_CONTROLLER_DVB, it would produce
two warnings:
drivers/media/dvb-core/dvbdev.c:219:12: warning: 'dvb_create_tsout_entity'
defined but not used [-Wunused-function]
static int dvb_create_tsout_entity(struc
The build of m32r allmodconfig fails with the error:
drivers/media/v4l2-core/videobuf2-dma-contig.c:484:2:
error: implicit declaration of function 'dma_get_cache_alignment'
The build of videobuf2-dma-contig.c depends on HAS_DMA and it is
correctly mentioned in the Kconfig but the symbol VI
DEFINE_IR_RAW_EVENT can be simplified and doesn't provide much benefit
as all elements are initialized to 0. But keep it as it is used in a
lot of places.
duration is the first element of the embedded union and therefore
used for the initialization even if not explicitely mentioned.
Signed-off-by:
30 matches
Mail list logo
