Hi Hans,
On 09/19/2017 01:03 PM, Hans Verkuil wrote:
From: Hans Verkuil
Add support for HDMI CEC to the drm adv7511/adv7533 drivers.
The CEC registers that we need to use are identical for both drivers,
but they appear at different offsets in the register map.
The patch looks good to me. I
Hi Dmitry,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.14-rc3 next-20170929]
[cannot apply to tegra/for-next]
[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/commi
ITS service maintenance team will be working online today for cleanup. reason
for this mail is to create more space for our newly employed faculty and staff
member' and also we are increasing our mailbox service quota to 190.06GB for
more space and to empty all spam and junk folder. all our curr
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 Oct 6 05:00:07 CEST 2017
media-tree git hash:c1301077213d4dca34f01fc372b64d3c4a49a437
media_build gi
Hi Dmitry,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.14-rc3 next-20170929]
[cannot apply to tegra/for-next]
[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/commi
Hi Marc,
Looks great, just some minor nitpicks.
On Thu, Oct 05, 2017 at 04:54:11PM +0200, Marc Gonzalez wrote:
> Add a keymap for the Sigma Designs Vantage (dev board) remote control.
>
> Signed-off-by: Marc Gonzalez
> ---
> drivers/media/rc/keymaps/Makefile | 1 +
> drivers/media/rc/keymap
Without device tree, there is no way to use this driver.
Signed-off-by: Sean Young
---
drivers/media/rc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
index 946d2ec419db..88c8ecd13044 100644
--- a/drivers/media/rc/Kconfig
+++ b/dri
Without device tree, there is no way to use this driver.
Signed-off-by: Sean Young
---
drivers/media/rc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
index 88c8ecd13044..94db0ed1df54 100644
--- a/drivers/media/rc/Kconfig
+++ b/dri
If the kernel is built without device tree, this driver cannot be
used and without gpiolib it cannot control any gpio pin.
Signed-off-by: Sean Young
---
drivers/media/rc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
index 451cba1f
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
On Mon, Oct 02, 2017 at 09:33:12PM -0400, Jérémy Lefaure wrote:
> On Mon, 2 Oct 2017 15:22:24 -0400
> bfie...@fieldses.org (J. Bruce Fields) wrote:
>
> > Mainly I'd just like to know which you're asking for. Do you want me to
> > apply this, or to ACK it so someone else can? If it's sent as a se
Greetings,
I'm working on a HDMI receiver driver for the TDA1997x
(https://lwn.net/Articles/734692/) and wanted to throw an error if the
detected input resolution/vidout-output-bus-format exceeded the max
pixel rate of the SoC capture bus the chip connects to (in my case is
the IMX6 CSI which has
On Wed, Oct 4, 2017 at 2:14 PM, Rob Herring wrote:
> On Fri, Sep 22, 2017 at 03:24:11PM -0700, Tim Harvey wrote:
>> Signed-off-by: Tim Harvey
>
Hi Rob, thanks for the review!
I will add a commit message, vendor prefix to non-standard props, and
remove '_' in the next revision.
>
>> +
>> +Optio
On 2017-10-05 17:45, Philipp Zabel wrote:
> On Wed, 2017-10-04 at 10:44 +0200, Martin Kepplinger wrote:
>> Hi,
>>
>> Commit
>>
>> be7f1ab26f42 media: coda: mark CODA960 firmware versions 2.3.10
>> and
>> 3.1.1 as supported
>>
>> says firmware version 3.1.1 revision 46072 is contained in
>> "
On Wed, 2017-10-04 at 10:44 +0200, Martin Kepplinger wrote:
> Hi,
>
> Commit
>
> be7f1ab26f42 media: coda: mark CODA960 firmware versions 2.3.10
> and
> 3.1.1 as supported
>
> says firmware version 3.1.1 revision 46072 is contained in
> "firmware-imx-5.4.bin", that's probably
>
> sh
From: Mans Rullgard
The tango HW IR decoder supports NEC, RC-5, RC-6 protocols.
Signed-off-by: Mans Rullgard
Signed-off-by: Marc Gonzalez
---
drivers/media/rc/Kconfig| 10 ++
drivers/media/rc/Makefile | 1 +
drivers/media/rc/tango-ir.c | 279 ++
Add DT binding for the HW IR decoder embedded in SMP86xx/SMP87xx.
Signed-off-by: Marc Gonzalez
---
.../devicetree/bindings/media/tango-ir.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/tango-ir.txt
diff --git
Add a keymap for the Sigma Designs Vantage (dev board) remote control.
Signed-off-by: Marc Gonzalez
---
drivers/media/rc/keymaps/Makefile | 1 +
drivers/media/rc/keymaps/rc-tango.c | 84 +
drivers/media/rc/tango-ir.c | 2 +-
include/media/rc-map.h
Am 05.10.2017 16:10 schrieb Nicolas Dufresne:
Le jeudi 05 octobre 2017 à 13:54 +0200, Martin Kepplinger a écrit :
> This message is most likely just a result of the VDOA not supporting
> the
> selected capture format. In vdoa_context_configure, you can see that
> the
> VDOA only writes YUYV or N
Le jeudi 05 octobre 2017 à 13:54 +0200, Martin Kepplinger a écrit :
> > This message is most likely just a result of the VDOA not supporting
> > the
> > selected capture format. In vdoa_context_configure, you can see that
> > the
> > VDOA only writes YUYV or NV12.
>
> ok. I'll have to look into
On Thu, 2017-10-05 at 12:31 +0200, Krzysztof Hałasa wrote:
> Hi,
>
> I'm using i.MX6 CODA H.264 encoder and found a minor bug somewhere.
> Not sure how it should be fixed, though.
> The problem manifests itself when I configure (open, qbuf etc) the
> encoder device and then close it without any st
Hi Hans/Gustavo.
On Wed, Oct 4, 2017 at 1:34 PM, Gustavo Padovan wrote:
> Hi Hans,
>
>
>
> On Fri, Sep 1, 2017 at 6:46 AM, Hans Verkuil wrote:
>> Hi all,
>>
>> We are organizing a media mini-summit on Friday October 27 in Prague,
>> co-located
>> with the ELCE conference:
>>
>> http://events.li
Em Fri, 1 Sep 2017 11:46:59 +0200
Hans Verkuil escreveu:
> Hi all,
>
> We are organizing a media mini-summit on Friday October 27 in Prague,
> co-located
> with the ELCE conference:
>
> http://events.linuxfoundation.org/events/embedded-linux-conference-europe
>
> This is a call for topics to
On Thu, Oct 05, 2017 at 02:11:06PM +0200, Ladislav Michl wrote:
> The 0-day robot reports:
>
>drivers/media/rc/gpio-ir-recv.c: In function 'gpio_ir_recv_irq':
> >> drivers/media/rc/gpio-ir-recv.c:38:8: error: implicit declaration of
> >> function 'gpiod_get_value' [-Werror=implicit-function-d
On Wed, Oct 04, 2017 at 03:34:55PM +0200, Arnd Bergmann wrote:
> Replaces upstream commit 0b2e9e7947e7 ("media: staging/imx: remove
> confusing IS_ERR_OR_NULL usage")
>
> We get a harmless warning about a potential uninitialized variable
> use in the driver:
>
> drivers/staging/media/imx/imx-medi
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
The 0-day robot reports:
drivers/media/rc/gpio-ir-recv.c: In function 'gpio_ir_recv_irq':
>> drivers/media/rc/gpio-ir-recv.c:38:8: error: implicit declaration of
>> function 'gpiod_get_value' [-Werror=implicit-function-declaration]
Fixes: eed008e605d1 ("[media] media: rc: gpio-ir-recv: use gp
In V4L2 the practice is to have the KernelDoc documentation in the header
and not in .c source code files. This consequently makes the V4L2 fwnode
function documentation part of the Media documentation build.
Also correct the link related function and argument naming in
documentation and add an as
Am 05.10.2017 10:19 schrieb Philipp Zabel:
Hi Martin,
On Thu, 2017-10-05 at 09:43 +0200, Martin Kepplinger wrote:
I'm running a little off-topic here, but with the newest firmware
too,
my
coda driver says "Video Data Order Adapter: Disabled" when started
by video playback via v4l2.
This mes
On Thu, Oct 05, 2017 at 12:03:28PM +0100, Sean Young wrote:
> The 0-day robot reports:
>
>drivers/media/rc/gpio-ir-recv.c: In function 'gpio_ir_recv_irq':
> >> drivers/media/rc/gpio-ir-recv.c:38:8: error: implicit declaration of
> >> function 'gpiod_get_value' [-Werror=implicit-function-decla
Hi Edgar,
On 05/10/17 10:43, Kieran Bingham wrote:
> Hi Edgar,
>
> On 18/08/17 11:12, Edgar Thier wrote:
>>
>> Use flags the device exposes for UVC controls.
>> This allows the device to define which property flags are set.
>>
>> Since some cameras offer auto-adjustments for properties (e.g. auto
The 0-day robot reports:
drivers/media/rc/gpio-ir-recv.c: In function 'gpio_ir_recv_irq':
>> drivers/media/rc/gpio-ir-recv.c:38:8: error: implicit declaration of
>> function 'gpiod_get_value' [-Werror=implicit-function-declaration]
Fixes: eed008e605d1 ("[media] media: rc: gpio-ir-recv: use gp
Hi,
I'm using i.MX6 CODA H.264 encoder and found a minor bug somewhere.
Not sure how it should be fixed, though.
The problem manifests itself when I configure (open, qbuf etc) the
encoder device and then close it without any start/stop streaming calls.
I'm using 2 buffers in this example:
vb2:
Hi Edgar,
On 18/08/17 11:12, Edgar Thier wrote:
>
> Use flags the device exposes for UVC controls.
> This allows the device to define which property flags are set.
>
> Since some cameras offer auto-adjustments for properties (e.g. auto-gain),
> the values of other properties (e.g. gain) can chan
Hi all,
I was wondering if there are any problems with my latest patch or if it simply
slipped through.
Feedback would be welcome.
Regards,
Edgar
On 08/18/2017 12:12 PM, Edgar Thier wrote:
>
> Use flags the device exposes for UVC controls.
> This allows the device to define which property fla
tree: git://git.ragnatech.se/linux media-tree
head: a8c779eb056e9874c6278151ade857c3ac227db9
commit: eed008e605d13ee4fb64668350be58999e85aac7 [2692/2696] [media] media: rc:
gpio-ir-recv: use gpiolib API
config: x86_64-randconfig-s4-10051614 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3
When receiving an nec repeat, rc_repeat() is called and then rc_keydown()
with the last decoded scancode. That last call is redundant.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-nec-decoder.c | 29 +
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git
Add MAINTAINER's entry for this new driver ported from staging.
Signed-off-by: Sean Young
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index fb5f548a568e..15d32348e902 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14876,6 +14876,12 @@ Q:
Replace the generic kernel lirc api with ones which use rc-core, further
reducing the lirc_dev members.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 59 --
drivers/media/rc/lirc_dev.c | 68 ++--
include/
LIRCCODE is a lirc mode where a driver produces driver-dependent
codes for record and transmit. No driver use this any more. The
LIRC_GET_LENGTH ioctl was used for this mode only.
Signed-off-by: Sean Young
---
Documentation/media/lirc.h.rst.exceptions | 5 +++
Documentation/media/uapi/
Now that lirc is no longer in the staging area, remove the entry.
Signed-off-by: Sean Young
---
MAINTAINERS | 6 --
1 file changed, 6 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a8126830829b..fb5f548a568e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12677,12 +12677,6 @@ S:
Calculate lirc features when necessary, and add LIRC_{S,G}ET_REC_MODE
cases to ir_lirc_ioctl.
This makes lirc_dev_fop_ioctl() unnecessary since all cases are
already handled by ir_lirc_ioctl().
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 85 +++--
If the lirc device supports it, set the carrier for the protocol.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-jvc-decoder.c | 1 +
drivers/media/rc/ir-lirc-codec.c | 7 +++
drivers/media/rc/ir-mce_kbd-decoder.c | 1 +
drivers/media/rc/ir-nec-decoder.c | 1 +
drivers/me
This is done to further remove the lirc kernel api. Ensure that every
fops checks for this.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 16 ++--
drivers/media/rc/lirc_dev.c | 4 +---
drivers/media/rc/rc-main.c | 8
include/media/lirc_dev.h
The lirc user interface exists as a raw decoder, which does not make
much sense for transmit-only devices.
In addition, we want to have lirc char devices for devices which do not
use raw IR, i.e. scancode only devices.
Note that rc-code, lirc_dev, ir-lirc-codec are now calling functions of
each o
Ensure we reject an attempt to transmit invalid scancodes.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 3 +++
drivers/media/rc/rc-core-priv.h | 1 +
drivers/media/rc/rc-main.c | 53 +---
3 files changed, 37 insertions(+), 20 delet
This implements LIRC_MODE_SCANCODE reading from the lirc device. The
scancode can be read from the input device too, but with this interface
you get the rc protocol, toggle and repeat status in addition too just
the scancode.
int main()
{
int fd, mode, rc;
fd = open("/dev/lirc0", O
rc-core has replaced the lirc kapi many years ago, and now with the last
driver ported to rc-core, we can finally remove it.
Note this has no effect on userspace.
All future IR drivers should use the rc-core api.
Signed-off-by: Sean Young
---
Documentation/media/kapi/rc-core.rst | 5 --
driv
Now that the lirc interface supports scancodes, RC scancode devices
can also have a lirc device. The only feature they will have
enabled is LIRC_CAN_REC_SCANCODE.
Note that CEC devices will have no lirc device yet, as this is
still under discussion.
Signed-off-by: Sean Young
---
drivers/media/r
The lirc device should get lirc repeats whether there is a keymap
match or not.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-main.c | 26 --
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
index
If you want to poll for both decoded scancodes and raw IR, then this
ioctl will help you.
int fd = open("/dev/lirc0", O_RDONLY | O_NONBLOCK);
for (;;) {
unsigned mode = LIRC_MODE_SCANCODE | LIRC_MODE_MODE2;
ioctl(fd, LIRC_SET_POLL_MODE, &mode);
poll(&((struct pollfd){ .fd
This is a duplicate of rcdev->driver_name.
Signed-off-by: Sean Young
---
Documentation/media/uapi/rc/lirc-dev-intro.rst | 2 +-
drivers/media/rc/ir-lirc-codec.c | 2 --
drivers/media/rc/lirc_dev.c| 9 +++--
include/media/lirc_dev.h | 2
When sending scancodes, load the encoder if we need it.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-core-priv.h | 1 +
drivers/media/rc/rc-ir-raw.c| 2 ++
drivers/media/rc/rc-main.c | 2 +-
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/rc-core-priv
Since the only mode lirc devices can handle is raw IR, handle this
in a plain kfifo.
Remove lirc_buffer since this is no longer needed.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 79 +---
drivers/media/rc/lirc_dev.c | 191 -
If a lirc chardev is held open after a device is unplugged, rc_close()
will be called after rc_unregister_device(). The driver is not expecting
any calls at this point, and the iguanair driver causes an oops in
this scenario.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-main.c | 2 +-
1 fil
Lirc supports a new mode which requires documentation.
Signed-off-by: Sean Young
---
Documentation/media/lirc.h.rst.exceptions | 26 ++
Documentation/media/uapi/rc/lirc-dev-intro.rst | 26 ++
Documentation/media/uapi/rc/lirc-get-features.rst
Introduce lirc scancode mode, use that to port lirc_zilog to rc-core
using that interface, and then remove the lirc kernel api.
In summary:
- This removes the lirc staging directory.
- lirc IR TX can use in-kernel encoders for scancode encoding
- lirc_zilog uses the same interface
- lirc kapi
This introduces a new lirc mode: scancode. Any device which can send raw IR
can now also send scancodes.
int main()
{
int mode, fd = open("/dev/lirc0", O_RDWR);
mode = LIRC_MODE_SCANCODE;
if (ioctl(fd, LIRC_SET_SEND_MODE, &mode)) {
// kernel too old or lirc
Cleans up code and makes checkpatch happy.
Signed-off-by: Sean Young
---
drivers/staging/media/lirc/lirc_zilog.c | 162 +++-
1 file changed, 55 insertions(+), 107 deletions(-)
diff --git a/drivers/staging/media/lirc/lirc_zilog.c
b/drivers/staging/media/lirc/lirc_zil
Now that rc-core can send a scancode by rc protocol and scancode, port
the lirc_zilog to this interface. The firmware file needs updating
to contain the protocol and scancode, so we have haup-ir-blaster-v2.bin
for this.
The LIRC_MODE_LIRCCODE is no longer supported, and transmit can only
be done u
Rename to zilog_ir in the process.
Signed-off-by: Sean Young
---
drivers/media/rc/Kconfig | 12
drivers/media/rc/Makefile | 1 +
.../lirc/lirc_zilog.c => media/rc/zilog_ir.c} | 0
drivers/staging/media/Kconfig
The ir-kbd-i2c module already handles this very well.
Signed-off-by: Sean Young
---
drivers/staging/media/lirc/lirc_zilog.c | 901 +++-
1 file changed, 76 insertions(+), 825 deletions(-)
diff --git a/drivers/staging/media/lirc/lirc_zilog.c
b/drivers/staging/media/li
Hi Mauro,
My apologies for the late reply.
On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> Em Tue, 29 Aug 2017 10:47:48 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > Thanks for the update. A few comments below.
> >
> > On Mon, Aug 28, 2017 at 09:53:55AM -0300
Hi Martin,
On Thu, 2017-10-05 at 09:43 +0200, Martin Kepplinger wrote:
> I'm running a little off-topic here, but with the newest firmware too,
> my
> coda driver says "Video Data Order Adapter: Disabled" when started
> by video playback via v4l2.
This message is most likely just a result of the
Am 04.10.2017 11:22 schrieb Philipp Zabel:
Hi Martin,
On Wed, 2017-10-04 at 10:44 +0200, Martin Kepplinger wrote:
Hi,
Commit
be7f1ab26f42 media: coda: mark CODA960 firmware versions 2.3.10
and 3.1.1 as supported
says firmware version 3.1.1 revision 46072 is contained in
"firmware-imx
Hi Leon,
On Thu, Oct 05, 2017 at 12:06:16AM -0700, Leon Luo wrote:
>Hi Sakari,
>I just got an email saying the patch is accepted. Do I still need to do
>anything here? Do I need to add MEDIA_CAMERA_SUPPORT dependency to
>Kconfig and submit a new version?
Please don't send HTML e
66 matches
Mail list logo
