> 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
On 2016-04-28 23:47, Wolfram Sang wrote:
> On Wed, Apr 20, 2016 at 05:18:02PM +0200, Peter Rosin wrote:
>> The root i2c adapter lock is then no longer held by the i2c mux during
>> accesses behind the i2c gate, and such accesses need to take that lock
>> just like any other ordinary i2c accesses do
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 Apr 29 04:00:20 CEST 2016
git branch: test
git hash: 45c175c4ae9695d6d2f30a45ab7f3866cfac184b
gcc versi
Hi Ivo,
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
following built as modules:
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=
On Wed, Apr 20, 2016 at 05:18:02PM +0200, Peter Rosin wrote:
> The root i2c adapter lock is then no longer held by the i2c mux during
> accesses behind the i2c gate, and such accesses need to take that lock
> just like any other ordinary i2c accesses do.
>
> So, declare the i2c gate mux-locked, an
* Ivaylo Dimitrov [160428 14:21]:
>
> I didn't test legacy boot, as I don't really see any value of doing it now
> the end of the legacy boot is near, the driver does not function correctly,
> however the patchset at least allows for the driver to be build and we have
> something to improve on. A
Hi,
On 27.04.2016 02:51, Tony Lindgren wrote:
Hi all,
Here are minimal fixes to get ir-rx51 going again. Then further
fixes can be done as noted in the second patch.
Regards,
Tony
Tony Lindgren (2):
ARM: OMAP2+: Add more functions to pwm pdata for ir-rx51
[media] ir-rx51: Fix build af
On 2016-04-28 22:50, Wolfram Sang wrote:
> On Wed, Apr 20, 2016 at 05:17:56PM +0200, Peter Rosin wrote:
>> Add i2c_lock_bus() and i2c_unlock_bus(), which call the new lock_bus and
>> unlock_bus ops in the adapter. These funcs/ops take an additional flags
>> argument that indicates for what purpos
* Ivaylo Dimitrov [160428 13:44]:
> Хи,
>
> On 28.04.2016 23:22, Tony Lindgren wrote:
> >* Ivaylo Dimitrov [160428 12:39]:
> >>On 27.04.2016 02:51, Tony Lindgren wrote:
> >>
> >>omap_dm_timer_request_specific always fails with message "Please use
> >>omap_dm_timer_request_by_cap/node()" with DT
On Wed, Apr 20, 2016 at 05:17:56PM +0200, Peter Rosin wrote:
> Add i2c_lock_bus() and i2c_unlock_bus(), which call the new lock_bus and
> unlock_bus ops in the adapter. These funcs/ops take an additional flags
> argument that indicates for what purpose the adapter is locked.
>
> There are two flag
Хи,
On 28.04.2016 23:22, Tony Lindgren wrote:
* Ivaylo Dimitrov [160428 12:39]:
On 27.04.2016 02:51, Tony Lindgren wrote:
omap_dm_timer_request_specific always fails with message "Please use
omap_dm_timer_request_by_cap/node()" with DT boot.
I hacked the code to use omap_dm_timer_request_by_
* Ivaylo Dimitrov [160428 12:39]:
> On 27.04.2016 02:51, Tony Lindgren wrote:
>
> omap_dm_timer_request_specific always fails with message "Please use
> omap_dm_timer_request_by_cap/node()" with DT boot.
>
> I hacked the code to use omap_dm_timer_request_by_cap(OMAP_TIMER_HAS_PWM)
> and it seems
Hi,
On 27.04.2016 02:51, Tony Lindgren wrote:
The ir-rx51 driver for n900 has been disabled since the multiarch
changes as plat include directory no longer is SoC specific.
Let's fix it with minimal changes to pass the dmtimer calls in
pdata. Then the following changes can be done while things
Shuah,
Em Thu, 28 Apr 2016 10:23:10 -0600
Shuah Khan escreveu:
> >>> I'm running it today with the stress test. So far (~100 unbind loops,
> >>> with 5
> >>> concurrent accesses via mc_nextgen_test), the only issue it got so
> >>> far seems to be at V4L2 cdev stuff (not at the media side, but a
Hello,
Here my second patch version about GS serializer.
It should be easy to add support for GS1582 and GS1572.
I am not sure about V4L2 interfaces to set/get timings.
I tested with GS1662 component and v4l2-dbg and v4l2-ctl tools.
But this component family support CEA standards and other
(SMPTE
Hi Mauro,
On 04/28/2016 09:04 AM, Mauro Carvalho Chehab wrote:
> Em Thu, 28 Apr 2016 08:50:59 -0600
> Shuah Khan escreveu:
>
>> On 04/28/2016 05:41 AM, Mauro Carvalho Chehab wrote:
>>> Em Wed, 27 Apr 2016 16:20:56 -0600
>>> Shuah Khan escreveu:
>>>
On 03/24/2016 05:37 AM, Mauro Carvalho
My name is Barr. Martin William and i am writing to you about the death of
my late client whom I believe to be one of your relatives and some
fund($US9,500,000,00)he left behind before his death. And I want you to
stand as his next of kin since you have the same surname with him and claim
this mone
My name is Barr. Martin William and i am writing to you about the death of
my late client whom I believe to be one of your relatives and some
fund($US9,500,000,00)he left behind before his death. And I want you to
stand as his next of kin since you have the same surname with him and claim
this mone
Em Thu, 28 Apr 2016 08:50:59 -0600
Shuah Khan escreveu:
> On 04/28/2016 05:41 AM, Mauro Carvalho Chehab wrote:
> > Em Wed, 27 Apr 2016 16:20:56 -0600
> > Shuah Khan escreveu:
> >
> >> On 03/24/2016 05:37 AM, Mauro Carvalho Chehab wrote:
> >>> Em Thu, 24 Mar 2016 10:24:44 +0200
> >>> Laurent
On 04/28/2016 05:41 AM, Mauro Carvalho Chehab wrote:
> Em Wed, 27 Apr 2016 16:20:56 -0600
> Shuah Khan escreveu:
>
>> On 03/24/2016 05:37 AM, Mauro Carvalho Chehab wrote:
>>> Em Thu, 24 Mar 2016 10:24:44 +0200
>>> Laurent Pinchart escreveu:
>>>
On Wednesday 23 Mar 2016 16:27:46 Mauro Car
Hi Olli,
I've checked if the chip is M88DS3103 and it is not DS3103, but
DS3002b. LinuxTV says it's just like DS3000 and I've seen that the
TeVii S471 also uses that demodulator.
I've tried just to use the code used by TeVii S471, but then ds3000 says
something like:
* Invalid probe, probably not
Hi Linux,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.6-4
For some regression fixes:
- videobuf2 core: avoid the risk of going past buffer on multi-planes
and fix rw mode;
- fix support for 4K formats at V4L2 core;
- fix a trouble at davi
On 04/28/2016 03:39 PM, Marek Szyprowski wrote:
> Hello,
>
>
> On 2016-04-28 15:29, Hans Verkuil wrote:
>> On 04/28/2016 03:20 PM, 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 need
Hello,
On 2016-04-28 15:29, Hans Verkuil wrote:
On 04/28/2016 03:20 PM, 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, contiguous map
On 04/28/2016 03:20 PM, 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, contiguous mapping in DMA
> address space. This is essential
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, contiguous mapping in DMA
address space. This is essential for all devices, which use dma-contig
videobuf2 memory a
Hi Marek,
Looks good, just a typo and a large sprinkling of extra 'the' in the text :-)
On 04/28/2016 02:12 PM, 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 s
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, contiguous mapping in DMA
address space. This is essential for all devices, which use dma-contig
videobuf2 memory a
Em Wed, 27 Apr 2016 07:51:08 -0600
Shuah Khan escreveu:
> > - cdev patch;
> > - kref patch.
> >
> > As a bonus side, by breaking into that, it helps to identify what
> > fixes are needed if we found similar issues at the other parts of
> > the subsystems.
>
> No problem breaking the it into 3
Em Wed, 27 Apr 2016 15:56:33 -0600
Shuah Khan escreveu:
> On 04/27/2016 10:43 AM, Lars-Peter Clausen wrote:
> > Looks mostly good, a few comments.
> >
> > On 04/27/2016 05:08 AM, Shuah Khan wrote:
> > [...]
> >> @@ -428,7 +428,7 @@ static long media_device_ioctl(struct file *filp,
> >> unsign
Em Wed, 27 Apr 2016 16:20:56 -0600
Shuah Khan escreveu:
> On 03/24/2016 05:37 AM, Mauro Carvalho Chehab wrote:
> > Em Thu, 24 Mar 2016 10:24:44 +0200
> > Laurent Pinchart escreveu:
> >
> >> On Wednesday 23 Mar 2016 16:27:46 Mauro Carvalho Chehab wrote:
> >>> struct media_devnode is currentl
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 similar issue to multi-planer even if
>> it
>> is in a single buffer.
>>
>> Th
Commit 0c426c472b5585ed6e59160359c979506d45ae49 ("[media] media: Always
keep a graph walk large enough around") changed
media_device_register_entity() function to take mdev->graph_mutex. This
causes deadlock in driver probe, which calls (indirectly) this function
with ->graph_mutex taken. This patc
Commit 0c426c472b5585ed6e59160359c979506d45ae49 ("[media] media: Always
keep a graph walk large enough around") changed
media_device_register_entity() function to take mdev->graph_mutex. This
causes deadlock in driver probe, which calls (indirectly) this function
with ->graph_mutex taken. This patc
Hi Hendrik,
Can you check that the chip on the board is indeed M88DS3103? I could
not read the text on the chip on the photo you sent earlier.
Furthermore, could you load the m88ds3103 driver with debugging
enabled before loading the cx23885 module:
modprobe m88ds3103 dyndbg==pmf
Then send the d
On Thu, Apr 28, 2016 at 8:36 AM, Laurent Pinchart
wrote:
>> > diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt
>> > b/Documentation/devicetree/bindings/media/renesas,fcp.txt new file mode
>> > 100644
>> > index ..0c72ca24379f
>> > --- /dev/null
>> > +++ b/Documentat
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
>>> --- a/drivers/media/media-devnode.c
>>> +++ b/drivers/media/media-devnode.
37 matches
Mail list logo
