[linux-next:master 7190/10372] htmldocs: Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain".

2016-12-03 Thread kbuild test robot 
tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 
master
head:   e05f574a0bb1f4502a4b2264fdb0ef6419cf3772
commit: 1dc4bbf0b268246f6202c761016735933b6f0b99 [7190/10372] docs-rst: 
doc-guide: split the kernel-documentation.rst contents
reproduce: make htmldocs

All errors (new ones prefixed by >>):

   make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
   include/linux/init.h:1: warning: no structured comments found
   include/linux/kthread.h:26: warning: Excess function parameter '...' 
description in 'kthread_create'
   kernel/sys.c:1: warning: no structured comments found
   Error: Cannot open file drivers/dma-buf/dma-fence.c
   Error: Cannot open file drivers/dma-buf/dma-fence.c
   WARNING: kernel-doc 'scripts/kernel-doc -rst -enable-lineno -export 
drivers/dma-buf/dma-fence.c' failed with return code 2
   Error: Cannot open file include/linux/dma-fence.h
   Error: Cannot open file include/linux/dma-fence.h
   WARNING: kernel-doc 'scripts/kernel-doc -rst -enable-lineno -internal 
include/linux/dma-fence.h' failed with return code 2
   drivers/dma-buf/seqno-fence.c:1: warning: no structured comments found
   Error: Cannot open file drivers/dma-buf/dma-fence-array.c
   Error: Cannot open file drivers/dma-buf/dma-fence-array.c
   WARNING: kernel-doc 'scripts/kernel-doc -rst -enable-lineno -export 
drivers/dma-buf/dma-fence-array.c' failed with return code 2
   Error: Cannot open file include/linux/dma-fence-array.h
   Error: Cannot open file include/linux/dma-fence-array.h
   WARNING: kernel-doc 'scripts/kernel-doc -rst -enable-lineno -internal 
include/linux/dma-fence-array.h' failed with return code 2
   include/uapi/linux/vtpm_proxy.h:1: warning: no structured comments found
   drivers/char/tpm/tpm_vtpm_proxy.c:71: warning: No description found for 
parameter 'filp'
   drivers/char/tpm/tpm_vtpm_proxy.c:71: warning: No description found for 
parameter 'buf'
   drivers/char/tpm/tpm_vtpm_proxy.c:71: warning: No description found for 
parameter 'count'
   drivers/char/tpm/tpm_vtpm_proxy.c:71: warning: No description found for 
parameter 'off'
   drivers/char/tpm/tpm_vtpm_proxy.c:121: warning: No description found for 
parameter 'filp'
   drivers/char/tpm/tpm_vtpm_proxy.c:121: warning: No description found for 
parameter 'buf'
   drivers/char/tpm/tpm_vtpm_proxy.c:121: warning: No description found for 
parameter 'count'
   drivers/char/tpm/tpm_vtpm_proxy.c:121: warning: No description found for 
parameter 'off'
   drivers/char/tpm/tpm_vtpm_proxy.c:201: warning: No description found for 
parameter 'proxy_dev'
   drivers/char/tpm/tpm_vtpm_proxy.c:1: warning: no structured comments found
   include/sound/compress_driver.h:162: warning: No description found for 
parameter 'id[64]'
   include/sound/compress_driver.h:162: warning: No description found for 
parameter 'proc_root'
   include/sound/compress_driver.h:162: warning: No description found for 
parameter 'proc_info_entry'
   include/net/mac80211.h:3207: ERROR: Unexpected indentation.
   include/net/mac80211.h:3210: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   include/net/mac80211.h:3212: ERROR: Unexpected indentation.
   include/net/mac80211.h:3213: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   include/net/mac80211.h:1772: ERROR: Unexpected indentation.
   include/net/mac80211.h:1776: WARNING: Block quote ends without a blank line; 
unexpected unindent.
>> Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx 
>> c domain".
   kernel/sched/fair.c:7259: WARNING: Inline emphasis start-string without 
