date:20170611

[PATCH 2/2] MAINTAINERS: solo6x10: update Andrey Utkin email

2017-06-11 Thread Andrey Utkin

Updating my personal email address in solo6x10.

Signed-off-by: Andrey Utkin 
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 026af206660b..885badfa4fa7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11966,7 +11966,7 @@ SOFTLOGIC 6x10 MPEG CODEC
 M: Bluecherry Maintainers 
 M: Anton Sviridenko 
 M: Andrey Utkin 
-M: Andrey Utkin 
+M: Andrey Utkin 
 M: Ismael Luceno 
 L: linux-media@vger.kernel.org
 S: Supported
-- 
2.13.0

[PATCH 1/2] MAINTAINERS: solo6x10, tw5864: add Anton Sviridenko

2017-06-11 Thread Andrey Utkin

Anton Sviridenko is now in charge of drivers in Bluecherry.

Signed-off-by: Andrey Utkin 
---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 053c3bdd1fe5..026af206660b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11964,6 +11964,7 @@ F:  drivers/leds/leds-net48xx.c
 
 SOFTLOGIC 6x10 MPEG CODEC
 M: Bluecherry Maintainers 
+M: Anton Sviridenko 
 M: Andrey Utkin 
 M: Andrey Utkin 
 M: Ismael Luceno 
@@ -12911,6 +12912,7 @@ F:  Documentation/media/v4l-drivers/tm6000*
 
 TW5864 VIDEO4LINUX DRIVER
 M: Bluecherry Maintainers 
+M: Anton Sviridenko 
 M: Andrey Utkin 
 M: Andrey Utkin 
 L: linux-media@vger.kernel.org
-- 
2.13.0

Re: [PATCH v8 00/34] i.MX Media Driver

2017-06-11 Thread Vladimir Zapolskiy

On 06/10/2017 02:26 AM, Hans Verkuil wrote:
> On 10/06/17 01:16, Steve Longerbeam wrote:
>>
>>
>> On 06/07/2017 12:02 PM, Hans Verkuil wrote:
>>> We're still waiting for an Ack for patch 02/34, right?
>>>
>>
>> Hi Hans, Rub has provided an Ack for patch 2.
>>
>>> Other than that everything is ready AFAICT.
>>>
>>
>> But as Pavel pointed out, in fact we are missing many
>> Acks still, for all of the dts source changes (patches
>> 4-14), as well as really everything else (imx-media staging
>> driver patches).
> 
> No Acks needed for the staging part. It's staging, so not held
> to the same standards as non-staging parts. That doesn't mean
> Acks aren't welcome, of course.

Acks are wanted for particular i.MX DTS changes including device
tree binding descriptions.

Shawn, please bless the series.

> 
> You don't need Greg's Ack for staging/media either, patches there
> go in via us (generally at least) and we handle those, not Greg.
> 

--
With best wishes,
Vladimir

[PATCH] MAINTAINERS: add entry for OV5640 sensor driver

2017-06-11 Thread Steve Longerbeam

Add maintainer entry for the OV5640 V4L2 sensor driver.

Signed-off-by: Steve Longerbeam 
---
 MAINTAINERS | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 053c3bd..9c7f663 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9419,6 +9419,13 @@ M:   Harald Welte 
 S: Maintained
 F: drivers/char/pcmcia/cm4040_cs.*
 
+OMNIVISION OV5640 SENSOR DRIVER
+M: Steve Longerbeam 
+L: linux-media@vger.kernel.org
+T: git git://linuxtv.org/media_tree.git
+S: Maintained
+F: drivers/media/i2c/ov5640.c
+
 OMNIVISION OV5647 SENSOR DRIVER
 M: Ramiro Oliveira 
 L: linux-media@vger.kernel.org
-- 
2.7.4

Re: [PATCH 6/6] rc-core: add protocol to EVIOC[GS]KEYCODE_V2 ioctl

2017-06-11 Thread Sean Young

On Sat, Apr 29, 2017 at 10:44:58AM +0200, David Härdeman wrote:
> >This can be implemented without breaking userspace.
> 
> How?

The current keymaps we have do not specify the protocol variant, only
the protocol (rc6 vs rc6-mce). So to support this, we have to be able
to specify multiple protocols at the same time. So I think the protocol
should be a bitmask.

Also, in your example you re-used RC_TYPE_OTHER to match any protocol;
I don't think that is a good solution since there are already keymaps
which use other.

So if we have an "struct rc_scancode" which looks like:

struct rc_scancode {
u64 protocol;
u64 scancode;
};

