Hello
On 11/09/2016 05:44 PM, Ramesh Shanmugasundaram wrote:
+static int max2175_set_lo_freq(struct max2175 *ctx, u64 lo_freq)
+{
+ u64 scaled_lo_freq, scaled_npf, scaled_integer, scaled_fraction;
+ u32 frac_desired, int_desired, lo_mult = 1;
+ const u32 scale_factor = 100
On Mon, Nov 7, 2016 at 11:04 PM, Stanimir Varbanov
wrote:
> Makefile and Kconfig files to build the Venus video codec driver.
>
> Signed-off-by: Stanimir Varbanov
> ---
> drivers/media/platform/qcom/Kconfig| 7 +++
> drivers/media/platform/qcom/Makefile | 1 +
> drivers/media
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: Fri Nov 11 05:00:18 CET 2016
media-tree git hash:bd676c0c04ec94bd830b9192e2c33f2c4532278d
media_build git
Hello
On 11/10/2016 10:08 AM, Laurent Pinchart wrote:
Antti, Hans, ping ? Please see below.
On Friday 04 Nov 2016 09:23:29 Ramesh Shanmugasundaram wrote:
On 11/02/2016 10:58 PM, Laurent Pinchart wrote:
On Wednesday 02 Nov 2016 09:00:00 Ramesh Shanmugasundaram wrote:
On Wednesday 12 Oct 2016
Hi Sean,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on next-20161110]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Sean-Young/serial_ir-port-lirc_serial-to-rc-core
Hi Philipp,
Thank you for the patch.
On Monday 07 Nov 2016 21:15:47 Philipp Zabel wrote:
> The Rift CV1 Sensor has bInterfaceClass set to vendor specific, so we
> need an entry in uvc_ids to probe it. Just as the Rift DK2 IR tracker,
> it misreports the pixel format as YUYV instead of Y8.
>
> Th
On 11/10/2016 05:19 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Thursday 10 Nov 2016 17:16:31 Shuah Khan wrote:
>> On 11/10/2016 05:11 PM, Laurent Pinchart wrote:
>>> On Thursday 10 Nov 2016 17:00:16 Shuah Khan wrote:
On 11/10/2016 04:53 PM, Laurent Pinchart wrote:
> On Tuesday 08 Nov
Hi Shuah,
On Thursday 10 Nov 2016 17:16:31 Shuah Khan wrote:
> On 11/10/2016 05:11 PM, Laurent Pinchart wrote:
> > On Thursday 10 Nov 2016 17:00:16 Shuah Khan wrote:
> >> On 11/10/2016 04:53 PM, Laurent Pinchart wrote:
> >>> On Tuesday 08 Nov 2016 12:20:29 Shuah Khan wrote:
> On Tue, Nov 8, 2
On 11/10/2016 05:11 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Thursday 10 Nov 2016 17:00:16 Shuah Khan wrote:
>> On 11/10/2016 04:53 PM, Laurent Pinchart wrote:
>>> On Tuesday 08 Nov 2016 12:20:29 Shuah Khan wrote:
On Tue, Nov 8, 2016 at 6:55 AM, Sakari Ailus wrote:
> From: Sakari Ai
Hi Shuah,
On Thursday 10 Nov 2016 17:00:16 Shuah Khan wrote:
> On 11/10/2016 04:53 PM, Laurent Pinchart wrote:
> > On Tuesday 08 Nov 2016 12:20:29 Shuah Khan wrote:
> >> On Tue, Nov 8, 2016 at 6:55 AM, Sakari Ailus wrote:
> >>> From: Sakari Ailus
> >>>
> >>> Allow allocating the media device dyn
On 11/10/2016 04:53 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Tuesday 08 Nov 2016 12:20:29 Shuah Khan wrote:
>> On Tue, Nov 8, 2016 at 6:55 AM, Sakari Ailus wrote:
>>> From: Sakari Ailus
>>>
>>> Allow allocating the media device dynamically. As the struct media_device
>>> embeds struct media
Hi Shuah,
On Tuesday 08 Nov 2016 12:20:29 Shuah Khan wrote:
> On Tue, Nov 8, 2016 at 6:55 AM, Sakari Ailus wrote:
> > From: Sakari Ailus
> >
> > Allow allocating the media device dynamically. As the struct media_device
> > embeds struct media_devnode, the lifetime of that object is that same tha
Hi Mauro,
On Tuesday 08 Nov 2016 15:00:27 Mauro Carvalho Chehab wrote:
> Em Tue, 8 Nov 2016 15:55:10 +0200 Sakari Ailus escreveu:
> > This reverts commit 6f0dd24a084a ("[media] media: fix media devnode
> > ioctl/syscall and unregister race"). The commit was part of an original
> > patchset to avo
The function hva_hw_probe in the file
drivers/media/platform/sti/hva/hva-hw.c contains the following code:
/* get memory for esram */
esram = platform_get_resource(pdev, IORESOURCE_MEM, 1);
if (IS_ERR_OR_NULL(esram)) {
dev_err(dev, "%s failed to get esra
On 11/07, Stanimir Varbanov wrote:
> diff --git a/drivers/media/platform/qcom/venus/core.c
> b/drivers/media/platform/qcom/venus/core.c
> new file mode 100644
> index ..7b14b1f12e20
> --- /dev/null
> +++ b/drivers/media/platform/qcom/venus/core.c
> @@ -0,0 +1,557 @@
> +/*
> + * Copyrig
Tested with a homebrew serial ir.
Signed-off-by: Sean Young
---
MAINTAINERS |6 +
drivers/media/rc/Kconfig | 17 +
drivers/media/rc/Makefile|1 +
drivers/media/rc/serial_ir.c | 1025 +++
dr
This makes transmission more reliable and the code much cleaner.
Signed-off-by: Sean Young
---
drivers/media/rc/serial_ir.c | 260 +--
1 file changed, 54 insertions(+), 206 deletions(-)
diff --git a/drivers/media/rc/serial_ir.c b/drivers/media/rc/serial_i
Previously the warnings were added back at the W=1 level and above,
this now turns them on again by default, assuming that we have addressed
all warnings and again have a clean build for v4.10.
I found a number of new warnings in linux-next already and submitted
bugfixes for those. Hopefully they
Some configurations produce this harmless warning when built with
gcc -Wmaybe-uninitialized:
infiniband/core/cma.c: In function 'cma_get_net_dev':
infiniband/core/cma.c:1242:12: warning: 'src_addr_storage.sin_addr.s_addr' may
be used uninitialized in this function [-Wmaybe-uninitialized]
I previ
A bugfix introduced a harmless gcc warning in nfs4_slot_seqid_in_use
if we enable -Wmaybe-uninitialized again:
fs/nfs/nfs4session.c:203:54: error: 'cur_seq' may be used uninitialized in this
function [-Werror=maybe-uninitialized]
gcc is not smart enough to conclude that the IS_ERR/PTR_ERR pair
r
A recent rework accidentally left a debugging printk untouched
while changing the meaning of the variables, leading to an
uninitialized variable being printed:
drivers/media/i2c/ir-kbd-i2c.c: In function 'get_key_haup_common':
drivers/media/i2c/ir-kbd-i2c.c:62:2: error: 'toggle' may be used uninit
When called more than twice, the nios2_time_init() function
return an uninitialized value, as detected by gcc -Wmaybe-uninitialized
arch/nios2/kernel/time.c: warning: 'ret' may be used uninitialized in this
function
This makes it return '0' here, matching the comment above the
function.
Acked-b
Hi Linus,
It took a while for some patches to make it into mainline through
maintainer trees, but the 28-patch series is now reduced to 10, with
one tiny patch added at the end. I hope this can still make it into
v4.9. Aside from patches that are no longer required, I did these changes
compared t
The rfc4106 encrypy/decrypt helper functions cause an annoying
false-positive warning in allmodconfig if we turn on
-Wmaybe-uninitialized warnings again:
arch/x86/crypto/aesni-intel_glue.c: In function ‘helper_rfc4106_decrypt’:
include/linux/scatterlist.h:67:31: warning: ‘dst_sg_walk.sg’ may be us
The newly introduced soc_pcmcia_regulator_set() function sometimes returns
without setting its return code, as shown by this warning:
drivers/pcmcia/soc_common.c: In function 'soc_pcmcia_regulator_set':
drivers/pcmcia/soc_common.c:112:5: error: 'ret' may be used uninitialized in
this function [-W
gcc correctly warns about an incorrect use of the 'pa' variable
in case we pass an empty scatterlist to __s390_dma_map_sg:
arch/s390/pci/pci_dma.c: In function '__s390_dma_map_sg':
arch/s390/pci/pci_dma.c:309:13: warning: 'pa' may be used uninitialized in this
function [-Wmaybe-uninitialized]
Th
apm_bios_call() can fail, and return a status in its argument
structure. If that status however is zero during a call from
apm_get_power_status(), we end up using data that may have
never been set, as reported by "gcc -Wmaybe-uninitialized":
arch/x86/kernel/apm_32.c: In function ‘apm’:
arch/x86/ke
From: Sean Young
When receiving a nec repeat, ensure the correct scancode is repeated
rather than a random value from the stack. This removes the need
for the bogus uninitialized_var() and also fixes the warnings:
drivers/media/usb/dvb-usb/dib0700_core.c: In function
‘dib0700_rc_urb_complet
Traditionally, we have always had warnings about uninitialized variables
enabled, as this is part of -Wall, and generally a good idea [1], but it
also always produced false positives, mainly because this is a variation
of the halting problem and provably impossible to get right in all cases
[2].
V
> commit 0c979a12309af49894bb1dc60e747c3cd53fa888
> Author: Mauro Carvalho Chehab
> Date: Wed Nov 9 15:33:17 2016 -0200
>
> [media] gp8psk: Fix DVB frontend attach
>
> it should be calling module_get() at attach, as otherwise
> module_put() will crash.
>
> Signed-off-by: Mauro Ca
On Thu, Nov 03, 2016 at 03:39:31AM +0800, kbuild test robot wrote:
> Hi Sean,
>
> [auto build test WARNING on linuxtv-media/master]
> [also build test WARNING on v4.9-rc3 next-20161028]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
> [Sugge
On Thu, Nov 10, 2016 at 08:45:24AM +0100, Hans Verkuil wrote:
> Fix compiler warning about uninitialized variable reference:
>
> ir-kbd-i2c.c: In function 'get_key_haup_common.isra.3':
> ir-kbd-i2c.c:62:2: warning: 'toggle' may be used uninitialized in this
> function [-Wmaybe-uninitialized]
>
Hallo, Sie benötigen einen Instant-Darlehen zu Satz von 2%?
Wir bieten alle Arten von Krediten @ 2% jährlich.
Zur Bewerbung Neue Nachricht verfassen:
E-Mail: newdawnfinan...@financier.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord
On Wed, Nov 09, 2016 at 02:45:21PM +0100, Hans Verkuil wrote:
> On 11/09/16 14:28, Dan Carpenter wrote:
> >Hello Tiffany Lin,
> >
> >The patch 590577a4e525: "[media] vcodec: mediatek: Add Mediatek V4L2
> >Video Decoder Driver" from Sep 2, 2016, leads to the following static
> >checker warning:
> >
Hi,
this is purely a request for comments after a discussion had with
Rob and Jacek [*] about where to place the ir leds binding. Rob wants
the binding to be under led, while Jacek wants it in media...
"Ubi maior minor cessat": it goes to LED and they can be organized
in a subdirectory.
Standing
2016-11-10 9:40 GMT+01:00 Mauro Carvalho Chehab :
> Em Wed, 9 Nov 2016 11:07:35 -0800
> Linus Torvalds escreveu:
>
>> On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
>> >
>> > Tried patch with no success. Again a NULL ptr dereferece.
>>
>> That patch was pure garbage, I think. Pretty much all th
On Thu, Nov 10, 2016 at 08:49:43AM +0100, Hans Verkuil wrote:
> The daily build produces this compiler warning:
>
> dib0700_core.c: In function 'dib0700_rc_urb_completion':
> dib0700_core.c:787:2: warning: 'protocol' may be used uninitialized in this
> function [-Wmaybe-uninitialized]
> rc_keyd
On Thu, 10 Nov 2016, Markus Heiser wrote:
> Could this POC persuade you, if so, I send a more elaborate RFC,
> what do you think about?
Sorry, I do not wish to be part of this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubs
From: Ingi Kim
When video file was decoded by H/W MFCv8. It occured IOMMU page fault
because of accessing abnormal memory of mfc ctx buf
So this patch supports buffer size of mfc context more.
Relevant page fault error is below.
[ 3524.617147] PAGE FAULT occurred at 0x10108000 by 1120.sysmm
From: Andrzej Hajda
Driver complains about too small scratch buffer size. After adjusting
it according to vendor code, decoding works.
Signed-off-by: Andrzej Hajda
[mszyprow: moved the change to the header file]
Signed-off-by: Marek Szyprowski
---
drivers/media/platform/s5p-mfc/regs-mfc-v6.h
From: Donghwa Lee
Currently, when incomplete frame is recieved in the middle of
decoding, driver have treated it to error, so src/dst queue and
clock are cleaned. Although it is obviously error case, it is need
to maintain video decoding in case of necessity. This patch
supports skip incomplete f
Hi!
This is a collection of various fixes for Exynos MFC codec driver.
They all come from the internal kernel tree used for Tizen 3.0
development (available on git.tizen.org).
Patches were tested on Odroid U3 and XU3 boards (Exynos 4412 and 5422).
Best regards
Marek Szyprowski
Samsung R&D Instit
Newer MFC hardware have internal clock gating feature, so additional
software-triggered clock gating sometimes causes misbehavior of the MFC
firmware and results in freeze or crash. This patch changes the driver
to use software-triggered clock gating only when working with v5 MFC
hardware, where it
Hi Jacek,
> > > > > Only DT bindings of LED class drivers should be placed in
> > > > > Documentation/devicetree/bindings/leds. Please move it to the
> > > > > media bindings.
> > > >
> > > > that's where I placed it first, but Rob asked me to put it in the
> > > > LED directory and Cc the LED ma
From: "Shailendra Verma"
There is no need to call kfree() if memdup_user() fails, as no memory
was allocated and the error in the error-valued pointer should be returned.
Signed-off-by: Shailendra Verma
---
drivers/staging/media/lirc/lirc_imon.c |5 ++---
drivers/staging/media/lirc/lirc_s
From: "Shailendra Verma"
There is no need to call kfree() if memdup_user() fails, as no memory
was allocated and the error in the error-valued pointer should be returned.
Signed-off-by: Shailendra Verma
---
drivers/staging/media/lirc/lirc_imon.c |5 ++---
drivers/staging/media/lirc/lirc_s
Hi Ramesh,
Thank you for the patch.
On Wednesday 09 Nov 2016 15:44:44 Ramesh Shanmugasundaram wrote:
> This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs.
> The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF
> device represents a channel and each channel
Hi Ramesh,
On Friday 21 Oct 2016 14:49:30 Ramesh Shanmugasundaram wrote:
> > On Wednesday 12 Oct 2016 15:10:25 Ramesh Shanmugasundaram wrote:
> >> This patch adds driver support for MAX2175 chip. This is Maxim
> >> Integrated's RF to Bits tuner front end chip designed for
> >> software-defined rad
Em Wed, 9 Nov 2016 11:07:35 -0800
Linus Torvalds escreveu:
> On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
> >
> > Tried patch with no success. Again a NULL ptr dereferece.
>
> That patch was pure garbage, I think. Pretty much all the other
> drivers that use the same approach will have th
Hi Ramesh,
Thank you for the patch.
On Wednesday 09 Nov 2016 15:44:43 Ramesh Shanmugasundaram wrote:
> This patch adds documentation for the three new SDR formats
>
> V4L2_SDR_FMT_SCU16BE
> V4L2_SDR_FMT_SCU18BE
> V4L2_SDR_FMT_SCU20BE
>
> Signed-off-by: Ramesh Shanmugasundaram
>
> ---
> .../me
Antti, Hans, ping ? Please see below.
On Friday 04 Nov 2016 09:23:29 Ramesh Shanmugasundaram wrote:
> > On 11/02/2016 10:58 PM, Laurent Pinchart wrote:
> >> On Wednesday 02 Nov 2016 09:00:00 Ramesh Shanmugasundaram wrote:
> > On Wednesday 12 Oct 2016 15:10:29 Ramesh Shanmugasundaram wrote:
> >
Em Wed, 9 Nov 2016 17:03:52 -0800
VDR User escreveu:
> >> (gdb) l *module_put+0x67
> >> 0xc10a4b87 is in module_put (kernel/module.c:1108).
> >> 1103int ret;
> >> 1104
> >> 1105if (module) {
> >> 1106preempt_disable();
> >> 1107ret =
52 matches
Mail list logo