end-string.
   kernel/time/timer.c:1240: ERROR: Unexpected indentation.
   kernel/time/timer.c:1242: ERROR: Unexpected indentation.
   kernel/time/timer.c:1243: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   include/linux/wait.h:121: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   include/linux/wait.h:124: ERROR: Unexpected indentation.
   include/linux/wait.h:126: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   kernel/time/hrtimer.c:1021: WARNING: Block quote ends without a blank line; 
unexpected unindent.
   kernel/signal.c:317: WARNING: Inline literal start-string without end-string.
   drivers/base/firmware_class.c:1348: WARNING: Bullet list ends without a 
blank line; unexpected unindent.
   drivers/message/fusion/mptbase.c:5054: WARNING: Definition list ends without 
a blank line; unexpected unindent.
   drivers/tty/serial/serial_core.c:1893: WARNING: Definition list ends without 
a blank line; unexpected unindent.
   include/linux/spi/spi.h:369: ERROR: Unexpected indentation.
   drivers/usb/core/message.c:478: ERROR: Unexpected indentation.
   drivers/usb/core/message.c:479: WARNING: Block quote ends without a blank 
line; unexpected unindent.
   Documentation/driver-api/usb.rst:623: ERROR: Unknown target name: "usb_type".

[PATCH 1/1] media: pci: meye: set error code on failures

2016-12-03 Thread Pan Bian 
From: Pan Bian 

The value of return variable ret is 0 on some error paths, for example,
when pci_resource_start() returns a NULL pointer. 0 means no error in
this context, which is contrary to the fact. This patch fixes the bug.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189011

Signed-off-by: Pan Bian 
---
 drivers/media/pci/meye/meye.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/media/pci/meye/meye.c b/drivers/media/pci/meye/meye.c
index ba887e8..115e141 100644
--- a/drivers/media/pci/meye/meye.c
+++ b/drivers/media/pci/meye/meye.c
@@ -1669,6 +1669,7 @@ static int meye_probe(struct pci_dev *pcidev, const 
struct pci_device_id *ent)
goto outenabledev;
}
 
+   ret = -EIO;
mchip_adr = pci_resource_start(meye.mchip_dev,0);
if (!mchip_adr) {
v4l2_err(v4l2_dev, "meye: mchip has no device base address\n");
-- 
1.9.1


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 1/1] media: pci: meye: set error code on failures

2016-12-03 Thread Pan Bian 
From: Pan Bian 

The value of return variable ret is 0 on some error paths, for example,
when pci_resource_start() returns a NULL pointer. 0 means no error in
this context, which is contrary to the fact. This patch fixes the bug.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189011

Signed-off-by: Pan Bian 
---
 drivers/media/pci/meye/meye.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/media/pci/meye/meye.c b/drivers/media/pci/meye/meye.c
index ba887e8..115e141 100644
--- a/drivers/media/pci/meye/meye.c
+++ b/drivers/media/pci/meye/meye.c
@@ -1669,6 +1669,7 @@ static int meye_probe(struct pci_dev *pcidev, const 
struct pci_device_id *ent)
goto outenabledev;
}
 