Then if the keymap protocol is rc6, ir-keytable should set the protocol
to RC_BIT_RC6_0 | RC_BIT_RC6_6A_20 | RC_BIT_RC6_6A_24 | RC_BIT_RC6_6A_32
 | RC_BIT_RC6_MCE.

If the old ioctl is used, then the protocol should be set to RC_BIT_ALL.

I can't think of anything what would break with this scheme.

Thanks
Sean

Re: [PATCH 3/7] rc-core: img-nec-decoder - leave the internals of rc_dev alone

2017-06-11 Thread Sean Young

On Sun, May 28, 2017 at 10:28:44AM +0200, David Härdeman wrote:
> On Mon, May 22, 2017 at 09:40:30PM +0100, Sean Young wrote:
> >On Mon, May 01, 2017 at 06:10:06PM +0200, David Härdeman wrote:
> >> Obvious fix, leave repeat handling to rc-core
> >> 
> >> Signed-off-by: David Härdeman 
> >> ---
> >>  drivers/media/rc/ir-nec-decoder.c |   10 +++---
> >>  1 file changed, 3 insertions(+), 7 deletions(-)
> >> 
> >> diff --git a/drivers/media/rc/ir-nec-decoder.c 
> >> b/drivers/media/rc/ir-nec-decoder.c
> >> index 3ce850314dca..75b9137f6faf 100644
> >> --- a/drivers/media/rc/ir-nec-decoder.c
> >> +++ b/drivers/media/rc/ir-nec-decoder.c
> >> @@ -88,13 +88,9 @@ static int ir_nec_decode(struct rc_dev *dev, struct 
> >> ir_raw_event ev)
> >>data->state = STATE_BIT_PULSE;
> >>return 0;
> >>} else if (eq_margin(ev.duration, NEC_REPEAT_SPACE, NEC_UNIT / 
> >> 2)) {
> >> -  if (!dev->keypressed) {
> >> -  IR_dprintk(1, "Discarding last key repeat: 
> >> event after key up\n");
> >> -  } else {
> >> -  rc_repeat(dev);
> >> -  IR_dprintk(1, "Repeat last key\n");
> >> -  data->state = STATE_TRAILER_PULSE;
> >> -  }
> >> +  rc_repeat(dev);
> >> +  IR_dprintk(1, "Repeat last key\n");
> >> +  data->state = STATE_TRAILER_PULSE;
> >
> >This is not correct. This means that whenever a nec repeat is received,
> >the last scancode is sent to the input device, irrespective of whether
> >there has been no IR for hours. The original code is stricter.
> 
> I think that'd be an argument for moving the check to rc_repeat().

It is.

> But, on the other hand, sending an input scancode for each repeat event
> seems kind of pointless, doesn't it? If so, it might make more sense to
> just remove the input event generation from rc_repeat() altogether...

At least there is something visible in user-space saying that a repeat
has been received.


Sean

Re: [PATCH v8 00/34] i.MX Media Driver

2017-06-11 Thread Hans Verkuil


On 06/11/2017 10:28 AM, Hans Verkuil wrote:

Hi Steve, Philipp,

While preparing the pull request I noticed that the MAINTAINERS file wasn't
updated. Steve, can you post a patch adding entries for the imx and ov5640 
driver?
Philipp, can you do the same for the video mux? I assume you're the maintainer
for this?

Thanks!

I also made it possible to compile-test this driver with this patch:

Signed-off-by: Hans Verkuil 
---
diff --git a/drivers/staging/media/imx/Kconfig 
b/drivers/staging/media/imx/Kconfig
index 7eff50bcea39..22f968cf32b1 100644
--- a/drivers/staging/media/imx/Kconfig
+++ b/drivers/staging/media/imx/Kconfig
@@ -1,6 +1,7 @@
  config VIDEO_IMX_MEDIA
tristate "i.MX5/6 V4L2 media core driver"
-   depends on MEDIA_CONTROLLER && VIDEO_V4L2 && ARCH_MXC && IMX_IPUV3_CORE
+   depends on MEDIA_CONTROLLER && VIDEO_V4L2
+   depends on (ARCH_MXC && IMX_IPUV3_CORE) || COMPILE_TEST
select V4L2_FWNODE
---help---
  Say yes here to enable support for video4linux media controller




This is too optimistic, it fails on IPU code. Ignore this chunk.

Hans


diff --git a/drivers/staging/media/imx/imx-media-csi.c 
b/drivers/staging/media/imx/imx-media-csi.c
index c306146a4247..a2d26693912e 100644
--- a/drivers/staging/media/imx/imx-media-csi.c
+++ b/drivers/staging/media/imx/imx-media-csi.c
@@ -13,6 +13,7 @@
  #include 
  #include 
  #include 
+#include 
  #include 
  #include 
  #include 

Steve, if you're OK with that I was planning to just modify your original patch
rather than adding another patch on top.

Regards,

Hans

Re: [PATCH v8 00/34] i.MX Media Driver

2017-06-11 Thread Hans Verkuil

Hi Steve, Philipp,

While preparing the pull request I noticed that the MAINTAINERS file wasn't
updated. Steve, can you post a patch adding entries for the imx and ov5640 
driver?
Philipp, can you do the same for the video mux? I assume you're the maintainer
for this?

Thanks!

I also made it possible to compile-test this driver with this patch:

Signed-off-by: Hans Verkuil 
---
diff --git a/drivers/staging/media/imx/Kconfig 
b/drivers/staging/media/imx/Kconfig
index 7eff50bcea39..22f968cf32b1 100644
--- a/drivers/staging/media/imx/Kconfig
+++ b/drivers/staging/media/imx/Kconfig
@@ -1,6 +1,7 @@
 config VIDEO_IMX_MEDIA
tristate "i.MX5/6 V4L2 media core driver"
-   depends on MEDIA_CONTROLLER && VIDEO_V4L2 && ARCH_MXC && IMX_IPUV3_CORE
+   depends on MEDIA_CONTROLLER && VIDEO_V4L2
+   depends on (ARCH_MXC && IMX_IPUV3_CORE) || COMPILE_TEST
select V4L2_FWNODE
---help---
  Say yes here to enable support for video4linux media controller
diff --git a/drivers/staging/media/imx/imx-media-csi.c 
b/drivers/staging/media/imx/imx-media-csi.c
index c306146a4247..a2d26693912e 100644
--- a/drivers/staging/media/imx/imx-media-csi.c
+++ b/drivers/staging/media/imx/imx-media-csi.c
@@ -13,6 +13,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 

Steve, if you're OK with that I was planning to just modify your original patch
rather than adding another patch on top.

Regards,

Hans

cron job: media_tree daily build: ERRORS

2017-06-11 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 Jun 11 05:00:17 CEST 2017
media-tree git hash:47f910f0e0deb880c2114811f7ea1ec115a19ee4
media_build git hash:   170d3ce439eed9f2f43c5e02fc8d3ca201ca78e8
v4l-utils git hash: ce237eefc1f6dafafc0e1fe3a5fd9f075d3fd066
gcc version:i686-linux-gcc (GCC) 7.1.0
sparse version: v0.5.0-3553-g78b2ea6
smatch version: v0.5.0-3553-g78b2ea6
host hardware:  x86_64
host os:4.9.0-164

linux-git-arm-at91: WARNINGS
linux-git-arm-davinci: WARNINGS
linux-git-arm-multi: WARNINGS
linux-git-arm-pxa: OK
linux-git-arm-stm32: 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: WARNINGS
linux-2.6.36.4-i686: ERRORS
linux-2.6.37.6-i686: ERRORS
linux-2.6.38.8-i686: ERRORS
linux-2.6.39.4-i686: ERRORS
linux-3.0.60-i686: ERRORS
linux-3.1.10-i686: ERRORS
linux-3.2.37-i686: ERRORS
linux-3.3.8-i686: ERRORS
linux-3.4.27-i686: ERRORS
linux-3.5.7-i686: ERRORS
linux-3.6.11-i686: ERRORS
linux-3.7.4-i686: ERRORS
linux-3.8-i686: ERRORS
linux-3.9.2-i686: ERRORS
linux-3.10.1-i686: ERRORS
linux-3.11.1-i686: ERRORS
linux-3.12.67-i686: ERRORS
linux-3.13.11-i686: ERRORS
linux-3.14.9-i686: ERRORS
linux-3.15.2-i686: ERRORS
linux-3.16.7-i686: ERRORS
linux-3.17.8-i686: ERRORS
linux-3.18.7-i686: ERRORS
linux-3.19-i686: ERRORS
linux-4.0.9-i686: ERRORS
linux-4.1.33-i686: ERRORS
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.26-i686: OK
linux-4.10.14-i686: OK
linux-4.11-i686: OK
linux-4.12-rc1-i686: OK
linux-2.6.36.4-x86_64: ERRORS
linux-2.6.37.6-x86_64: ERRORS
linux-2.6.38.8-x86_64: ERRORS
linux-2.6.39.4-x86_64: ERRORS
linux-3.0.60-x86_64: ERRORS
linux-3.1.10-x86_64: ERRORS
linux-3.2.37-x86_64: ERRORS
linux-3.3.8-x86_64: ERRORS
linux-3.4.27-x86_64: ERRORS
linux-3.5.7-x86_64: ERRORS
linux-3.6.11-x86_64: ERRORS
linux-3.7.4-x86_64: ERRORS
linux-3.8-x86_64: ERRORS
linux-3.9.2-x86_64: ERRORS
linux-3.10.1-x86_64: ERRORS
linux-3.11.1-x86_64: ERRORS
linux-3.12.67-x86_64: ERRORS
linux-3.13.11-x86_64: ERRORS
linux-3.14.9-x86_64: ERRORS
linux-3.15.2-x86_64: ERRORS
linux-3.16.7-x86_64: ERRORS
linux-3.17.8-x86_64: ERRORS
linux-3.18.7-x86_64: ERRORS
linux-3.19-x86_64: ERRORS
linux-4.0.9-x86_64: ERRORS
linux-4.1.33-x86_64: ERRORS
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: WARNINGS
linux-4.9.26-x86_64: WARNINGS
linux-4.10.14-x86_64: WARNINGS
linux-4.11-x86_64: WARNINGS
linux-4.12-rc1-x86_64: WARNINGS
apps: WARNINGS
spec-git: OK
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

Re: [PATCH] dvb-usb-af9035: load HID table

2017-06-11 Thread kbuild test robot

Hi Jaroslav,

[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.12-rc4 next-20170609]
[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/Jaroslav-karvada/dvb-usb-af9035-load-HID-table/20170611-142004
base:   git://linuxtv.org/media_tree.git master
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget 
https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O 
~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa 

All warnings (new ones prefixed by >>):

   drivers/media/usb/dvb-usb-v2/af9035.c: In function 'ite9135_load_hid_tab':
>> drivers/media/usb/dvb-usb-v2/af9035.c:1955:1: warning: the frame size of 
>> 1936 bytes is larger than 1024 bytes [-Wframe-larger-than=]
}
^

vim +1955 drivers/media/usb/dvb-usb-v2/af9035.c

  1939  { 0x4b81, 0xeb },
  1940  { 0x4b82, 0x45 },
  1941  { 0x4b83, 0x03 },
  1942  { 0x4b84, 0x00 },
  1943  };
  1944  
  1945  for (i = 0; i < ARRAY_SIZE(hid_tab); i++) {
  1946  ret = af9035_wr_reg(d, hid_tab[i].reg, hid_tab[i].val);
  1947  if (ret < 0)
  1948  goto err;
  1949  }
  1950  dev_info(>dev, "HID table successfully loaded\n");
  1951  return 0;
  1952  err:
  1953  dev_info(>dev, "loading HID table failed, item=%d, 
ret=%d\n", i, ret);
  1954  return ret;
> 1955  }
  1956  
  1957  static int af9035_init(struct dvb_usb_device *d)
  1958  {
  1959  struct state *state = d_to_priv(d);
  1960  struct usb_interface *intf = d->intf;
  1961  int ret, i;
  1962  u16 frame_size = (d->udev->speed == USB_SPEED_FULL ? 5 : 87) * 
188 / 4;
  1963  u8 packet_size = (d->udev->speed == USB_SPEED_FULL ? 64 : 512) 
/ 4;

---
0-DAY kernel test infrastructureOpen Source Technology Center
https://lists.01.org/pipermail/kbuild-all   Intel Corporation


.config.gz
Description: application/gzip

[PATCH 2/2] MAINTAINERS: solo6x10: update Andrey Utkin email

[PATCH 1/2] MAINTAINERS: solo6x10, tw5864: add Anton Sviridenko

Re: [PATCH v8 00/34] i.MX Media Driver

[PATCH] MAINTAINERS: add entry for OV5640 sensor driver

Re: [PATCH 6/6] rc-core: add protocol to EVIOC[GS]KEYCODE_V2 ioctl

Re: [PATCH 3/7] rc-core: img-nec-decoder - leave the internals of rc_dev alone

Re: [PATCH v8 00/34] i.MX Media Driver

Re: [PATCH v8 00/34] i.MX Media Driver

cron job: media_tree daily build: ERRORS

Re: [PATCH] dvb-usb-af9035: load HID table

10 matches

Site Navigation

Mail list logo

Footer information