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 Jan 4 05:00:17 CET 2018
media-tree git hash:6f0e5fd39143a59c22d60e7befc4f33f22aeed2f
media_build git
From: Tianshu Qiu
This patch set adds new pixel formats specific for intel 3rd generation ipu
driver.
Tianshu Qiu (2):
Update headers from upstream kernel
Add support for intel ipu3 specific raw formats
include/linux/videodev2.h | 15 +++
yavta.c | 4
2
From: Tianshu Qiu
Add support for these pixel formats:
V4L2_PIX_FMT_IPU3_SBGGR10
V4L2_PIX_FMT_IPU3_SGBRG10
V4L2_PIX_FMT_IPU3_SGRBG10
V4L2_PIX_FMT_IPU3_SRGGB10
Signed-off-by: Tianshu Qiu
---
yavta.c | 4
1 file changed, 4 insertions(+)
diff --git a/yavta.c b/yavta.c
index afe96331a520..5
From: Tianshu Qiu
Upstream commit 6f0e5fd39143a59c22d60e7befc4f33f22aeed2f
Signed-off-by: Tianshu Qiu
---
include/linux/videodev2.h | 15 +++
1 file changed, 15 insertions(+)
diff --git a/include/linux/videodev2.h b/include/linux/videodev2.h
index b1e36ee553da..afa4d09c59a3 100644
From: Tianshu Qiu
Add support for these pixel formats:
V4L2_PIX_FMT_IPU3_SBGGR10
V4L2_PIX_FMT_IPU3_SGBRG10
V4L2_PIX_FMT_IPU3_SGRBG10
V4L2_PIX_FMT_IPU3_SRGGB10
Signed-off-by: Tianshu Qiu
---
yavta.c | 4
1 file changed, 4 insertions(+)
diff --git a/yavta.c b/yavta.c
index afe96331a520..5
From: Tianshu Qiu
This patch set adds new pixel formats specific for intel 3rd generation ipu
driver.
Tianshu Qiu (2):
Update headers from upstream kernel
Add support for intel ipu3 specific raw formats
include/linux/videodev2.h | 15 +++
yavta.c | 4
2
From: Tianshu Qiu
Upstream commit 6f0e5fd39143a59c22d60e7befc4f33f22aeed2f
Signed-off-by: Tianshu Qiu
---
include/linux/videodev2.h | 15 +++
1 file changed, 15 insertions(+)
diff --git a/include/linux/videodev2.h b/include/linux/videodev2.h
index b1e36ee553da..afa4d09c59a3 100644
When dmabuf is used for BLOB type frame, the frame
buffers allocated by gralloc will hold more pages
than the valid frame data due to height alignment.
In this case, the page numbers in sg list could exceed the
FBPT upper limit value - max_lops(8)*1024 to cause crash.
Limit the LOP access to the
cio2 driver should release buffer with QUEUED state
when start_stream op failed, wrong buffer state will
cause vb2 core throw a warning.
Signed-off-by: Yong Zhi
Signed-off-by: Cao Bing Bu
---
drivers/media/pci/intel/ipu3/ipu3-cio2.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
On Wed, Jan 3, 2018 at 11:23 AM, Mauro Carvalho Chehab
wrote:
> Em Tue, 2 Jan 2018 10:48:54 +0100
> Arnd Bergmann escreveu:
>> @@ -2965,7 +2968,6 @@ void dvb_frontend_detach(struct dvb_frontend* fe)
>> dvb_frontend_invoke_release(fe, fe->ops.release_sec);
>> dvb_frontend_invoke_rele
The driver apparently assumes that the device uses the same page size
as the CPU, but also assumes that this is 4096 bytes. On architectures
with a larger page size like 65536 bytes, we get a warning about an
integer overflow:
drivers/media/pci/intel/ipu3/ipu3-cio2.c: In function
'cio2_fbpt_entry
Hi Sakari,
thanks for review..
On Wed, Jan 03, 2018 at 12:11:32PM +0200, Sakari Ailus wrote:
> Hi Jacopo,
>
> Please see my comments below.
>
> On Tue, Jan 02, 2018 at 04:03:53PM +0100, Jacopo Mondi wrote:
> > ov7670 driver supports two optional properties supplied through platform
> > data, b
On 1/3/2018 12:32 PM, Kieran Bingham wrote:
> From: Kieran Bingham
>
> The Linux UVC driver has long provided adequate performance capabilities for
> web-cams and low data rate video devices in Linux while resolutions were low.
>
> Modern USB cameras are now capable of high data rates thanks to
Hi Fabio,
On Wed, Jan 03, 2018 at 02:57:07PM -0200, Fabio Estevam wrote:
> clk_prepare_enable() may fail, so we should better check its return value
> and propagate it in the case of error.
>
> Signed-off-by: Fabio Estevam
Thanks for the patch. This particular issue appears to have been address
From: Kieran Bingham
We currently store three separate arrays for each URB reference we hold.
Objectify the data needed to track URBs into a single uvc_urb structure,
allowing better object management and tracking of the URB.
All accesses to the data pointers through stream, are converted to us
From: Kieran Bingham
The URB completion handlers currently reference the stream context.
Now that each URB has its own context structure, convert the decode (and
one encode) functions to utilise this context for URB management.
Signed-off-by: Kieran Bingham
Reviewed-by: Laurent Pinchart
---
From: Kieran Bingham
Both uvc_start_streaming(), and uvc_stop_streaming() are called from
userspace context. As such, they do not need to save the IRQ state, and
can use spin_lock_irq() and spin_unlock_irq() respectively.
Signed-off-by: Kieran Bingham
---
drivers/media/usb/uvc/uvc_queue.c | 10
From: Kieran Bingham
The URB completion operation obtains the current buffer by reading
directly into the queue internal interface.
Protect this queue abstraction by providing a helper
uvc_queue_get_current_buffer() which can be used by both the decode
task, and the uvc_queue_next_buffer() funct
From: Kieran Bingham
The buffer queue interface currently operates sequentially, processing
buffers after they have fully completed.
In preparation for supporting parallel tasks operating on the buffers,
we will need to support buffers being processed on multiple CPUs.
Adapt the uvc_queue_next_
From: Kieran Bingham
Newer high definition cameras, and cameras with multiple lenses such as
the range of stereovision cameras now available have ever increasing
data rates.
The inclusion of a variable length packet header in URB packets mean
that we must memcpy the frame data out to our destina
From: Kieran Bingham
The Linux UVC driver has long provided adequate performance capabilities for
web-cams and low data rate video devices in Linux while resolutions were low.
Modern USB cameras are now capable of high data rates thanks to USB3 with
1080p, and even 4k capture resolutions support
Hi Fabio,
On Wed, Jan 03, 2018 at 04:14:35PM -0200, Fabio Estevam wrote:
> On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote:
>
> >> Initially the rest GPIO was doing:
> >>
> >> - gpio_set_value(GPIO_PTT3, 0);
> >> - mdelay(10);
> >> - gpio_set_value(GPIO_PTT3, 1);
> >> -
Create a source pad and set the media controller type to the sensor.
Cc: Sakari Ailus
Cc: Mauro Carvalho Chehab
Signed-off-by: Akinobu Mita
---
* Changelog v2
- Fix typo s/meida/media/ in the patch title, noticed by Sakari Ailus
drivers/media/i2c/mt9m111.c | 22 --
1 file
The mt9m111 driver requires clocks property for the master clock to the
sensor, but there is no description for that. This adds it.
Cc: Rob Herring
Cc: Sakari Ailus
Cc: Mauro Carvalho Chehab
Signed-off-by: Akinobu Mita
---
* Changelog v2
- Fix typo s/meida/media/ in the patch title, noticed b
The mt9m111 has the test pattern generator features. This makes use of
it through V4L2_CID_TEST_PATTERN control.
Cc: Sakari Ailus
Cc: Mauro Carvalho Chehab
Signed-off-by: Akinobu Mita
---
* Changelog v2
- Fix typo s/meida/media/ in the patch title, noticed by Sakari Ailus
drivers/media/i2c/m
This series adds media controller support and other miscellaneous changes
to the mt9m111 driver. The MT9M111 camera modules are easily available
for the hobbyists.
* Changelog v2
- Fix typo s/meida/media/ in the patch title, noticed by Sakari Ailus
- Improve the wording for "clock-names" property,
Set the V4L2_SUBDEV_FL_HAS_DEVNODE flag for the subdevice so that the
subdevice device node is created.
Cc: Sakari Ailus
Cc: Mauro Carvalho Chehab
Signed-off-by: Akinobu Mita
---
* Changelog v2
- Fix typo s/meida/media/ in the patch title, noticed by Sakari Ailus
drivers/media/i2c/mt9m111.c |
On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote:
>> Initially the rest GPIO was doing:
>>
>> - gpio_set_value(GPIO_PTT3, 0);
>> - mdelay(10);
>> - gpio_set_value(GPIO_PTT3, 1);
>> - mdelay(10); /* wait to let chip come out of reset */
>
> And that's what my driver code
Hi Fabio,
On Wed, Jan 03, 2018 at 03:27:53PM -0200, Fabio Estevam wrote:
> Hi Jacopo,
>
> On Wed, Jan 3, 2018 at 3:13 PM, jacopo mondi wrote:
>
> > That would be true if I would have declared the GPIO to be ACTIVE_LOW.
> > See patch [5/9] in this series and search for "rstb". The GPIO (which
> >
Hi Jacopo,
On Wed, Jan 3, 2018 at 3:13 PM, jacopo mondi wrote:
> That would be true if I would have declared the GPIO to be ACTIVE_LOW.
> See patch [5/9] in this series and search for "rstb". The GPIO (which
> is shared between two devices) is said to be active high...
Just looked at your patch
Hi Fabio,
On Wed, Jan 03, 2018 at 02:41:20PM -0200, Fabio Estevam wrote:
> Hi Jacopo,
>
> On Thu, Dec 28, 2017 at 12:01 PM, Jacopo Mondi
> wrote:
>
> > + if (priv->rstb_gpio) {
> > + gpiod_set_value(priv->rstb_gpio, 0);
> > + usleep_range(500, 1000);
> > +
clk_prepare_enable() may fail, so we should better check its return value
and propagate it in the case of error.
Signed-off-by: Fabio Estevam
---
drivers/media/i2c/ov5640.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov564
Hi Jacopo,
On Thu, Dec 28, 2017 at 12:01 PM, Jacopo Mondi
wrote:
> + if (priv->rstb_gpio) {
> + gpiod_set_value(priv->rstb_gpio, 0);
> + usleep_range(500, 1000);
> + gpiod_set_value(priv->rstb_gpio, 1);
> + usleep_range(500, 1000);
T
Hi Laurent,
On Tue, Jan 02, 2018 at 05:50:38PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> Thank you for the patch.
>
> On Thursday, 28 December 2017 16:01:21 EET Jacopo Mondi wrote:
> > - priv->clk = v4l2_clk_get(&client->dev, "mclk");
> > - if (IS_ERR(priv->clk))
> > + priv->clk = clk_
Hi Laurent,
On Wed, Jan 03, 2018 at 05:49:55PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> >
> > DT based platforms won't have any info->xlkc_rate, so they should be
> > fine. I wonder how could I set rate in board code, as I'm just
> > registering an alias for the clock there...
>
> Exactly a
Hi Jacopo,
On Wednesday, 3 January 2018 17:44:58 EET jacopo mondi wrote:
> On Tue, Jan 02, 2018 at 05:44:03PM +0200, Laurent Pinchart wrote:
> > On Thursday, 28 December 2017 16:01:19 EET Jacopo Mondi wrote:
> >> Remove soc_camera framework dependencies from ov772x sensor driver.
> >> - Handle clo
On Thu, 2017-12-21 at 05:52 +0800, kbuild test robot wrote:
> Hi Philipp,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on linuxtv-media/master]
> [also build test WARNING on v4.15-rc4 next-20171220]
> [if your patch is applied to the wrong git tree, please dro
Hi Laurent,
On Tue, Jan 02, 2018 at 05:44:03PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> Thank you for the patch.
>
> On Thursday, 28 December 2017 16:01:19 EET Jacopo Mondi wrote:
> > Remove soc_camera framework dependencies from ov772x sensor driver.
> > - Handle clock and gpios
> > - Regi
On Fri, Dec 29, 2017 at 04:08:22PM +0800, Shunqian Zheng wrote:
> This patch adds driver for Omnivision's ov5695 sensor,
> the driver supports following features:
> - supported resolutions
>+ 2592x1944 at 30fps
>+ 1920x1080 at 30fps
>+ 1296x972 at 60fps
>+ 1280x720 at 30fps
>+
Hi Mauro,
The following changes since commit 9eb124fe796cbadd454c8f946d7051f4c3f4a251:
Merge branch 'docs-next' of git://git.lwn.net/linux into patchwork
(2017-12-22 14:38:28 -0500)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git uvc/next
for you to fetch cha
Hi Shunqian,
On Fri, Dec 29, 2017 at 04:08:25PM +0800, Shunqian Zheng wrote:
> Add device tree binding documentation for the OV2685 sensor.
DT bindings should precede the driver. Speaking of which --- you should add
an entry in the MAINTAINERS file for both.
>
> Signed-off-by: Shunqian Zheng
>
Hi Shunqian,
Please see my comments below.
On Fri, Dec 29, 2017 at 04:08:24PM +0800, Shunqian Zheng wrote:
> This patch adds driver for Omnivision's ov2685 sensor.
> Though the ov2685 can output yuv data, this driver only
> supports the raw bayer format, including the following features:
> - ou
Hi Jacopo,
On Wednesday, 3 January 2018 10:49:52 EET jacopo mondi wrote:
> On Tue, Jan 02, 2018 at 01:45:30PM +0200, Laurent Pinchart wrote:
> > On Thursday, 28 December 2017 16:01:13 EET Jacopo Mondi wrote:
> >> Add bindings documentation for Renesas Capture Engine Unit (CEU).
> >>
> >> Signed-o
Hi Jacopo,
On Wednesday, 3 January 2018 12:47:48 EET jacopo mondi wrote:
> On Tue, Jan 02, 2018 at 03:46:27PM +0200, Laurent Pinchart wrote:
> >> +/*
> >> + * ceu_device - CEU device instance
> >> + */
> >> +struct ceu_device {
> >> + struct device *dev;
> >> + struct video_device
From: Edgar Thier
Use flags the device exposes for UVC controls.
This allows the device to define which property flags are set.
Since some cameras offer auto-adjustments for properties (e.g. auto-gain),
the values of other properties (e.g. gain) can change in the camera.
Examining the flags ensu
Hi Edgar,
On Wednesday, 3 January 2018 08:07:44 EET Edgar Thier wrote:
> Hi Emmanuel,
If we pick names randomly I'll call you David :-)
> >>> + int flags = 0;
> >>> +
> >>> + data = kmalloc(2, GFP_KERNEL);
> >
> > Isn't 1 byte enough ?
>
> To quote from Kieran further up this thread:
>
> >> k
Hi Laurent,
On Tue, Jan 02, 2018 at 03:46:27PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> Thank you for the patch.
>
> > +/*
> > + * ceu_device - CEU device instance
> > + */
> > +struct ceu_device {
> > + struct device *dev;
> > + struct video_device vdev;
> > + struct v4
Em Tue, 2 Jan 2018 10:48:54 +0100
Arnd Bergmann escreveu:
> A bugfix introduce a link failure in configurations without CONFIG_MODULES:
>
> In file included from drivers/media/usb/dvb-usb/pctv452e.c:20:0:
> drivers/media/usb/dvb-usb/pctv452e.c: In function 'pctv452e_frontend_attach':
> drivers/
Hi Jacopo,
Please see my comments below.
On Tue, Jan 02, 2018 at 04:03:53PM +0100, Jacopo Mondi wrote:
> ov7670 driver supports two optional properties supplied through platform
> data, but currently does not support any standard video interface
> property.
>
> Add support through OF parsing for
Em Mon, 1 Jan 2018 19:42:40 +
Bryan O'Donoghue escreveu:
> Right now it is not possible to return a value larger than LONG_MAX on 32
> bit systems. You can pass a rate of ULONG_MAX but can't return anything
> past LONG_MAX due to the fact both the rounded_rate and negative error
> codes are
v5 sent !
On 01/03/2018 10:23 AM, Sakari Ailus wrote:
> Hi Hugues,
>
> On Wed, Jan 03, 2018 at 09:12:43AM +, Hugues FRUCHET wrote:
>> OK, thanks for all Sakari !
>
> One thing I've missed so far --- the DT binding changes should be always
> cc'd to the devicetree list which I see is missing
Switch gpiod_set_value to gpiod_set_value_cansleep to avoid
warnings when powering sensor.
Signed-off-by: Hugues Fruchet
---
drivers/media/i2c/ov5640.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov5640.c
index c89ed6
Add support of DVP parallel mode in addition of
existing MIPI CSI mode. The choice between two modes
and configuration is made through device tree.
Signed-off-by: Hugues Fruchet
---
drivers/media/i2c/ov5640.c | 148 +++--
1 file changed, 130 insertions(+),
Verify that chip identifier is correct when probing.
Signed-off-by: Hugues Fruchet
---
drivers/media/i2c/ov5640.c | 95 ++
1 file changed, 79 insertions(+), 16 deletions(-)
diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov5640.c
index 610
Refine CSI-2 endpoint documentation and add bindings
for DVP parallel interface support.
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/i2c/ov5640.txt | 46 +-
1 file changed, 44 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindi
Enhance OV5640 CSI driver to support also DVP parallel interface.
Add RGB565 (LE & BE) and YUV422 YUYV format in addition to existing
YUV422 UYVY format.
Some other improvements on chip identifier check and removal
of warnings in powering phase around gpio handling.
===
= history =
===
Add RGB565 (LE & BE) and YUV422 YUYV format in addition
to existing YUV422 UYVY format.
Signed-off-by: Hugues Fruchet
---
drivers/media/i2c/ov5640.c | 74 +-
1 file changed, 67 insertions(+), 7 deletions(-)
diff --git a/drivers/media/i2c/ov5640.c b/dr
When CONFIG_PM is disabled, we get harmless warnings about the
suspend/resume callbacks being unused:
drivers/media/pci/intel/ipu3/ipu3-cio2.c:1993:12: error: 'cio2_resume' defined
but not used [-Werror=unused-function]
drivers/media/pci/intel/ipu3/ipu3-cio2.c:1967:12: error: 'cio2_suspend' defin
Hi Hugues,
On Wed, Jan 03, 2018 at 09:12:43AM +, Hugues FRUCHET wrote:
> OK, thanks for all Sakari !
One thing I've missed so far --- the DT binding changes should be always
cc'd to the devicetree list which I see is missing now. Could you send v5,
cc'ing at least the bindings to the devicetr
OK, thanks for all Sakari !
On 01/03/2018 10:10 AM, Sakari Ailus wrote:
> On Wed, Jan 03, 2018 at 08:47:09AM +, Hugues FRUCHET wrote:
>> Hi Sakari,
>> this is fine for me to drop those two lines so sync signals become
>> mandatory.
>> Must I repost a v5 serie ?
>
> Here's the diff:
>
> diff
On Wed, Jan 03, 2018 at 08:47:09AM +, Hugues FRUCHET wrote:
> Hi Sakari,
> this is fine for me to drop those two lines so sync signals become
> mandatory.
> Must I repost a v5 serie ?
Here's the diff:
diff --git a/Documentation/devicetree/bindings/media/i2c/ov5640.txt
b/Documentation/device
On Wed, Jan 03, 2018 at 08:47:09AM +, Hugues FRUCHET wrote:
> Hi Sakari,
> this is fine for me to drop those two lines so sync signals become
> mandatory.
> Must I repost a v5 serie ?
I'll do that while applying the patches. Thanks.
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
Hi Laurent,
On Tue, Jan 02, 2018 at 01:50:07PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> Thank you for the patch.
>
> On Thursday, 28 December 2017 16:01:14 EET Jacopo Mondi wrote:
> > Add renesas-ceu header file.
> >
> > Do not remove the existing sh_mobile_ceu.h one as long as the original
Hi Laurent,
On Tue, Jan 02, 2018 at 01:45:30PM +0200, Laurent Pinchart wrote:
> Hi Jacopo,
>
> Thank you for the patch.
>
> On Thursday, 28 December 2017 16:01:13 EET Jacopo Mondi wrote:
> > Add bindings documentation for Renesas Capture Engine Unit (CEU).
> >
> > Signed-off-by: Jacopo Mondi
> >
Hi Sakari,
this is fine for me to drop those two lines so sync signals become
mandatory.
Must I repost a v5 serie ?
Best regards,
Hugues.
On 01/02/2018 01:24 PM, Sakari Ailus wrote:
> On Tue, Jan 02, 2018 at 02:20:46PM +0200, Sakari Ailus wrote:
>> Hi Hugues,
>>
>> One more thing, please see bel
65 matches
Mail list logo