+   ret = -EIO;
mchip_adr = pci_resource_start(meye.mchip_dev,0);
if (!mchip_adr) {
v4l2_err(v4l2_dev, "meye: mchip has no device base address\n");
-- 
1.9.1


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

cron job: media_tree daily build: ERRORS

2016-12-03 Thread Hans Verkuil 
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:   Sun Dec  4 05:00:16 CET 2016
media-tree git hash:365fe4e0ce218dc5ad10df17b150a366b6015499
media_build git hash:   1606032398b1d79149c1507be2029e1a00d8dff0
v4l-utils git hash: 063d1f5d5e60783002d781e8a23911acbda65e99
gcc version:i686-linux-gcc (GCC) 6.2.0
sparse version: v0.5.0-3553-g78b2ea6
smatch version: v0.5.0-3553-g78b2ea6
host hardware:  x86_64
host os:4.8.0-164

linux-git-arm-at91: OK
linux-git-arm-davinci: OK
linux-git-arm-multi: OK
linux-git-arm-pxa: OK
linux-git-blackfin-bf561: OK
linux-git-i686: OK
linux-git-m32r: OK
linux-git-mips: OK
linux-git-powerpc64: OK
linux-git-sh: OK
linux-git-x86_64: OK
linux-2.6.36.4-i686: WARNINGS
linux-2.6.37.6-i686: WARNINGS
linux-2.6.38.8-i686: WARNINGS
linux-2.6.39.4-i686: WARNINGS
linux-3.0.60-i686: WARNINGS
linux-3.1.10-i686: WARNINGS
linux-3.2.37-i686: WARNINGS
linux-3.3.8-i686: WARNINGS
linux-3.4.27-i686: WARNINGS
linux-3.5.7-i686: WARNINGS
linux-3.6.11-i686: WARNINGS
linux-3.7.4-i686: WARNINGS
linux-3.8-i686: WARNINGS
linux-3.9.2-i686: WARNINGS
linux-3.10.1-i686: WARNINGS
linux-3.11.1-i686: OK
linux-3.12.67-i686: OK
linux-3.13.11-i686: WARNINGS
linux-3.14.9-i686: WARNINGS
linux-3.15.2-i686: WARNINGS
linux-3.16.7-i686: WARNINGS
linux-3.17.8-i686: WARNINGS
linux-3.18.7-i686: WARNINGS
linux-3.19-i686: WARNINGS
linux-4.0.9-i686: WARNINGS
linux-4.1.33-i686: WARNINGS
linux-4.2.8-i686: WARNINGS
linux-4.3.6-i686: WARNINGS
linux-4.4.22-i686: WARNINGS
linux-4.5.7-i686: WARNINGS
linux-4.6.7-i686: WARNINGS
linux-4.7.5-i686: WARNINGS
linux-4.8-i686: OK
linux-4.9-rc5-i686: OK
linux-2.6.36.4-x86_64: WARNINGS
linux-2.6.37.6-x86_64: WARNINGS
linux-2.6.38.8-x86_64: WARNINGS
linux-2.6.39.4-x86_64: WARNINGS
linux-3.0.60-x86_64: WARNINGS
linux-3.1.10-x86_64: WARNINGS
linux-3.2.37-x86_64: WARNINGS
linux-3.3.8-x86_64: WARNINGS
linux-3.4.27-x86_64: WARNINGS
linux-3.5.7-x86_64: WARNINGS
linux-3.6.11-x86_64: WARNINGS
linux-3.7.4-x86_64: WARNINGS
linux-3.8-x86_64: WARNINGS
linux-3.9.2-x86_64: WARNINGS
linux-3.10.1-x86_64: WARNINGS
linux-3.11.1-x86_64: OK
linux-3.12.67-x86_64: OK
linux-3.13.11-x86_64: WARNINGS
linux-3.14.9-x86_64: WARNINGS
linux-3.15.2-x86_64: WARNINGS
linux-3.16.7-x86_64: WARNINGS
linux-3.17.8-x86_64: WARNINGS
linux-3.18.7-x86_64: WARNINGS
linux-3.19-x86_64: WARNINGS
linux-4.0.9-x86_64: WARNINGS
linux-4.1.33-x86_64: WARNINGS
linux-4.2.8-x86_64: WARNINGS
linux-4.3.6-x86_64: WARNINGS
linux-4.4.22-x86_64: WARNINGS
linux-4.5.7-x86_64: WARNINGS
linux-4.6.7-x86_64: WARNINGS
linux-4.7.5-x86_64: WARNINGS
linux-4.8-x86_64: OK
linux-4.9-rc5-x86_64: OK
apps: WARNINGS
spec-git: OK
smatch: ERRORS
sparse: WARNINGS

Detailed results are available here:

http://www.xs4all.nl/~hverkuil/logs/Sunday.log

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Sunday.tar.bz2

The Media Infrastructure API from this daily build is here:

http://www.xs4all.nl/~hverkuil/spec/index.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v3 3/4] stk1160: Add module param for setting the record gain.

2016-12-03 Thread Ezequiel Garcia 
On 2 December 2016 at 08:05, Mauro Carvalho Chehab
 wrote:
> Em Sun, 27 Nov 2016 12:11:48 +0100
> Marcel Hasler  escreveu:
>
>> Allow setting a custom record gain for the internal AC97 codec (if 
>> available). This can be
>> a value between 0 and 15, 8 is the default and should be suitable for most 
>> users. The Windows
>> driver also sets this to 8 without any possibility for changing it.
>
> The problem of removing the mixer is that you need this kind of
> crap to setup the volumes on a non-standard way.
>

Right, that's a good point.

> NACK.
>
> Instead, keep the alsa mixer. The way other drivers do (for example,
> em28xx) is that they configure the mixer when an input is selected,
> increasing the volume of the active audio channel to 100% and muting
> the other audio channels. Yet, as the alsa mixer is exported, users
> can change the mixer settings in runtime using some alsa (or pa)
> mixer application.
>

Yeah, the AC97 mixer we are currently leveraging
exposes many controls that have no meaning in this device,
so removing that still looks like an improvement.

I guess the proper way is creating our own mixer
(not using snd_ac97_mixer)  exposing only the record
gain knob.

Marcel, what do you think?
-- 
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v3 4/4] stk1160: Give the chip some time to retrieve data from AC97 codec.

