Update and expand the CEC documentation. Especially w.r.t. non-blocking mode.
Signed-off-by: Hans Verkuil
---
This depends on https://patchwork.linuxtv.org/patch/35614/.
Changes since v2: update the documentation of the all_device_types and features
fields due to changes
Sakari Ailus wrote:
> I believe people are more familiar with the state of the code with the
> reverts than without them. The first two reverted patches I don't really
> have a problem with, but they depend on the third reverted patch which
> is more problematic and they'll no longer be needed
We cannot build the cec driver when the RC core is a module
and cec is built-in:
drivers/staging/built-in.o: In function `cec_allocate_adapter':
:(.text+0x134): undefined reference to `rc_allocate_device'
drivers/staging/built-in.o: In function `cec_register_adapter':
:(.text+0x304): undefined
staging media drivers tend to have a build time dependency on the
media support. In particular, the newly added pulse8 cec driver can
only be a loadable module if MEDIA_SUPPORT=m, but its build dependency
is on a 'bool' symbol (MEDIA_CEC), so a randconfig build can fail
with pulse8_cec built-in:
Hi
On 2016-07-18 19:54, Vincent Stehlé wrote:
When allocating memory to hold the device dma parameters in
vb2_dma_contig_set_max_seg_size(), the requested size is by mistake only
the size of a pointer. Request the correct size instead.
Fixes: 3f0339691896 ("media: vb2-dma-contig: add helper
Update and expand the CEC documentation. Especially w.r.t. non-blocking mode.
Signed-off-by: Hans Verkuil
---
This depends on https://patchwork.linuxtv.org/patch/35614/.
Changes since v2: better document the timestamp fields
Changes since v1: update the documentation of
Hi Mauro,
Thank you for your reply.
Mauro Carvalho Chehab wrote:
> Em Fri, 15 Jul 2016 01:34:55 +0300
> Sakari Ailus escreveu:
>
>> Hi folks,
>>
>> I've been working on this for some time now but only got the full patchset
>> working some moments ago. The patchset
These patches fix a number of bugs in the CEC framework. These were discovered
while extending and improving the compliance tests for the CEC API.
The vivid patch adds MONITOR_ALL support.
The latest compliance tests are here:
https://git.linuxtv.org/hverkuil/v4l-utils.git/log/?h=cec-johan
The
On Tuesday, July 19, 2016 10:30:22 AM CEST Hans Verkuil wrote:
> On 07/19/16 10:10, Arnd Bergmann wrote:
> > We cannot build the cec driver when the RC core is a module
> > and cec is built-in:
> >
> > drivers/staging/built-in.o: In function `cec_allocate_adapter':
> > :(.text+0x134): undefined
On 07/19/16 10:10, Arnd Bergmann wrote:
> We cannot build the cec driver when the RC core is a module
> and cec is built-in:
>
> drivers/staging/built-in.o: In function `cec_allocate_adapter':
> :(.text+0x134): undefined reference to `rc_allocate_device'
> drivers/staging/built-in.o: In function
On 07/18/16 20:30, Mauro Carvalho Chehab wrote:
> This patch series finally ends the conversion of the media documents to ReST
> format.
>
> After this series, *all* media documentation will be inside a ReST book.
>
> They'll be:
>
> - Linux Media Infrastructure userspace API
> - With 5
drivers/media/platform/rcar_fdp1.c:1972:2: warning: initialization from
incompatible pointer type
.queue_setup = fdp1_queue_setup,
^
drivers/media/platform/rcar_fdp1.c:1972:2: warning: (near initialization
for 'fdp1_qops.queue_setup')
drivers/media/platform/rcar_fdp1.c:
Em Tue, 19 Jul 2016 10:27:47 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Thank you for your reply.
>
> Mauro Carvalho Chehab wrote:
> > Em Fri, 15 Jul 2016 01:34:55 +0300
> > Sakari Ailus escreveu:
> >
> >> Hi folks,
> >>
> >>
Hi all,
This patch adds support for the R-Car MIPI CSI-2 interface. And is based
on top of the media_tree.
Changes since v1:
- Drop dependency on a pad aware s_stream operation.
- Use the DT bindings format "renesas,-", thanks Geert
for pointing this out.
Niklas Söderlund (1):
[media]
A V4L2 driver for Renesas R-Car MIPI CSI-2 interface. The driver
supports the rcar-vin driver on R-Car Gen3 SoCs where a separate driver
is needed to receive CSI-2.
Driver is based on a prototype by Koji Matsuoka in the Renesas BSP.
Signed-off-by: Niklas Söderlund
Am 18.07.2016 um 13:54 schrieb Mauro Carvalho Chehab :
> Em Sun, 17 Jul 2016 20:37:19 -0600
> Jonathan Corbet escreveu:
>
>> [Back home and trying to get going on stuff for real. I'll look at the
>> issues listed in this message one at a time.]
>>
>>
Hi Kieran,
Hmm, I don't think I ever reviewed this one.
So here is my quick review:
General note: I need to see the v4l2-compliance output. Make sure you run
with the latest version from v4l-utils.
On 06/30/16 15:41, Kieran Bingham wrote:
> The FDP1 driver performs advanced de-interlacing on a
From: Wei Yongjun
Add the missing platform_device_del() before return from
lirc_parallel_init() in the error handling case.
Signed-off-by: Wei Yongjun
---
drivers/staging/media/lirc/lirc_parallel.c | 10 ++
1 file changed,
Thanks Geert,
That looks good to me.
I'll fold in to my existing patch.
--
Regards
Kieran
On 19/07/16 12:51, Geert Uytterhoeven wrote:
> drivers/media/platform/rcar_fdp1.c:1972:2: warning: initialization from
> incompatible pointer type
> .queue_setup = fdp1_queue_setup,
> ^
Am 19.07.2016 um 13:12 schrieb Mauro Carvalho Chehab :
> Em Tue, 19 Jul 2016 11:19:11 +0200
> Hans Verkuil escreveu:
>
>>> All those documents are built automatically, once by day, at linuxtv.org:
>>>
>>> uAPI:
>>>
Em Tue, 19 Jul 2016 11:19:11 +0200
Hans Verkuil escreveu:
> > All those documents are built automatically, once by day, at linuxtv.org:
> >
> > uAPI:
> > https://linuxtv.org/downloads/v4l-dvb-apis-new/media/media_uapi.html
>
> Erm, there is nothing there, only the
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-core.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/rcar-vin/Kconfig
This is done to prepare for Gen3 support where there are more than one
subdevice and the usage of them are complex. There is a need to be able
to change which subdevices are involved in capturing during runtime (but
not while streaming). Furthermore the subdevices can be shared by
more then one
Tha ARM randconfig builds came up with another rare build failure
for the dib3000mc driver, when dvb-usb-dibusb-mb is built-in and
dib3000mc is a loadable module:
ERROR: "dibusb_dib3000mc_frontend_attach"
[drivers/media/usb/dvb-usb/dvb-usb-nova-t-usb2.ko] undefined!
ERROR:
Tha ARM randconfig builds came up with another rare build failure
for the dib3000mc driver, when dvb-usb-dibusb-mb is built-in and
dib3000mc is a loadable module:
ERROR: "dibusb_dib3000mc_frontend_attach"
[drivers/media/usb/dvb-usb/dvb-usb-nova-t-usb2.ko] undefined!
ERROR:
Added function to read BER for ISDB-T
Also SNR values fixed for ISDB-T
Signed-off-by: Abylay Ospan
---
drivers/media/dvb-frontends/cxd2841er.c | 48 ++---
1 file changed, 45 insertions(+), 3 deletions(-)
diff --git
Add the register needed to work with Gen3 hardware. This patch just adds
the logic for how to work with the Gen3 hardware. More work is required
to enable the subdevice structure needed to support capturing.
Signed-off-by: Niklas Söderlund
---
Fix a error from the original driver where v4l2_device_call_until_err()
where used for the pad specific v4l2 operation set_fmt. Also fix up the
error path from this fix so if there is an error it will be propagated
to the caller.
The error path label have also been renamed as a result from a
Hi,
This series enable Gen3 support for the rcar-vin driver. It is based on
top of the media_tree.
This is a rather large patch since unfortunately the subdevice and input
selection on Gen3 are much more complex than on Gen2, see individual
patches for a more detailed explanation.
- Patch 1-2
The main purpose of this commit is to make consecutive patches easier to
read. This is achieved with the following changes.
- Rename the variable 'entity' in struct rvin_dev to 'digital'. When we
add Gen3 support later this will only deal with the digital input
source.
- Rename all functions
The original drivers code to find a subdevice by looking in the DT graph
and how the callbacks to the v4l2 async bind framework where poorly
written. The most obvious example of badness was the duplication of data
in the struct rvin_graph_entity.
This patch removes the data duplication,
The primary reason for this change is to prepare for Gen3 support where
there will be more then one possible video source. Each source will have
its own media bus format and code, so it needs to be moved from the per
device structure to a structure used to represent an individual
connection to a
The check for if the specific pixelformat is supported on the current
chip should happen in VIDIOC_S_FMT and VIDIOC_TRY_FMT and not when we
try to setup the hardware for streaming.
Signed-off-by: Niklas Söderlund
---
Em Tue, 19 Jul 2016 14:31:18 +0200
Markus Heiser escreveu:
> > I really hate stupid toolchains that require everybody to upgrade to
> > the very latest version of it every time.
>
> Hi Mauro,
>
> It might be annoying how sphinx handles errors, but normally a build
This is done in preparation for Gen3 support where media controller
support will be mandatory for the driver.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-v4l2.c | 7 +--
2
This is done to prepare for Gen3 support where there are more than one
subdevice and the usage of them are complex and can be shared between
multiple rcar-vin instances. There are a few trouble areas with Gen3
that needs to be solved in order to be able to capture video.
1. There can be up to 4
From: Laurent Pinchart
The optional operation can be used by entities to report whether two
pads are internally connected.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by:
From: Laurent Pinchart
This is a wrapper around the media entity has_route operation.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by: Niklas Söderlund
These are present in the soc-camera version of this driver and it's time
to add them to this driver as well.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
In order to try and separate which v4l2 subdevice operation the driver
calls from which subdevice it currently have chosen as its current input
a abstraction is created. The abstraction is mostly straight forward:
- The v4l2_subdev_call() calls that only can act on the current active
subdevice
Fix a error from the original driver where the wrong error code is
returned if the driver fails to get a IRQ number from
platform_get_irq().
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 2 +-
1 file changed, 1
A recent bugfix to adv7180 brought to light that the rcar-vin driver are
looking for the wrong media bus format. It was looking for a YUVU format
but then expecting UYVY data. The bugfix for adv7180 will break the
usage of rcar-vin together with a adv7180 as found on Renesas R-Car2
Koelsch boards
Em Tue, 19 Jul 2016 11:53:19 -0300
Mauro Carvalho Chehab escreveu:
> Yet, this doesn't solve the specific issue for the TOC index
> name. How this could be done in a way that would be backward
> compatible to 1.2.x?
Answering myself, the following patch should trick
Hi Hans,
Thank you for your comments.
I've started to take them into account.
I've got a question about V4L2_FIELD_ANY in buf_prepare (please see below).
[snip]
>> +static int hva_buf_prepare(struct vb2_buffer *vb)
>> +{
>> + struct hva_ctx *ctx = vb2_get_drv_priv(vb->vb2_queue);
>> +
Document the ir-spi driver's binding which is a IR led driven
through the SPI line.
Signed-off-by: Andi Shyti
---
Documentation/devicetree/bindings/media/spi-ir.txt | 20
1 file changed, 20 insertions(+)
create mode 100644
IR raw transmitter driver type is specified in the enum
rc_driver_type as RC_DRIVER_IR_RAW_TX which includes all those
devices that transmit raw stream of bit to a receiver.
The data are provided by userspace applications, therefore they
don't need any input device allocation, but still they need
Am 19.07.2016 um 16:53 schrieb Mauro Carvalho Chehab :
> Em Tue, 19 Jul 2016 14:31:18 +0200
> Markus Heiser escreveu:
>
>
>>> I really hate stupid toolchains that require everybody to upgrade to
>>> the very latest version of it every time.
Hello.
On 07/19/2016 05:20 PM, Niklas Söderlund wrote:
Fix a error from the original driver where the wrong error code is
returned if the driver fails to get a IRQ number from
platform_get_irq().
Signed-off-by: Niklas Söderlund
---
Hi,
this is an RFCset that follows this patch:
http://marc.info/?l=linux-kernel=146736225606125=2
and after Sean's review and recommendations:
http://marc.info/?l=linux-kernel=146737935611128=2
The main goal is to add support in the rc framework for IR
transmitters, which currently is only
Move the input device allocation, map and protocol handling to
different functions.
Signed-off-by: Andi Shyti
---
drivers/media/rc/rc-main.c | 140 +
1 file changed, 77 insertions(+), 63 deletions(-)
diff --git
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through a character device. The chardev is
handled by the LIRC framework and its
Raw transmitters receive the data which need to be sent to
receivers from userspace as stream of bits, they don't require
any handling from the lirc framework.
Signed-off-by: Andi Shyti
---
drivers/media/rc/ir-lirc-codec.c | 30 +++---
1 file
The driver type can be assigned immediately when an RC device
requests to the framework to allocate the device.
This is an 'enum rc_driver_type' data type and specifies whether
the device is a raw receiver or scancode receiver. The type will
be given as parameter to the rc_allocate_device device.
Hi Hans,
On Mon, 2016-07-18 at 14:44 +0200, Hans Verkuil wrote:
> On 07/18/2016 02:28 PM, tiffany lin wrote:
> > Understood now.
> >
> > Now I am trying to figure out how to make this function right.
> > Our encoder only support crop range from (0, 0) to (width, height), so
> > if s->r.top and
Raw IR transmitters do not need any thread listening for
occurring events. Check the driver type before running the
thread.
Signed-off-by: Andi Shyti
---
drivers/media/rc/rc-ir-raw.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git
On 07/19/2016 05:55 PM, Jean Christophe TROTIN wrote:
> Hi Hans,
>
> Thank you for your comments.
> I've started to take them into account.
> I've got a question about V4L2_FIELD_ANY in buf_prepare (please see below).
>
> [snip]
>
> >> +static int hva_buf_prepare(struct vb2_buffer *vb)
> >>
From: Markus Elfring
Date: Tue, 19 Jul 2016 19:54:16 +0200
The spi_unregister_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Em Tue, 19 Jul 2016 18:42:50 +0200
Markus Heiser escreveu:
> > What we miss is the documentation for Sphinx 1.2 and 1.3 versions. The
> > site only has documentation for the very latest version, making harder
> > to ensure that we're using only the tags supported by a
Am 19.07.2016 20:02, schrieb SF Markus Elfring:
> From: Markus Elfring
> Date: Tue, 19 Jul 2016 19:54:16 +0200
>
> The spi_unregister_device() function tests whether its argument is NULL
> and then returns immediately. Thus the test around the call is not needed.
Em Tue, 19 Jul 2016 17:16:35 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 3) When there's an asterisk inside the source code, for example, to
> > document a pointer, or when something else
Em Tue, 19 Jul 2016 17:01:33 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 2) For functions, kernel-doc is now an all or nothing. If not all
> > functions are declared, it outputs this
Am 20.07.2016 um 00:58 schrieb Jonathan Corbet :
> On Tue, 19 Jul 2016 12:00:24 +0200
> Markus Heiser wrote:
>
>> I recommend to consider to switch to the python version of the parser.
>> I know, that there is a natural shyness about a
On Wed, Jul 20, 2016 at 12:56:58AM +0900, Andi Shyti wrote:
> The ir-spi is a simple device driver which supports the
> connection between an IR LED and the MOSI line of an SPI device.
>
> The driver, indeed, uses the SPI framework to stream the raw data
> provided by userspace through a
Replace hard-coded addresses with new register macro defines. No
functional changes.
Signed-off-by: Steve Longerbeam
---
drivers/media/i2c/adv7180.c | 73 ++---
1 file changed, 49 insertions(+), 24 deletions(-)
diff --git
Parse the optional v4l2 endpoint DT node. If the V4L2_MBUS_NEWAVMODE
parallel bus flag is set, configure the BT.656 bus in NEWAVMODE.
Signed-off-by: Steve Longerbeam
---
drivers/media/i2c/adv7180.c | 47 ++---
1 file changed,
Enable the SD lock/unlock interrupts and send V4L2_EVENT_SRC_CH_LOCK_STATUS
in the interrupt handler on a detected lock/unlock.
Signed-off-by: Steve Longerbeam
---
v2:
- last version of this patch was based on the old reverted autodetect
code. This version now
This patch adds a "newavmode" boolean property as part of the v4l2 endpoint
properties. This indicates an Analog Devices decoder is generating EAV/SAV
codes to suit Analog Devices encoders.
Signed-off-by: Steve Longerbeam
Cc: Mauro Carvalho Chehab
This version adds a new v4l2 endpoint property and BT.656 bus flag
for the "NEWAVMODE" setting of Analog Devices decoders. The i.MX6
capture backend is not able to sync on the bt.656 stream from the
ADV7180 when the latter is in manual video standard setting mode,
unless NEWWAVMODE is used in
The ADV7180 and ADV7182 transmit whole fields, bottom field followed
by top (or vice-versa, depending on detected video standard). So
for chips that do not have support for explicitly setting the field
mode, set the field mode to SEQ_BT for PAL, and SEQ_TB for NTSC (there
seems to be conflicting
Em Tue, 19 Jul 2016 16:49:16 -0600
Jonathan Corbet escreveu:
> On Tue, 19 Jul 2016 11:53:19 -0300
> Mauro Carvalho Chehab wrote:
>
> > So, I guess we should set the minimal requirement to 1.2.x.
>
> *sigh*.
>
> I hate to do that; things are
Add a signal lock status change to the source changes bitmask.
This indicates there was a signal lock or unlock event detected
at the input of a video decoder.
Signed-off-by: Steve Longerbeam
Cc: Mauro Carvalho Chehab
---
Change the media bus format from YUYV8_2X8 to UYVY8_2X8. Colors
now look correct when capturing with the i.mx6 backend.
Signed-off-by: Steve Longerbeam
Tested-by: Tim Harvey
Acked-by: Tim Harvey
Acked-by: Lars-Peter
Some targets control the ADV7180 power pin via a gpio, so add
optional support for "powerdown" pin control.
Signed-off-by: Steve Longerbeam
Tested-by: Tim Harvey
Acked-by: Tim Harvey
Cc: Lars-Peter Clausen
Implement g_parm to return the current standard's frame period.
Signed-off-by: Steve Longerbeam
Tested-by: Tim Harvey
Acked-by: Tim Harvey
---
drivers/media/i2c/adv7180.c | 22 ++
1 file changed, 22
Access to the interrupt page registers has been broken since at least
commit 3999e5d01da7 ("[media] adv7180: Do implicit register paging").
That commit forgot to add the interrupt page number to the register
defines.
Signed-off-by: Steve Longerbeam
Tested-by: Tim
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 Jul 20 04:00:18 CEST 2016
git branch: test
git hash: 009a620848218d521f008141c62f56bf19294dd9
gcc
Em Tue, 19 Jul 2016 17:30:24 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 4) There are now several errors when parsing functions. Those seems to
> > happen when an argument is a function
Hi,
On Tue, Jul 19, 2016 at 11:21:17PM +0300, mat...@sai.msu.ru wrote:
> Hello,
>
> I have Philips SPC 900 camera (0471:0329) connected to my AM335x based
> BeagleBoneBlack SBC.
> I am sure that both of them are fine and work properly.
> I am running Linux 4.6.4 (my kernel config is available
2016-07-19 23:56 GMT+03:00 Bin Liu :
> Hi,
>
> On Tue, Jul 19, 2016 at 11:21:17PM +0300, mat...@sai.msu.ru wrote:
>> Hello,
>>
>> I have Philips SPC 900 camera (0471:0329) connected to my AM335x based
>> BeagleBoneBlack SBC.
>> I am sure that both of them are fine and work properly.
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 4) There are now several errors when parsing functions. Those seems to
> happen when an argument is a function pointer, like:
>
> /devel/v4l/patchwork/Documentation/media/kapi/v4l2-core.rst:757: WARNING:
On Tue, 19 Jul 2016 11:53:19 -0300
Mauro Carvalho Chehab wrote:
> So, I guess we should set the minimal requirement to 1.2.x.
*sigh*.
I hate to do that; things are happening quickly enough with Sphinx that
it would be nice to be able to count on a newer version. That
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 2) For functions, kernel-doc is now an all or nothing. If not all
> functions are declared, it outputs this warning:
>
> ./include/media/media-devnode.h:1: warning: no structured comments
>
> And
Hello,
I have Philips SPC 900 camera (0471:0329) connected to my AM335x based
BeagleBoneBlack SBC.
I am sure that both of them are fine and work properly.
I am running Linux 4.6.4 (my kernel config is available at
https://clck.ru/A2kQs ) and I've just discovered, that there is an issue with
On Tue, 19 Jul 2016 12:00:24 +0200
Markus Heiser wrote:
> I recommend to consider to switch to the python version of the parser.
> I know, that there is a natural shyness about a reimplementation in python
> and thats why I offer to support it for a long time period ..
Hi,
On Wed, Jul 20, 2016 at 12:25:44AM +0300, Matwey V. Kornilov wrote:
> 2016-07-19 23:56 GMT+03:00 Bin Liu :
> > Hi,
> >
> > On Tue, Jul 19, 2016 at 11:21:17PM +0300, mat...@sai.msu.ru wrote:
> >> Hello,
> >>
> >> I have Philips SPC 900 camera (0471:0329) connected to my AM335x
On Wed, Jul 20, 2016 at 12:56:52AM +0900, Andi Shyti wrote:
> The driver type can be assigned immediately when an RC device
> requests to the framework to allocate the device.
>
> This is an 'enum rc_driver_type' data type and specifies whether
> the device is a raw receiver or scancode receiver.
On Wed, Jul 20, 2016 at 12:56:54AM +0900, Andi Shyti wrote:
> IR raw transmitter driver type is specified in the enum
> rc_driver_type as RC_DRIVER_IR_RAW_TX which includes all those
> devices that transmit raw stream of bit to a receiver.
>
> The data are provided by userspace applications,
On Wed, Jul 20, 2016 at 12:56:56AM +0900, Andi Shyti wrote:
> Raw transmitters receive the data which need to be sent to
> receivers from userspace as stream of bits, they don't require
> any handling from the lirc framework.
No drivers of type RC_DRIVER_IR_RAW_TX should handle tx just like any
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 3) When there's an asterisk inside the source code, for example, to
> document a pointer, or when something else fails when parsing a
> header file, kernel-doc handler just outputs:
>
Am 20.07.2016 um 02:09 schrieb Mauro Carvalho Chehab :
> Em Tue, 19 Jul 2016 17:16:35 -0600
> Jonathan Corbet escreveu:
>
>> On Sun, 17 Jul 2016 10:01:54 -0300
>> Mauro Carvalho Chehab wrote:
>>
>>> 3) When there's an
From: Markus Elfring
Date: Tue, 19 Jul 2016 21:24:26 +0200
The video_unregister_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle
When my system (with last upstream kernel) goes into suspend (hybrid-sleep
with systemd), I get sometimes (around every third to fifth time) a system
freeze, when systemd removes the modules cx23885 cx25840 for my DVB-C/T card
DVBSky T982. The modules are not used at the moment (e.g. by
92 matches
Mail list logo