Additionally, now it specifies which channels it's showing.
Signed-off-by: Ismael Luceno
---
drivers/media/pci/solo6x10/solo6x10-v4l2.c | 27 +--
1 file changed, 9 insertions(+), 18 deletions(-)
diff --git a/drivers/media/pci/solo6x10/solo6x10-v4l2.c
Such frame size is met in practice. Also report oversized frames.
Based on patches by Andrey Utkin .
Signed-off-by: Ismael Luceno
---
drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c | 7 +--
1 file changed, 5 insertions(+), 2
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: Sat Apr 30 04:00:17 CEST 2016
git branch: test
git hash: 45c175c4ae9695d6d2f30a45ab7f3866cfac184b
gcc
Hi, Satoshi,
just some small comments about tuners/qm1d1c0042...
> --- a/drivers/media/tuners/qm1d1c0042.c
> +++ b/drivers/media/tuners/qm1d1c0042.c
> @@ -32,14 +32,23 @@
> #include "qm1d1c0042.h"
>
> #define QM1D1C0042_NUM_REGS 0x20
> -
> -static const u8 reg_initval[QM1D1C0042_NUM_REGS] = {
Hi,
On 30.04.2016 01:20, Pali Rohár wrote:
On Saturday 30 April 2016 00:13:59 Pavel Machek wrote:
Any other application I should look at? Thanks,
Maybe camera-ui, which is part of CSSU?
https://github.com/community-ssu/camera-ui
This is based on gdigicam, are you sure it is compatible
When driver unbinds while media_ioctl is in progress, cdev_put() fails with
when app exits after driver unbinds.
Add a kobject to the media_devnode structure and set this kobject as the
cdev parent kobject. This allows cdev_add() to hold a reference to it and
release the reference in cdev_del()
On Saturday 30 April 2016 00:13:59 Pavel Machek wrote:
> Any other application I should look at? Thanks,
Maybe camera-ui, which is part of CSSU?
https://github.com/community-ssu/camera-ui
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
Hi!
What is reasonable camera application for testing?
N900 looks like a low-end digital camera. I have now have the hardware
working (can set focus to X cm using command line), but that's not
going to be useful for taking photos.
In particular, who is going to do computation neccessary for
Hi!
> "5. DT Bindings for flash & lens controllers
>
> There are drivers that create their MC topology using the device tree
> information,
> which works great for entities that transport data, but how to detect entities
> that don’t transport data such as flash devices, focusers, etc.? How can
Hi,
On 29.04.2016 20:45, Sebastian Reichel wrote:
Hi,
On Fri, Apr 29, 2016 at 02:05:52AM +0200, Sebastian Reichel wrote:
On Wed, Apr 27, 2016 at 08:12:50PM +0300, Ивайло Димитров wrote:
The zImage + initrd works with the steps you described below.
Great!
I also got it working with the
Hi,
On Fri, Apr 29, 2016 at 02:05:52AM +0200, Sebastian Reichel wrote:
> On Wed, Apr 27, 2016 at 08:12:50PM +0300, Ивайло Димитров wrote:
> > > The zImage + initrd works with the steps you described below.
> >
> > Great!
>
> I also got it working with the previously referenced branch with the
>
On 04/28/2016 01:19 AM, Lars-Peter Clausen wrote:
> On 04/27/2016 11:56 PM, Shuah Khan wrote:
dev_dbg(mdev->dev, "Media device unregistered\n");
}
diff --git a/drivers/media/media-devnode.c b/drivers/media/media-devnode.c
index 29409f4..9af9ba1 100644
---
Hi Mauro, Akihiro,
I resend the same patch except that no credit info of mine is added
because of not rewriting a significant amount of the driver.
I got some reports that this patch works well on PX-BCUD and PT3, those are
the all devices can be affected by this patch.
--
I added em28xx_dvb to
Hi!
> > > This seems to be mostly in line with what has been discussed in the
> > > meeting,
> > > except that the patches add a device specific property. Please ignore the
> > > led patches in that tree for now (i.e. four patches on the top are the
> > > relevant ones here).
> > >
> >
> > I'm
Hi Marek,
On Fri, Apr 29, 2016 at 01:39:43PM +0200, Marek Szyprowski wrote:
> Hi Sakari,
>
>
> On 2016-04-29 13:21, Sakari Ailus wrote:
> >Hi Marek,
> >
> >Thanks for the patch!
> >
> >On Thu, Apr 28, 2016 at 03:20:03PM +0200, Marek Szyprowski wrote:
> >>This patch lets vb2-dma-contig memory
Hi Mauro,
Here is the pull request for the HDMI CEC framework. The code of this pull
request is identical to the v16 patch series:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg97057.html
The pull request is for 4.7, but I am aware that it is likely that it will
slide to 4.8 since
From: Hans Verkuil
The vivid driver has been extended to provide CEC adapters for the HDMI
input and HDMI outputs in order to test CEC applications.
This CEC emulation is faithful to the CEC timings (i.e., it all at a
snail's pace).
Signed-off-by: Hans Verkuil
From: Hans Verkuil
Add CEC support to the adv7604 driver.
Signed-off-by: Hans Verkuil
[k.deb...@samsung.com: Merged changes from CEC Updates commit by Hans Verkuil]
[k.deb...@samsung.com: add missing methods cec/io_write_and_or]
From: Hans Verkuil
Document the new HDMI CEC framework.
Signed-off-by: Hans Verkuil
[k.deb...@samsung.com: add DocBook documentation by Hans Verkuil, with
Signed-off-by: Kamil Debski
Signed-off-by: Hans Verkuil
From: Kamil Debski
Add CEC interface driver present in the Samsung Exynos range of
SoCs.
The following files were based on work by SangPil Moon:
- exynos_hdmi_cec.h
- exynos_hdmi_cecctl.c
Signed-off-by: Kamil Debski
Signed-off-by: Hans Verkuil
From: Hans Verkuil
Add CEC support to the adv7511 driver.
Signed-off-by: Hans Verkuil
[k.deb...@samsung.com: Merged changes from CEC Updates commit by Hans Verkuil]
Signed-off-by: Kamil Debski
Signed-off-by: Hans Verkuil
From: Hans Verkuil
Explain why cec.c is still in staging.
Signed-off-by: Hans Verkuil
---
drivers/staging/media/cec/TODO | 13 +
1 file changed, 13 insertions(+)
create mode 100644 drivers/staging/media/cec/TODO
diff --git
From: Hans Verkuil
Add CEC support to the adv7842 driver.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/Kconfig | 9 ++
drivers/media/i2c/adv7842.c | 368
2 files changed, 314 insertions(+),
From: Hans Verkuil
Add DocBook documentation for the CEC API.
Signed-off-by: Hans Verkuil
[k.deb...@samsung.com: add documentation for passthrough mode]
[k.deb...@samsung.com: minor fixes and change of reserved field sizes]
Signed-off-by: Kamil
From: Hans Verkuil
Hi all,
The sixteenth version of this patchset does some final cleanup and
I'll post a pull request on the linux-media list for this patch series.
At first I didn't want to post a v16 at all, but there were just a bit
too many changes, even though
From: Kamil Debski
Add HDMI CEC specific keycodes to the keycodes definition.
Signed-off-by: Kamil Debski
Signed-off-by: Hans Verkuil
Acked-by: Dmitry Torokhov
---
include/uapi/linux/input-event-codes.h |
From: Hans Verkuil
The CEC ioctls didn't have compat32 support, so they returned -ENOTTY
when used in a 32 bit application on a 64 bit kernel.
Since all the CEC ioctls are 32-bit compatible adding support for this
API is trivial.
Signed-off-by: Hans Verkuil
From: Kamil Debski
Add handling of remote control events coming from the HDMI CEC bus.
This patch includes a new keymap that maps values found in the CEC
messages to the keys pressed and released. Also, a new protocol has
been added to the core.
Signed-off-by: Kamil Debski
From: Hans Verkuil
Inputs can come in over the HDMI CEC bus, so add a new type for this.
Signed-off-by: Hans Verkuil
Acked-by: Dmitry Torokhov
---
include/uapi/linux/input.h | 1 +
1 file changed, 1 insertion(+)
diff
On Mon 2016-04-25 00:08:12, Ivaylo Dimitrov wrote:
> From: Sakari Ailus
>
> Document the CSI1/CCP2 properties strobe_clk_inv and strobe_clock
> properties. The former tells whether the strobe/clock signal is inverted,
> while the latter signifies the clock or strobe mode.
>
On Mon 2016-04-25 00:08:11, Ivaylo Dimitrov wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s) since
> a receiver or transmitter can only support a single one. There are cases
> however where different options are possible.
>
On Mon 2016-04-25 00:08:09, Ivaylo Dimitrov wrote:
> From: Sakari Ailus
>
> CCP2, or CSI-1, is an older single data lane serial bus.
>
> Signed-off-by: Sakari Ailus
Acked-by: Pavel Machek
--
(english)
On Mon 2016-04-25 00:08:07, Ivaylo Dimitrov wrote:
> From: Sakari Ailus
>
> The function to parse CSI2 bus parameters was called
> v4l2_of_parse_csi_bus(), rename it as v4l2_of_parse_csi2_bus() in
> anticipation of CSI1/CCP2 support.
>
> Signed-off-by: Sakari Ailus
With the new dma_request_chan() the client driver does not need to look for
the DMA resource and it does not need to pass filter_fn anymore.
By switching to the new API the driver can now support deferred probing
against DMA.
Signed-off-by: Peter Ujfalusi
CC: Laurent
On 22/04/2016 16:44, Mauro Carvalho Chehab wrote:
>> On the other hand, it would be a good place to tell the user that it
>> is from a touch sensor.
>>
>> Using the upcoming metadata feature wouldn't work since there is no width
>> and height in the metadata format.
>>
>> I wonder what others
Hi, Hans!
On Fri, Apr 22, 2016 at 11:06:57AM +0200, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Both in videodev2.h and in the documentation there are a lot of features
> marked 'experimental' that have been around for years. Remove these
> annotations since it was pure
On Thu, Apr 28, 2016 at 7:33 AM, Stanimir Varbanov
wrote:
> On 04/15/2016 07:09 PM, Nicolas Dufresne wrote:
>> Le vendredi 15 avril 2016 à 11:58 -0400, Rob Clark a écrit :
>>> The issue is probably the YUV format, which we cannot really deal
>>> with
>>> properly in
Hi Sakari,
On 2016-04-29 13:21, Sakari Ailus wrote:
Hi Marek,
Thanks for the patch!
On Thu, Apr 28, 2016 at 03:20:03PM +0200, Marek Szyprowski wrote:
This patch lets vb2-dma-contig memory allocator to configure DMA max
segment size properly for the client device. Setting it is needed to let
On Fri, Apr 29, 2016 at 01:05:46PM +0200, Pali Rohár wrote:
> On Friday 29 April 2016 13:59:44 Sakari Ailus wrote:
> > > pavel@amd:/data/l/linux-n900$ git fetch
> > > git://git.retiisi.org.uk/~sailus/linux.git leds-as3645a:leds-as3645a
> > > fatal: unable to connect to git.retiisi.org.uk:
> > >
Hi Marek,
Thanks for the patch!
On Thu, Apr 28, 2016 at 03:20:03PM +0200, Marek Szyprowski wrote:
> This patch lets vb2-dma-contig memory allocator to configure DMA max
> segment size properly for the client device. Setting it is needed to let
> DMA-mapping subsystem to create a single,
Hi Tiffany,
On 04/26/2016 10:58 AM, Tiffany Lin wrote:
> ==
> Introduction
> ==
>
> The purpose of this series is to add the driver for video codec hw embedded
> in the Mediatek's MT8173 SoCs.
> Mediatek Video Codec is able to handle video encoding of in a range of
>
Em Wed, 27 Apr 2016 15:01:31 -0300
Helen Koike escreveu:
> Hi Mauro,
>
> Please pull the following patches correcting the returned error codes
> and respective docs in the pipeline validation.
>
> Regards,
> Helen
>
> The following changes since commit
On Friday 29 April 2016 13:59:44 Sakari Ailus wrote:
> > pavel@amd:/data/l/linux-n900$ git fetch
> > git://git.retiisi.org.uk/~sailus/linux.git leds-as3645a:leds-as3645a
> > fatal: unable to connect to git.retiisi.org.uk:
> > git.retiisi.org.uk: Name or service not known
> >
> >
Hi Pavel,
On Fri, Apr 29, 2016 at 11:50:02AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > adp1653 registers itself as a subdev, but there's no device that
> > > > register it as its part.
> > > >
> > > > (ad5820 driver seems to have the same problem).
> > > >
> > > > Is there example "dummy"
Hi Mauro,
This adds the new non-soc-camera rcar-vin driver, deprecating the older driver.
Tested with my Koelsch board.
This patch just marks the old driver as DEPRECATED.
I am unsure what is better:
1) just mark as DEPRECATED and remove it in the next kernel
2) move it to
Hi!
> > Warning: I'm no DT expert, so this is just a first attempt.
> >
> > Platform drivers (omap3isp) will have to add these controller devices to
> > the list
> > of subdevs to load asynchronously.
>
> I seem to have patches I haven't had time to push back then:
>
>
Hi!
> > > adp1653 registers itself as a subdev, but there's no device that
> > > register it as its part.
> > >
> > > (ad5820 driver seems to have the same problem).
> > >
> > > Is there example "dummy" device I could use, for sole purpose of
> > > having these devices appear in /dev? They are
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
arch/arm/boot/dts/omap4-panda-a4.dts | 2 +-
arch/arm/boot/dts/omap4-panda-es.dts | 2 +-
arch/arm/boot/dts/omap4.dtsi | 5 +-
drivers/gpu/drm/omapdrm/dss/Kconfig| 8 +
From: Tomi Valkeinen
hdmi_core_powerdown_disable() is supposed to disable HDMI core's
power-down mode. However, the function sets the power-down bit to 0,
which means "enable power-down".
This hasn't caused any issues as the PD seems to affect only interrupts
from HDMI
From: Hans Verkuil
As long as there is a valid physical address in the EDID and the omap
CEC support is enabled, then we keep ls_oe_gpio on to ensure the CEC
signal is passed through the tpd12s015.
Signed-off-by: Hans Verkuil
Suggested-by: Tomi
From: Hans Verkuil
This patch series sits on top of my earlier HDMI CEC framework:
http://www.spinics.net/lists/linux-media/msg99847.html
It is an RFC patch for now as I want to clean up hdmi_cec a bit more
and do a bit more testing.
Many thanks to Tomi for finding
cc: mesa-dev ML
On 04/28/2016 02:33 PM, Stanimir Varbanov wrote:
> On 04/15/2016 07:09 PM, Nicolas Dufresne wrote:
>> Le vendredi 15 avril 2016 à 11:58 -0400, Rob Clark a écrit :
>>> The issue is probably the YUV format, which we cannot really deal
>>> with
>>> properly in gallium.. it's a
On 2016-04-29 09:16, Wolfram Sang wrote:
>> Yes, obviously... I'll make that change locally and wait for the rest.
> Another nit: You could use '--strict' with checkpatch and see if you
> want to fix the issues reported. I am not keen on those (except for
> 'space around operators'), it's a matter
Refactor copying the IOCTL argument structs from the user space and back,
in order to reduce code copied around and make the implementation more
robust.
As a result, the copying is done while not holding the graph mutex.
Signed-off-by: Sakari Ailus
---
A number of years ago when someone (read: Laurent) added a new IOCTL to
the MC interface, I wanted IOCTL handling to be refactored. That wasn't
done however, so here are patches to do just that: there are too many
IOCTLs that copy the argument struct from the user and back.
The changes will also
Replace the switch by a nice array of supported IOCTLs, just like in V4L2.
Signed-off-by: Sakari Ailus
---
drivers/media/media-device.c | 58 +++-
1 file changed, 19 insertions(+), 39 deletions(-)
diff --git
Preparation for refactoring media IOCTL handling to unify common parts.
Signed-off-by: Sakari Ailus
---
drivers/media/media-device.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/media/media-device.c b/drivers/media/media-device.c
Hi Hans and Pavel,
On Fri, Apr 29, 2016 at 09:31:51AM +0200, Hans Verkuil wrote:
> On 04/29/2016 09:15 AM, Pavel Machek wrote:
> > Hi!
> >
> >> On n900, probe finishes ok (verified by adding printks), and the
> >> device shows up in /sys, but I don't get /dev/video* or
> >> /dev/v4l-subdev*.
>
Hi Ivaylo,
On Mon, Apr 25, 2016 at 07:32:50PM +0300, Ivaylo Dimitrov wrote:
> Hi,
>
> On 25.04.2016 16:25, Sakari Ailus wrote:
> >Hi Ivaylo,
> >
> >Thanks for the set!
> >
> >On Mon, Apr 25, 2016 at 12:08:01AM +0300, Ivaylo Dimitrov wrote:
> >>From: "Tuukka.O Toivonen"
On 04/29/2016 09:15 AM, Pavel Machek wrote:
> Hi!
>
>> On n900, probe finishes ok (verified by adding printks), and the
>> device shows up in /sys, but I don't get /dev/video* or
>> /dev/v4l-subdev*.
>>
>> Other drivers (back and front camera) load ok, and actually work. Any
>> idea what could
> Yes, obviously... I'll make that change locally and wait for the rest.
Another nit: You could use '--strict' with checkpatch and see if you
want to fix the issues reported. I am not keen on those (except for
'space around operators'), it's a matter of taste I guess, but maybe you
like some of
Hi!
> On n900, probe finishes ok (verified by adding printks), and the
> device shows up in /sys, but I don't get /dev/video* or
> /dev/v4l-subdev*.
>
> Other drivers (back and front camera) load ok, and actually work. Any
> idea what could be wrong?
Ok, so I guess I realized what is the
> So, I think all is ok, or do you need more than Tested-by?
I think this will do. Thanks!
signature.asc
Description: PGP signature
63 matches
Mail list logo