2016-12-03 Thread Ezequiel Garcia 
On 2 December 2016 at 08:09, Mauro Carvalho Chehab
 wrote:
> Em Sun, 27 Nov 2016 12:12:36 +0100
> Marcel Hasler  escreveu:
>
>> The STK1160 needs some time to transfer data from the AC97 registers into 
>> its own. On some
>> systems reading the chip's own registers to soon will return wrong values. 
>> The "proper" way to
>> handle this would be to poll STK1160_AC97CTL_0 after every read or write 
>> command until the
>> command bit has been cleared, but this may not be worth the hassle.
>>
>> Signed-off-by: Marcel Hasler 
>> ---
>>  drivers/media/usb/stk1160/stk1160-ac97.c | 9 +
>>  1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/media/usb/stk1160/stk1160-ac97.c 
>> b/drivers/media/usb/stk1160/stk1160-ac97.c
>> index 60327af..b39f51b 100644
>> --- a/drivers/media/usb/stk1160/stk1160-ac97.c
>> +++ b/drivers/media/usb/stk1160/stk1160-ac97.c
>> @@ -23,6 +23,7 @@
>>   *
>>   */
>>
>> +#include 
>>  #include 
>>
>>  #include "stk1160.h"
>> @@ -64,6 +65,14 @@ static u16 stk1160_read_ac97(struct stk1160 *dev, u16 reg)
>>*/
>>   stk1160_write_reg(dev, STK1160_AC97CTL_0, 0x8b);
>>
>> + /*
>> +  * Give the chip some time to transfer the data.
>> +  * The proper way would be to poll STK1160_AC97CTL_0
>> +  * until the command bit has been cleared, but this
>> +  * may not be worth the hassle.
>
> Why not? Relying on a fixed amount time is not nice.
>
> Take a look at em28xx_is_ac97_ready() function, at
> drivers/media/usb/em28xx/em28xx-core.c to see how this could be
> implemented instead.
>

We were reluctant to implement this properly because the read reg
function is only used for debugging purposes, to dump registers.

That said, it's not too much of a hassle to do it properly, and
we might have to if we are going to have our own mixer.

>
>> +  */
>> + usleep_range(20, 40);
>> +
>
>>   /* Retrieve register value */
>>   stk1160_read_reg(dev, STK1160_AC97_CMD, );
>>   stk1160_read_reg(dev, STK1160_AC97_CMD + 1, );
>
>
>
> Thanks,
> Mauro



