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: Thu Apr 26 05:00:13 CEST 2018
media-tree git hash:a2b2eff6ac2716f499defa590a6ec4ba379d765e
media_build
On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig wrote:
> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>> Out of curiosity, how much virtual flushing stuff is there still out
>> there? At least in drm we've pretty much ignore this, and seem to be
>> getting
On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
> For more fun:
>
> https://www.spinics.net/lists/dri-devel/msg173630.html
>
> Yeah, sometimes we want to disable the iommu because the on-gpu
> pagetables are faster ...
I am not on this list, but remote NAK from here. This needs
On Wed, Apr 25, 2018 at 1:45 AM, Niklas Söderlund
wrote:
> Store the group pointer before disassociating the VIN from the group.
s/get/put/ in one-line summary?
> Fixes: 3bb4c3bc85bf77a7 ("media: rcar-vin: add group allocator functions")
> Reported-by:
On Wed, Apr 25, 2018 at 8:43 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
>> For more fun:
>>
>> https://www.spinics.net/lists/dri-devel/msg173630.html
>>
>> Yeah, sometimes we want to disable the iommu because the on-gpu
>>
On Wed, Apr 25, 2018 at 8:15 AM, Christoph Hellwig wrote:
> On Tue, Apr 24, 2018 at 10:40:45PM +0200, Arnd Bergmann wrote:
>> @@ -221,6 +222,7 @@ struct zoran_fh {
>>
>> struct zoran_overlay_settings overlay_settings;
>> u32 *overlay_mask; /*
On Tue, Apr 24, 2018 at 10:40:45PM +0200, Arnd Bergmann wrote:
> No drivers should use virt_to_bus() any more. This converts
> one of the few remaining ones to the DMA mapping interface.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/media/pci/zoran/Kconfig| 2 +-
>
On Wed, Apr 25, 2018 at 2:13 AM, Daniel Vetter wrote:
> On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig wrote:
>> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>>> Out of curiosity, how much virtual flushing stuff is there still out
>>>
On 23/04/18 23:09, Mauro Carvalho Chehab wrote:
>> I don't think it's worth it renaming the common symbols. They will change
>> over
>> time as omapdrm is under heavy rework, and it's painful enough without
>> having
>> to handle cross-tree changes.
>
> It could just rename the
On Wed, Apr 25, 2018 at 12:09:05AM -0700, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 09:02:17AM +0200, Daniel Vetter wrote:
> > Can we please not nack everything right away? Doesn't really motivate
> > me to show you all the various things we're doing in gpu to make the
> > dma layer work
On Wed, Apr 25, 2018 at 1:48 AM, Christoph Hellwig wrote:
> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>> Out of curiosity, how much virtual flushing stuff is there still out
>> there? At least in drm we've pretty much ignore this, and seem to be
>> getting
On Wed, Apr 25, 2018 at 09:02:17AM +0200, Daniel Vetter wrote:
> Can we please not nack everything right away? Doesn't really motivate
> me to show you all the various things we're doing in gpu to make the
> dma layer work for us. That kind of noodling around in lower levels to
> get them to do
On Tuesday 13 February 2018 11:18 PM, Kieran Bingham wrote:
From: Kieran Bingham
The ADV7511 has four 256-byte maps that can be accessed via the main I2C
ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
Allow
On Tuesday 13 February 2018 11:18 PM, Kieran Bingham wrote:
From: Kieran Bingham
The ADV7511 has four 256-byte maps that can be accessed via the main I2C
ports. Each map has it own I2C address and acts as a standard slave
device on the I2C bus.
On Wed, Apr 25, 2018 at 09:30:39AM +0200, Daniel Vetter wrote:
> On Wed, Apr 25, 2018 at 12:09:05AM -0700, Christoph Hellwig wrote:
> > On Wed, Apr 25, 2018 at 09:02:17AM +0200, Daniel Vetter wrote:
> > > Can we please not nack everything right away? Doesn't really motivate
> > > me to show you
On Wed, Apr 25, 2018 at 8:13 AM, Daniel Vetter wrote:
> On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig wrote:
>> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>>> Out of curiosity, how much virtual flushing stuff is there still out
>>>
On Wed, Apr 25, 2018 at 02:24:36AM -0400, Alex Deucher wrote:
> > It has a non-coherent transaction mode (which the chipset can opt to
> > not implement and still flush), to make sure the AGP horror show
> > doesn't happen again and GPU folks are happy with PCIe. That's at
> > least my
On Wed, Apr 25, 2018 at 09:08:13AM +0200, Arnd Bergmann wrote:
> > That probably also means it can use dma_mmap_coherent instead of the
> > handcrafted remap_pfn_range loop and the PageReserved abuse.
>
> I'd rather not touch that code. How about adding a comment about
> the fact that it should
On Wed, Apr 25, 2018 at 12:09:05AM -0700, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 09:02:17AM +0200, Daniel Vetter wrote:
> > Can we please not nack everything right away? Doesn't really motivate
> > me to show you all the various things we're doing in gpu to make the
> > dma layer work
On Tue, Apr 24, 2018 at 11:43:35PM -0700, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
> > For more fun:
> >
> > https://www.spinics.net/lists/dri-devel/msg173630.html
> >
> > Yeah, sometimes we want to disable the iommu because the on-gpu
> >
On Wed, Apr 25, 2018 at 01:54:39AM -0700, Christoph Hellwig wrote:
> [discussion about this patch, which should have been cced to the iommu
> and linux-arm-kernel lists, but wasn't:
> https://www.spinics.net/lists/dri-devel/msg173630.html]
>
> On Wed, Apr 25, 2018 at 09:41:51AM +0200, Thierry
Hi Todor,
Thanks for the update. Just a few minor comments below.
On Tue, Apr 24, 2018 at 06:01:07PM +0300, Todor Tomov wrote:
> The ov7251 sensor is a 1/7.5-Inch B VGA (640x480) CMOS Digital Image
> Sensor from Omnivision.
>
> The driver supports the following modes:
> - 640x480 30fps
> -
On Fri, Apr 20, 2018 at 03:28:28PM +0200, Geert Uytterhoeven wrote:
> Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS")
> is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy
> CONFIG_ARCH_SHMOBILE, hence use the former.
>
> Renesas SuperH SH-Mobile SoCs
On 25/04/18 12:03, Laurent Pinchart wrote:
> Could we trim down omapfb to remove support for the devices supported by
> omapdrm ?
I was thinking about just that. But, of course, it's not quite
straightforward either.
We've got DSI manual update functionality in OMAP3-OMAP5 SoCs, which
covers a
From 0a3355b47dc465c6372d30fa4a36d1c5db6c0fe2 Mon Sep 17 00:00:00 2001
From: Marcel Stork
Date: Wed, 25 Apr 2018 10:53:34 +0200
Subject: [PATCH] Add new dvb-t board ":Zolid Hybrid Tv Stick".
Extra code to be able to use this stick, only digital, not analog nor
remote-control.
Hi Tomi,
On Wednesday, 25 April 2018 13:10:43 EEST Tomi Valkeinen wrote:
> On 25/04/18 13:02, Laurent Pinchart wrote:
> > On Wednesday, 25 April 2018 12:33:53 EEST Tomi Valkeinen wrote:
> >> On 25/04/18 12:03, Laurent Pinchart wrote:
> >>> Could we trim down omapfb to remove support for the
On Monday, April 23, 2018 10:55:57 AM Mauro Carvalho Chehab wrote:
> Em Mon, 23 Apr 2018 14:47:28 +0200
> Bartlomiej Zolnierkiewicz escreveu:
>
> > On Friday, April 20, 2018 01:42:51 PM Mauro Carvalho Chehab wrote:
> > > Add stubs for omapfb_dss.h, in the case it is
On Wed, Apr 25, 2018 at 09:56:43AM +0200, Thierry Reding wrote:
> And to add to the confusion, none of this seems to be an issue on 64-bit
> ARM where the generic DMA/IOMMU code from drivers/iommu/dma-iommu.c is
> used.
In the long term I want everyone to use that code. Help welcome!
Hi Yong,
On Fri, Mar 30, 2018 at 11:15 AM Yong Zhi wrote:
> This adds coeff, config parameters etc const definitions for
> IPU3 programming.
> Signed-off-by: Yong Zhi
> ---
> drivers/media/pci/intel/ipu3/ipu3-tables.c | 9609
On 25/04/18 13:02, Laurent Pinchart wrote:
> Hi Tomi,
>
> On Wednesday, 25 April 2018 12:33:53 EEST Tomi Valkeinen wrote:
>> On 25/04/18 12:03, Laurent Pinchart wrote:
>>> Could we trim down omapfb to remove support for the devices supported by
>>> omapdrm ?
>>
>> I was thinking about just that.
[discussion about this patch, which should have been cced to the iommu
and linux-arm-kernel lists, but wasn't:
https://www.spinics.net/lists/dri-devel/msg173630.html]
On Wed, Apr 25, 2018 at 09:41:51AM +0200, Thierry Reding wrote:
> > API from the iommu/dma-mapping code. Drivers have no
Hi Tomi,
On Wednesday, 25 April 2018 09:24:14 EEST Tomi Valkeinen wrote:
> On 23/04/18 23:09, Mauro Carvalho Chehab wrote:
> >> I don't think it's worth it renaming the common symbols. They will change
> >> over time as omapdrm is under heavy rework, and it's painful enough
> >> without having to
Em Wed, 25 Apr 2018 11:09:50 +0200
mjs escreveu:
> From 0a3355b47dc465c6372d30fa4a36d1c5db6c0fe2 Mon Sep 17 00:00:00 2001
> From: Marcel Stork
> Date: Wed, 25 Apr 2018 10:53:34 +0200
> Subject: [PATCH] Add new dvb-t board ":Zolid Hybrid Tv Stick".
>
>
On Wed, Apr 25, 2018 at 01:54:39AM -0700, Christoph Hellwig wrote:
> [discussion about this patch, which should have been cced to the iommu
> and linux-arm-kernel lists, but wasn't:
> https://www.spinics.net/lists/dri-devel/msg173630.html]
>
> On Wed, Apr 25, 2018 at 09:41:51AM +0200, Thierry
Hi Tomi,
On Wednesday, 25 April 2018 12:33:53 EEST Tomi Valkeinen wrote:
> On 25/04/18 12:03, Laurent Pinchart wrote:
> > Could we trim down omapfb to remove support for the devices supported by
> > omapdrm ?
>
> I was thinking about just that. But, of course, it's not quite
> straightforward
On Wed, Apr 25, 2018 at 9:21 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 09:08:13AM +0200, Arnd Bergmann wrote:
>> > That probably also means it can use dma_mmap_coherent instead of the
>> > handcrafted remap_pfn_range loop and the PageReserved abuse.
>>
>> I'd
Enable CEU0 peripheral for Renesas R-Mobile A1 R8A7740.
Signed-off-by: Jacopo Mondi
---
arch/arm/boot/dts/r8a7740.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7740.dtsi b/arch/arm/boot/dts/r8a7740.dtsi
index
Hello,
this small series add R-Mobile A1 R8A7740 to the list of CEU supported
SoCs, and adds the CEU node to r8a7740.dtsi.
All the information on CEU clocks, power domains and memory regions have been
deducted from the now-deleted board file:
arch/arm/mach-shmobile/board-armadillo800eva.c
Em Wed, 25 Apr 2018 12:11:10 +0200
mjs escreveu:
> Op Wed, 25 Apr 2018 06:16:20 -0300
> Mauro Carvalho Chehab schreef:
>
> > Em Wed, 25 Apr 2018 11:09:50 +0200
> > mjs escreveu:
> >
> > > From
Hello,
this small series add device tree support for the MT9T112 image
sensor.
As in the device tree bindings I used 'semi-standard' name for the
'powerdown' GPIO, I have changed that for all other users of the mt9t112
driver (SH Ecovec only).
A note on clock: as the mt9t112 driver expects
Add support for OF systems to mt9t112 image sensor driver.
As the devicetree bindings use standard name for 'powerdown' gpio, and while
at there, update the existing mt9t112 users to use the new name.
Signed-off-by: Jacopo Mondi
---
Add R-Mobile A1 R8A7740 SoC to the list of compatible values for the CEU
unit.
Signed-off-by: Jacopo Mondi
---
Documentation/devicetree/bindings/media/renesas,ceu.txt | 7 ---
drivers/media/platform/renesas-ceu.c| 1 +
2 files changed, 5
On Monday, April 23, 2018 05:11:14 PM Tomi Valkeinen wrote:
> On 23/04/18 16:56, Bartlomiej Zolnierkiewicz wrote:
>
> > Ideally we should be able to build both drivers in the same kernel
> > (especially as modules).
> >
> > I was hoping that it could be fixed easily but then I discovered
> >
Add device tree bindings documentation for Micron MT9T111/MT9T112 image
sensors.
Signed-off-by: Jacopo Mondi
---
Documentation/devicetree/bindings/mt9t112.txt | 41 +++
1 file changed, 41 insertions(+)
create mode 100644
Op Wed, 25 Apr 2018 08:18:55 -0300
Mauro Carvalho Chehab schreef:
> Em Wed, 25 Apr 2018 12:11:10 +0200
> mjs escreveu:
>
> > Op Wed, 25 Apr 2018 06:16:20 -0300
> > Mauro Carvalho Chehab schreef:
> >
> > > Em Wed, 25
--
Mein Name ist SHANE MISSLER. Ich habe den Jackpot im Wert von $451
Millionen Lotto im Januar 2018 gewonnen. Ich habe eine Spende von
€2.100.000 für Sie. Ich spende Ihnen diese Spende wegen der Liebe, die
ich für die Menschheit und die Bedürftigen in der Gesellschaft habe.
Bitte
Em Wed, 25 Apr 2018 14:24:09 +0200
mjs escreveu:
> Op Wed, 25 Apr 2018 08:18:55 -0300
> Mauro Carvalho Chehab schreef:
>
> > Em Wed, 25 Apr 2018 12:11:10 +0200
> > mjs escreveu:
> >
> > > Op Wed, 25 Apr 2018 06:16:20 -0300
>
From: Colin Ian King
The current code decrements the timeout counter i and the end of
each loop i is incremented, so the check for timeout will always
be false and hence the timeout mechanism is just a dead code path.
Potentially, if the RD_READY bit is not set, we
2018-04-24 0:54 GMT+09:00 Akinobu Mita :
> 2018-04-23 18:17 GMT+09:00 Laurent Pinchart
> :
>> Hi Mita-san,
>>
>> On Sunday, 22 April 2018 18:56:07 EEST Akinobu Mita wrote:
>>> This adds a device tree binding documentation for
On Wed, Apr 25, 2018 at 12:04:29PM +0200, Daniel Vetter wrote:
> > Coordinating the backport of a trivial helper in the arm tree is not
> > the end of the world. Really, this cowboy attitude is a good reason
> > why graphics folks have such a bad rep. You keep poking into random
> > kernel
On Wed, Apr 25, 2018 at 5:26 PM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann wrote:
>> That thought had occurred to me as well. I removed the oldest ISDN
>> drivers already some years ago, and the OSS sound drivers
>> got removed as well,
Hi,
On 25.04.2018 13:54, Sakari Ailus wrote:
> Hi Todor,
>
> Thanks for the update. Just a few minor comments below.
Thanks for the review again, Sakari.
I'm preparing the next version.
Best regards,
Todor
The ov7251 sensor is a 1/7.5-Inch B VGA (640x480) CMOS Digital Image
Sensor from Omnivision.
The driver supports the following modes:
- 640x480 30fps
- 640x480 60fps
- 640x480 90fps
Output format is 10bit B RAW - MEDIA_BUS_FMT_Y10_1X10.
The driver supports configuration via user controls for:
-
Add the document for ov7251 device tree binding.
CC: Rob Herring
CC: Mark Rutland
CC: devicet...@vger.kernel.org
Signed-off-by: Todor Tomov
Reviewed-by: Rob Herring
---
Hallo
Christoph Hellwig wrote:
On Wed, Apr 25, 2018 at 09:08:13AM +0200, Arnd Bergmann wrote:
That probably also means it can use dma_mmap_coherent instead of the
handcrafted remap_pfn_range loop and the PageReserved abuse.
I'd rather not touch that code. How about adding a comment about
the
Em Wed, 25 Apr 2018 17:58:25 +0200
Arnd Bergmann escreveu:
> On Wed, Apr 25, 2018 at 5:26 PM, Christoph Hellwig wrote:
> > On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann wrote:
> >> That thought had occurred to me as well. I removed the oldest ISDN
Op Wed, 25 Apr 2018 11:45:05 -0300
Mauro Carvalho Chehab schreef:
> Em Wed, 25 Apr 2018 14:24:09 +0200
> mjs escreveu:
>
> > Op Wed, 25 Apr 2018 08:18:55 -0300
> > Mauro Carvalho Chehab schreef:
> >
> > > Em Wed, 25
On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann wrote:
> That thought had occurred to me as well. I removed the oldest ISDN
> drivers already some years ago, and the OSS sound drivers
> got removed as well, and comedi got converted to the dma-mapping
> interfaces, so there isn't much left
On Wed, 2018-04-25 at 14:22 -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 25 Apr 2018 17:58:25 +0200
> Arnd Bergmann escreveu:
>
> > On Wed, Apr 25, 2018 at 5:26 PM, Christoph Hellwig > rg> wrote:
> > > On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann
The ov7251 sensor is a 1/7.5-Inch B VGA (640x480) CMOS Digital Image
Sensor from Omnivision.
--
Version 4:
- remove OF dependency;
- use only stack memory in ov7251_write_seq_regs();
- use DIV_ROUND_UP to round up sleep
From: Bingbu Cao
Interrupt behavior shows that some time the frame end and frame start
of next frame is unstable and can range from several to hundreds
of micro-sec. In the case of ~10us, isr may not clear next sof interrupt
status in single handling, which prevents new
On Wed, Apr 25, 2018 at 2:41 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 02:24:36AM -0400, Alex Deucher wrote:
>> > It has a non-coherent transaction mode (which the chipset can opt to
>> > not implement and still flush), to make sure the AGP horror show
>> >
From c5007d7596dd755fb5d95664d9eda9733d7df461 Mon Sep 17 00:00:00 2001
From: Marcel Stork
Date: Wed, 25 Apr 2018 19:34:20 +0200
Subject: [PATCH] Remove 2 excess lines in driver module em28xx
A cosmetic change by combining two sets of boards into one set because having
the
From 911e4ce75588f23ead083fd520a45af5336ee761 Mon Sep 17 00:00:00 2001
From: Marcel Stork
Date: Wed, 25 Apr 2018 19:49:07 +0200
Subject: [PATCH] Add new dvb-t board ":Zolid Hybrid Tv Stick".
Extra code to be able to use this stick, only digital, not analog nor
remote-control.
On 14 March 2018 at 12:55, Hans Verkuil wrote:
> On 03/09/2018 09:49 AM, Gustavo Padovan wrote:
>> From: Gustavo Padovan
>>
>> Receive in-fence from userspace and add support for waiting on them
>> before queueing the buffer to the driver.
On Wed, Apr 25, 2018 at 10:44 AM, Alex Deucher wrote:
> On Wed, Apr 25, 2018 at 2:41 AM, Christoph Hellwig wrote:
>> On Wed, Apr 25, 2018 at 02:24:36AM -0400, Alex Deucher wrote:
>>> > It has a non-coherent transaction mode (which the chipset can opt to
On 17.12.2017 03:17, Laurent Pinchart wrote:
> Color keying is the action of replacing pixels matching a given color
> (or range of colors) with transparent pixels in an overlay when
> performing blitting. Depending on the hardware capabilities, the
> matching pixel can either become fully
Hi Samuel,
On Tue, Apr 24, 2018 at 03:11:19PM -0700, Sam Bobrowicz wrote:
> FYI, still hard at work on this. Did some more experiments last week
> that seemed to corroborate the clock tree in the spreadsheet.
Ok, good, I'll send an updated version next week taking this into
account then. Thanks!
Hello Laurent,
On 17.12.2017 03:17, Laurent Pinchart wrote:
> Hello,
>
> This patch series is an attempt at implementing standard properties for color
> keying support in the KMS API.
I was looking at implementing colorkey support for NVIDIA Tegra (older Tegra's
in particular) and Daniel Vetter
On Wed, Apr 25, 2018 at 5:33 PM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 12:04:29PM +0200, Daniel Vetter wrote:
>> > Coordinating the backport of a trivial helper in the arm tree is not
>> > the end of the world. Really, this cowboy attitude is a good reason
>> >
Hi Christian,
I love your patch! Yet something to improve:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.17-rc2 next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
C libraries with 64-bit time_t use an incompatible format for
struct omap3isp_stat_data. This changes the kernel code to
support either version, by moving over the normal handling
to the 64-bit variant, and adding compatiblity code to handle
the old binary format with the existing ioctl command
Hi Mita-san,
On Wednesday, 25 April 2018 19:19:11 EEST Akinobu Mita wrote:
> 2018-04-24 0:54 GMT+09:00 Akinobu Mita :
> > 2018-04-23 18:17 GMT+09:00 Laurent Pinchart:
> >> On Sunday, 22 April 2018 18:56:07 EEST Akinobu Mita wrote:
> >>> This adds a device tree binding
On Wed, Apr 25, 2018 at 08:33:12AM -0700, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 12:04:29PM +0200, Daniel Vetter wrote:
> > - dma api hides the cache flushing requirements from us. GPUs love
> > non-snooped access, and worse give userspace control over that. We want
> > a strict
On Wed, Apr 25, 2018 at 11:35:13PM +0200, Daniel Vetter wrote:
> On arm that doesn't work. The iommu api seems like a good fit, except
> the dma-api tends to get in the way a bit (drm/msm apparently has
> similar problems like tegra), and if you need contiguous memory
> dma_alloc_coherent is the
75 matches
Mail list logo