Hi, Andy,
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Andy Shevchenko
> Sent: Friday, June 16, 2017 3:53 PM
> To: Zhi, Yong
> Cc: Linux Media Mailing List ;
> sakari.ai...@linux.intel.com; Zheng, Jian Xu ;
> tf.
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: Wed Oct 11 05:00:15 CEST 2017
media-tree git hash:c1301077213d4dca34f01fc372b64d3c4a49a437
media_build gi
Hi, Andy,
Thanks for the review.
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Andy Shevchenko
> Sent: Saturday, June 17, 2017 12:07 PM
> To: Sakari Ailus
> Cc: Zhi, Yong ; Linux Media Mailing List me...@vger.ke
On faster CPUs a delay is required after the POWER_UP/RESUME command and
the DD_RESTART command. Without the delay, the DD_RESTART command often
returns -EREMOTEIO and the Si2168 does not restart.
diff --git a/drivers/media/dvb-frontends/si2168.c
b/drivers/media/dvb-frontends/si2168.c
index 1
Hi Branislav,
On Tue, Oct 10, 2017 at 03:29:19PM +0200, Branislav Radocaj wrote:
> This is a patch to the radio-bcm2048.c file that fixes up
> a warning found by the checkpatch.pl tool.
>
> Signed-off-by: Branislav Radocaj
Nice work, a few git log nit picks for you to ensure your future kernel
In the function dvb_net_ule(), the pointer h.priv is not initialized.
When a ULE packet is received, the kernel crashes.
diff --git a/drivers/media/dvb-core/dvb_net.c
b/drivers/media/dvb-core/dvb_net.c
index 06b0dcc..abfa3e5 100644
--- a/drivers/media/dvb-core/dvb_net.c
+++ b/drivers/media/dvb
Hi Mauro,
On Tue, Oct 10, 2017 at 08:37:43AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Oct 2017 15:48:22 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > On Wed, Sep 27, 2017 at 07:23:47PM -0300, Mauro Carvalho Chehab wrote:
> > > As we now have a glossary, some terms used on open.r
Hi Mauro,
On Tue, Oct 10, 2017 at 09:49:38AM -0300, Mauro Carvalho Chehab wrote:
> Em Tue, 10 Oct 2017 14:54:35 +0300
> Sakari Ailus escreveu:
>
> > On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> > > Em Fri, 6 Oct 2017 14:51:06 +0300
> > > Sakari Ailus escreveu:
> > >
For some types of tuners (Philips FMD1216ME(X) MK3 currently) we know that
letting TDA9887 output port 1 remain high (inactive) will switch FM radio
to mono mode.
Let's make use of this functionality - nothing changes for the default
stereo radio mode.
Tested on a Medion 95700 board which has a FM
This series adds support for analog part of Medion 95700 in the cxusb
driver.
What works:
* Video capture at various sizes with sequential fields,
* Input switching (TV Tuner, Composite, S-Video),
* TV and radio tuning,
* Video standard switching and auto detection,
* Radio mode switching (stereo
This patch adds support for analog part of Medion 95700 in the cxusb
driver.
What works:
* Video capture at various sizes with sequential fields,
* Input switching (TV Tuner, Composite, S-Video),
* TV and radio tuning,
* Video standard switching and auto detection,
* Radio mode switching (stereo /
This patch prepares cxusb driver for supporting the analog part of
Medion 95700 (previously only the digital - DVB - mode was supported).
Specifically, it adds support for:
* switching the device between analog and digital modes of operation,
* enforcing that only one mode is active at the same ti
This commit adds pin to pad mapping and output format configuration support
in CX2584x-series chips to cx25840 driver.
This functionality is then used to allow disabling ivtv-specific hacks
(called a "generic mode"), so cx25840 driver can be used for other devices
not needing them without risking
If set_fmt callback is called with format->width or format->height set to
zero and HACTIVE_CNT or VACTIVE_CNT bits (respectively) in chip are zero
we will divide by zero later in this callback when we try to calculate
HSC or VSC values.
Fix this by explicitly rejecting these values.
Signed-off-by
A 0b1100 value in 4 LSBs of "General Status 1" register (AFD_FMT_STAT) has
known meaning for CX2584x-series chips - it means that a SECAM signal is
currently detected by the chip.
Use this opportunity to also fix wrong binary values that were present
as comments attached to some entries in an arra
On Tue, Oct 10, 2017 at 7:36 PM, Tom Saeger wrote:
> Make admin-guide document refs valid.
>
> Signed-off-by: Tom Saeger
Acked-by: Rafael J. Wysocki
> ---
> Documentation/ABI/stable/sysfs-devices | 2 +-
> Documentation/ABI/testing/sysfs-devices-system-cpu | 6 --
> Documentat
On Mon, Oct 09, 2017 at 07:19:11AM -0300, Mauro Carvalho Chehab wrote:
> Using enums makes easier to document, as it can use kernel-doc
> markups. It also allows cross-referencing, with increases the
> kAPI readability.
>
All changes look legit.
But I'd expect cx88_querycap() return type change
On Fri, Oct 6, 2017 at 3:14 AM, Philipp Zabel wrote:
>
> On Fri, 2017-10-06 at 10:49 +0300, Sakari Ailus wrote:
> > On Thu, Oct 05, 2017 at 10:21:16AM -0700, Tim Harvey wrote:
> > > Greetings,
> > >
> > > I'm working on a HDMI receiver driver for the TDA1997x
> > > (https://lwn.net/Articles/734692
Make media doc refs valid.
Signed-off-by: Tom Saeger
---
Documentation/admin-guide/kernel-parameters.txt| 4 ++--
Documentation/media/dvb-drivers/bt8xx.rst | 8
Documentation/media/uapi/v4l/dev-sliced-vbi.rst| 2 +-
Documentation/media/uapi/v4l/extended-controls.rst | 2
Make admin-guide document refs valid.
Signed-off-by: Tom Saeger
---
Documentation/ABI/stable/sysfs-devices | 2 +-
Documentation/ABI/testing/sysfs-devices-system-cpu | 6 --
Documentation/ABI/testing/sysfs-power | 6 --
Documentation/admin-guide/README.rst
Le mardi 29 août 2017 à 14:26 +0300, Stanimir Varbanov a écrit :
> Currently videobuf2-dma-sg checks for dma direction for
> every single page and videobuf2-dc lacks any dma direction
> checks and calls set_page_dirty_lock unconditionally.
>
> Thus unify and align the invocations of set_page_dirty
More word-smithing...
On 10/10/2017 01:45 PM, Mauro Carvalho Chehab wrote:
> When we added support for omap3, back in 2010, we added a new
> type of V4L2 devices that aren't fully controlled via the V4L2
> device node.
>
> Yet, we have never clearly documented in the V4L2 specification
> the diff
Hi Hans,
On Tue, Oct 10, 2017 at 03:18:13PM +0200, Hans Verkuil wrote:
> On 10/10/2017 02:57 PM, Sakari Ailus wrote:
> > Hi Hans,
> >
> > On Mon, Oct 09, 2017 at 01:45:25PM +0200, Hans Verkuil wrote:
> >> On 04/10/17 23:50, Sakari Ailus wrote:
> >>> The notifier complete callback may return an er
On Mon, Oct 09, 2017 at 07:19:24AM -0300, Mauro Carvalho Chehab wrote:
> Use the existing macros to identify vb2_io_modes bits.
>
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
More (mostly) small stuff:
On 10/10/2017 01:45 PM, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/uapi/v4l/glossary.rst | 167
> ++
On Mon, Oct 09, 2017 at 07:19:28AM -0300, Mauro Carvalho Chehab wrote:
> Add cross-references where needed and add periods at the end of
> each kernel-doc paragraph, in order to make it coherent with other
> VB2 descriptions.
>
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
--
Hi Mauro,
On Mon, Oct 09, 2017 at 07:19:27AM -0300, Mauro Carvalho Chehab wrote:
> When we split VB2 into an independent streaming module and
> a V4L2 one, some vb2-core functions started to have a wrong
> description: they're meant to be used only by the API-specific
> parts of VB2, like vb2-v4l2
Attached is the DVB-C tuning information for Elisa cable-TV in Finnish
capital region and Riihimäki.
--
Heikki Kantola
fi-Elisa-PKS
Description: Binary data
Hi Mauro,
On Mon, Oct 09, 2017 at 07:19:25AM -0300, Mauro Carvalho Chehab wrote:
> There are several issues on the current markups:
> - lack of cross-references;
> - wrong cross-references;
> - lack of a period of the end of several phrases;
> - Some descriptions can be enhanced.
>
> Signed-off-b
This is a patch to the radio-bcm2048.c file that fixes up
a warning found by the checkpatch.pl tool.
Signed-off-by: Branislav Radocaj
---
[1]: https://marc.info/?l=linux-driver-devel&m=150331308401055&w=2
Changes in v2:
Removed unused 'size' argument from property_read macro.
In property_write
On 10/10/2017 02:57 PM, Sakari Ailus wrote:
> Hi Hans,
>
> On Mon, Oct 09, 2017 at 01:45:25PM +0200, Hans Verkuil wrote:
>> On 04/10/17 23:50, Sakari Ailus wrote:
>>> The notifier complete callback may return an error. This error code was
>>> simply returned to the caller but never handled properl
On 10/10/2017 01:27 PM, Sakari Ailus wrote:
> Hi Hans,
>
> On Mon, Oct 09, 2017 at 02:06:55PM +0200, Hans Verkuil wrote:
>> Hi Sakari,
>>
>> My reply here is also valid for v15.
>>
>> On 26/09/17 13:30, Sakari Ailus wrote:
>>> Hi Hans,
>>>
>>> Thanks for the review.
>>>
>>> On Tue, Sep 26, 2017 at
Hi Hans,
On Mon, Oct 09, 2017 at 01:45:25PM +0200, Hans Verkuil wrote:
> On 04/10/17 23:50, Sakari Ailus wrote:
> > The notifier complete callback may return an error. This error code was
> > simply returned to the caller but never handled properly.
> >
> > Move calling the complete callback func
Em Tue, 10 Oct 2017 14:54:35 +0300
Sakari Ailus escreveu:
> On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 6 Oct 2017 14:51:06 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
Hi Sylwester,
On Mon, Oct 09, 2017 at 06:44:52PM +0200, Sylwester Nawrocki wrote:
> Hi Sakari,
>
> On 10/09/2017 04:18 PM, Sakari Ailus wrote:
> > Sure, how about this at the end of the current commit message:
> >
> > If there is a need to support removing the clock provider in the future,
> > t
On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Oct 2017 14:51:06 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > > > +V4L2 device node
> > > > + A device node that is associated
Hi Alan,
On Tue, Oct 10, 2017 at 10:08:40AM +0100, Alan Cox wrote:
> > Would it make sense to first get the other drivers to upstream and
> > then see what's the status of atomisp?
>
> Agreed
>
> > the board specific information from firmware is conveyed to the
> > sensor drivers will change to
On Kernel 2.6.39, the omap3 driver was introduced together with a new way
to control complex V4L2 devices used on embedded systems, but this was
never documented, as the original idea were to have "soon" support for
standard apps to use it as well, via libv4l, but that didn't happen so far.
Also,
Right now, only kAPI documentation describes the device naming.
However, such description is needed at the uAPI too. Add it,
and describe how to get an unique identify for a given device.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Hans Verkuil
Acked-by: Sakari Ailus
---
Documentation/media
When we added support for omap3, back in 2010, we added a new
type of V4L2 devices that aren't fully controlled via the V4L2
device node.
Yet, we have never clearly documented in the V4L2 specification
the differences between the two types.
Let's document them based on the the current implementat
As both vdev-centric and MC-centric devices may implement the
same APIs, we need a flag to allow userspace to distinguish
between them.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
Acked-by: Hans Verkuil
---
Documentation/media/uapi/v4l/open.rst| 7 +++
Documenta
minor numbers use to range between 0 to 255, but that
was changed a long time ago. While it still applies when
CONFIG_VIDEO_FIXED_MINOR_RANGES, when the minor number is
dynamically allocated, this may not be true. In any case,
this is not relevant, as udev will take care of it.
So, remove this use
As we now have a glossary, some terms used on open.rst
require adjustments.
Acked-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/open.rst | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/Documentation/media/u
The documentation doesn't mention if vdev-centric hardware
control would have subdev API or not.
Add a notice about that, reflecting the current status, where
three drivers use it, in order to support some subdev-specific
controls.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Sakari Ailus
Ack
Add a glossary of terms for V4L2, as several concepts are complex
enough to cause misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/glossary.rst | 167 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 168 in
Em Fri, 6 Oct 2017 15:48:22 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> On Wed, Sep 27, 2017 at 07:23:47PM -0300, Mauro Carvalho Chehab wrote:
> > As we now have a glossary, some terms used on open.rst
> > require adjustments.
> >
> > Acked-by: Hans Verkuil
> > Signed-off-by: Mauro Carvalho C
Hi Hans,
On Mon, Oct 09, 2017 at 02:06:55PM +0200, Hans Verkuil wrote:
> Hi Sakari,
>
> My reply here is also valid for v15.
>
> On 26/09/17 13:30, Sakari Ailus wrote:
> > Hi Hans,
> >
> > Thanks for the review.
> >
> > On Tue, Sep 26, 2017 at 10:47:40AM +0200, Hans Verkuil wrote:
> >> On 26/0
On Mon, Oct 9, 2017 at 8:14 PM, Arvind Yadav wrote:
> It seems that the return value of usb_ifnum_to_if() can be NULL and
> needs to be checked.
Hi Arvind,
Your patch fixes the issue.
Thanks!
Tested-by: Andrey Konovalov
>
> Signed-off-by: Arvind Yadav
> ---
> This bug report by Andrey Konov
Em Fri, 6 Oct 2017 15:24:27 +0300
Sakari Ailus escreveu:
> > +When V4L2 was originally designed, there was only one type of
> > +media hardware control: via the **V4L2 device nodes**. We refer to this
> > kind
> > +of control as **V4L2 device node centric** (or, simply,
> > "**vdevnode-centric*
Em Fri, 6 Oct 2017 14:51:06 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > > +V4L2 device node
> > > + A device node that is associated to a V4L2 main driver,
> > > + as specified in :ref:`v4l2_device_naming`.
>
> I think we
> Would it make sense to first get the other drivers to upstream and
> then see what's the status of atomisp?
Agreed
> the board specific information from firmware is conveyed to the
> sensor drivers will change to what the rest of the sensor drivers are
> using. I think a most straightforward w
On Tue, Oct 10, 2017 at 05:30:04AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Oct 2017 13:22:29 +0300
> Sakari Ailus escreveu:
>
> > > +Bridge driver
> > > + The same as V4L2 main driver.
> >
> > Not all V4L2 main drivers can be bridge drivers. Mem-to-mem devices, for
> > instance. Ho
On Tue, Oct 10, 2017 at 10:01:36AM +0200, Marek Szyprowski wrote:
> Hi Stanimir,
>
> On 2017-10-10 09:42, Stanimir Varbanov wrote:
> > Marek,
> >
> > Any comments?
>
> Oh, I thought that this one has been already merged. If not (yet),
> here is my ack.
>
> > On 08/29/2017 02:26 PM, Stanimir Var
Add a glossary of terms for V4L2, as several concepts are complex
enough to cause misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/glossary.rst | 150 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 151 in
Em Fri, 6 Oct 2017 13:22:29 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Thanks for continuing the work on this!
>
> On Wed, Sep 27, 2017 at 07:23:43PM -0300, Mauro Carvalho Chehab wrote:
> > Add a glossary of terms for V4L2, as several concepts are complex
> > enough to cause misunderstandings
If you try to store u64 in a kfifo (or a struct with u64 members),
then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes
padding due to alignment (note that struct __kfifo is 20 bytes
on 32 bit).
That in turn causes the __is_kfifo_ptr() to fail, which is caught
by kfifo_alloc(), which now r
Em Tue, 10 Oct 2017 10:27:12 +0200
Hans Verkuil escreveu:
> > +V4L2 sub-device driver
> > + Part of the media hardware that implements support for
> > + a hardware component.
>
> The description now no longer fits the term. I suggest:
>
> "The V4L2 driver that implements support for a
Hi Yong,
On Fri, Oct 06, 2017 at 06:39:00PM -0500, Yong Zhi wrote:
> The formats added by this patch are:
>
> V4L2_PIX_FMT_IPU3_SBGGR10
> V4L2_PIX_FMT_IPU3_SGBRG10
> V4L2_PIX_FMT_IPU3_SGRBG10
> V4L2_PIX_FMT_IPU3_SRGGB10
>
> Signed-off-by: Yong Zhi
> Signed-off-by: Hyungwoo Yang
Em Fri, 6 Oct 2017 13:22:29 +0300
Sakari Ailus escreveu:
> > +Bridge driver
> > + The same as V4L2 main driver.
>
> Not all V4L2 main drivers can be bridge drivers. Mem-to-mem devices, for
> instance. How about:
>
> A driver for a device receiving image data from another device (or
> tr
On 10/10/2017 10:20 AM, Mauro Carvalho Chehab wrote:
> Em Tue, 10 Oct 2017 09:47:13 +0200
> Hans Verkuil escreveu:
>
>> On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
>>> Add a glossary of terms for V4L2, as several concepts are complex
>>> enough to cause misunderstandings.
>>>
>>> Signed-
Em Tue, 10 Oct 2017 09:47:13 +0200
Hans Verkuil escreveu:
> On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> > Add a glossary of terms for V4L2, as several concepts are complex
> > enough to cause misunderstandings.
> >
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > Documentation/m
On Tue, Oct 10, 2017 at 10:46:35AM +0800, Wenyou Yang wrote:
> To improve the readability of code, rework the format list table,
> split the format array into two. Meanwhile, fix the issue of the
> clock provider operation and the pm runtime support.
>
> Changes in v4:
> - Call pm_runtime_get_syn
On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> The documentation doesn't mention if vdev-centric hardware
> control would have subdev API or not.
>
> Add a notice about that, reflecting the current status, where
> three drivers use it, in order to support some subdev-specific
> controls.
Hi Stanimir,
On 2017-10-10 09:42, Stanimir Varbanov wrote:
Marek,
Any comments?
Oh, I thought that this one has been already merged. If not (yet),
here is my ack.
On 08/29/2017 02:26 PM, Stanimir Varbanov wrote:
Currently videobuf2-dma-sg checks for dma direction for
every single page and
On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> As both vdev-centric and MC-centric devices may implement the
> same APIs, we need a flag to allow userspace to distinguish
> between them.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/uapi/v4l/open.rst| 7
This fixes wrongly filled bytesused field of v4l2_plane structure
by include data_offset in the plane, Also fill data_offset and
bytesused for capture type of buffers only.
Signed-off-by: Stanimir Varbanov
---
v2: Just delete pointless WARN_ON.
drivers/media/platform/qcom/venus/venc.c | 7 +++--
On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/uapi/v4l/glossary.rst | 136
> ++
> Docu
Hi Yong,
Thanks for the update! Please see my comments below.
On Fri, Oct 06, 2017 at 06:39:01PM -0500, Yong Zhi wrote:
> This patch adds CIO2 CSI-2 device driver for
> Intel's IPU3 camera sub-system support.
>
> Signed-off-by: Yong Zhi
> Signed-off-by: Hyungwoo Yang
> Signed-off-by: Rajmohan
Marek,
Any comments?
On 08/29/2017 02:26 PM, Stanimir Varbanov wrote:
> Currently videobuf2-dma-sg checks for dma direction for
> every single page and videobuf2-dc lacks any dma direction
> checks and calls set_page_dirty_lock unconditionally.
>
> Thus unify and align the invocations of set_pag
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:
If you try to store u64 in a kfifo (or a struct with u64 members),
then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes
padding due to alignment (note that struct __kfifo is 20 bytes
on 32 bit).
That in turn causes the __is_kfifo_ptr() to fail, which is caught
by kfifo_alloc(), which now r
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:
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 have no lirc device, since they can be controlled
from their /dev/cecN chardev.
Signed-off-by: Sean Young
---
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 | 51 +++---
Documentation/media/uapi/rc/lirc-get-features.rst | 16 ++
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, keycode, toggle and repeat status in addition
to just the scancode.
int main()
{
int fd, mode, rc;
fd = open("/dev/l
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
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 | 27 +--
1 file changed, 17 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_MODES, &mode);
poll(&((struct pollfd){ .fd
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 | 199 -
For some IR protocols, some scancode values not valid, i.e. they're part
of a different protocol variant.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-main.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc/rc-main.c b/drivers/media/rc
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
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
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
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 +++--
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/
Ensure we reject an attempt to transmit invalid scancodes.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 10
drivers/media/rc/rc-core-priv.h | 1 +
drivers/media/rc/rc-main.c | 53 +---
3 files changed, 44 insertions(+), 20
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
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
LIRCCODE is a lirc mode where a driver produces driver-dependent
codes for receive and transmit. No driver uses 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/uap
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
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
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 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
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
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
96 matches
Mail list logo