-- 
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Initial DVB-T2 scan data file for ke-Nairobi (Nairobi, Kenya)

2016-12-03 Thread Joseph Zik 
Initial DVB-T2 scan data file ke-Nairobi for Nairobi, Kenya.  Please
find patch attached

-- 
Joseph Zikusooka

diff --git a/dvb-t/ke-Nairobi b/dvb-t/ke-Nairobi
new file mode 100644
index 000..eb06512
--- /dev/null
+++ b/dvb-t/ke-Nairobi
@@ -0,0 +1,226 @@
+# location and provider: Nairobi-Kenya
+# date : 2016-12-03
+# provided by  : Joseph Zikusooka
+#  : http://joseph.zikusooka.com
+#  : joseph...@gmail.com
+#
+#--
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 47400
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 2/3
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 8K
+   GUARD_INTERVAL = 1/4
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 50600
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 56200
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 57000
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 58600
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 51400
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 57800
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 60200
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 53000
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 52200
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT22
+   FREQUENCY = 53800
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = AUTO
+   CODE_RATE_LP = AUTO
+   MODULATION = QAM/AUTO
+   TRANSMISSION_MODE = 32K
+   GUARD_INTERVAL = 1/16
+   HIERARCHY = AUTO
+   STREAM_ID = 4294967295
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT22
+   FREQUENCY = 55400
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = AUTO
+   CODE_RATE_LP = AUTO
+   MODULATION = QAM/AUTO
+   TRANSMISSION_MODE = 32K
+   GUARD_INTERVAL = 1/16
+   HIERARCHY = AUTO
+   STREAM_ID = 4294967295
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 851968000
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 3/4
+   CODE_RATE_LP = 3/4
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 4K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = 1
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 1007943680
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 1/2
+   CODE_RATE_LP = NONE
+   MODULATION = QPSK
+   TRANSMISSION_MODE = 2K
+   GUARD_INTERVAL = 1/32
+   HIERARCHY = NONE
+   INVERSION = AUTO
+
+[CHANNEL]
+   DELIVERY_SYSTEM = DVBT2
+   FREQUENCY = 1645032704
+   BANDWIDTH_HZ = 800
+   CODE_RATE_HP = 2/3
+   CODE_RATE_LP = NONE
+   MODULATION =

Hello Beautiful

2016-12-03 Thread Bentley 
Hello beautiful, How you doing today? I hope you are doing well. My name is 
Bentley, from the US. I'm in Syria right now fighting ISIS. I want to get to 
know you better, if I may be so bold. I consider myself an easy-going man, and 
I am currently looking for a relationship in which I feel loved. Please tell me 
more about yourself, if you don't mind.

Hope to hear from you soon.

Regards,
Bentley.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Possible Bug in media build WinTV SoloHD

2016-12-03 Thread ochr 
Hello,
 
first I would like to thank you very much for your continuing effort on making 
dvb hardware work on old linux kernels. I'm currently using an Odroid C2 as a 
tv server using Libreelec media build edition and two WinTV SoloHD USB sticks 
following this thread: 
http://forum.odroid.com/viewtopic.php?f=144=22887[https://deref-gmx.com/mail/client/xYeN3ugPLE8/dereferrer/?redirectUrl=http%3A%2F%2Fforum.odroid.com%2Fviewtopic.php%3Ff%3D144%26t%3D22887]
 
With the release v3 everything was working fine. But v4 does not identify 
correctly the USB Sticks. I guess it's a problem with the more recent version 
of media build included that's why I contact you directly.
 
WinTV SoloHD (2040:0264) (Identified as PCTV tripleStick (292e) (card=94)) 
needs the following kernel modules:
em28xx
si2157
si2168
and firmware of course
 
v3: working release uses mediabuild (2016-08-08-b6aa39228966)

[   11.173668] Latest git patches (needed if you report a bug to 
linux-media@vger.kernel.org):
[   11.173668]     b6aa39228966e0d3f0bc3306be1892f87792903a Merge tag 
'v4.8-rc1' into patchwork
[   11.173668]     29b4817d4018df78086157ea3a55c1d9424a7cfc Linux 4.8-rc1
[   11.173668]     857953d72f3744f325de93320cc2673795e9ca89 Merge branch 
'for-linus' of
 
...
 
[   13.167012] usbcore: registered new interface driver em28xx
[   13.169126] em28178 #0: Binding DVB extension
 
em28xx, si2157 and si2168 are correctly loaded and shown in lsmod as used.
 

 
v4: not working release uses mediabuild (2016-11-22-d3d83ee20afd)

[   11.133420] Latest git patches (needed if you report a bug to 
linux-media@vger.kernel.org):
[   11.133420]     d3d83ee20afda16ad0133ba00f63c11a8d842a35 [media] 
DaVinci-VPFE-Capture: fix error handling
[   11.133420]     399426cadf5b0539a5b2a4d805257ce8acc6aba2 [media] cx88: make 
checkpatch.pl happy
[   11.133420]     1d38971438157dc57f0a4be89abf23b472458633 [media] v4l: 
rcar_fdp1: add FCP dependency
 
...
 
[   13.127857] usbcore: registered new interface driver em28xx
[   13.130001] em28xx: Registered (Em28xx dvb Extension) extension
 
em28xx is loaded correctly and shown in lsmod as used, but si2157 and si2168 
dont come up. If they are loaded manually, they aren't used.
 

 
My guess: There is something wrong with em28xx. Attached you'll find the dmesg 
output. If you need additional information, please don't hesitate to ask.
 
Thank you very much in advance
 
Yours sincerly
Olaf
 
 

dmesg
Description: Binary data


v3
Description: Binary data


v4
Description: Binary data

[PATCH 1/1] media: platform: sti: return -ENOMEM on errors

2016-12-03 Thread Pan Bian 
From: Pan Bian 

Function bdisp_debugfs_create() returns 0 even on errors. So its caller
cannot detect the errors. It may be better to return "-ENOMEM" on the
exception paths.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188801

Signed-off-by: Pan Bian 
---
 drivers/media/platform/sti/bdisp/bdisp-debug.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/platform/sti/bdisp/bdisp-debug.c 
b/drivers/media/platform/sti/bdisp/bdisp-debug.c
index 79c5635..7af6686 100644
--- a/drivers/media/platform/sti/bdisp/bdisp-debug.c
+++ b/drivers/media/platform/sti/bdisp/bdisp-debug.c
@@ -677,7 +677,7 @@ int bdisp_debugfs_create(struct bdisp_dev *bdisp)
 
 err:
bdisp_debugfs_remove(bdisp);
-   return 0;
+   return -ENOMEM;
 }
 
 void bdisp_debugfs_remove(struct bdisp_dev *bdisp)
-- 
1.9.1


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] staging:bcm2048 : Add parentheses around variable x

2016-12-03 Thread Tabrez khan 
Add parentheses around variable x for the readability purpose.

This warning was found using checkpatch.pl.

Signed-off-by: Tabrez khan 
---
 drivers/staging/media/bcm2048/radio-bcm2048.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/media/bcm2048/radio-bcm2048.c 
b/drivers/staging/media/bcm2048/radio-bcm2048.c
index 4d9bd02..2f28dd0 100644
--- a/drivers/staging/media/bcm2048/radio-bcm2048.c
+++ b/drivers/staging/media/bcm2048/radio-bcm2048.c
@@ -185,7 +185,7 @@
 #define v4l2_to_dev(f) ((f * BCM2048_FREQV4L2_MULTI) / BCM2048_FREQDEV_UNIT)
 
 #define msb(x)  ((u8)((u16)x >> 8))
-#define lsb(x)  ((u8)((u16)x &  0x00FF))
+#define lsb(x)  ((u8)((u16)(x) &  0x00FF))
 #define compose_u16(msb, lsb)  (((u16)msb << 8) | lsb)
 
 #define BCM2048_DEFAULT_POWERING_DELAY 20
-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html