On Thu, Feb 22, 2018 at 11:37:20AM +0100, Jacopo Mondi wrote:
> Add Capture Engine Unit (CEU) node to device tree.
>
> Signed-off-by: Jacopo Mondi
> Reviewed-by: Geert Uytterhoeven
> Reviewed-by: Laurent Pinchart
> Acked-by: Hans Verkuil
I have marked this patch as deferred as it depends on t
3 warning regressions:
+ drivers/media/i2c/ov13858.c: warning: cast to restricted __be32: => 1093:16
+ drivers/media/i2c/ov13858.c: warning: incorrect type in assignment
(different base types): => :13
+ drivers/media/i2c/ov13858.c: warning: incorrect type in initializer
(different bas
Hi Laurent,
Thanks for your patch.
On 2018-02-22 22:52:26 +0200, Laurent Pinchart wrote:
> The DRM pipelines can use either the BRU or the BRS for blending. Make
> sure the right name is used in debugging messages to avoid confusion.
>
> Signed-off-by: Laurent Pinchart
Reviewed-by: Niklas Söde
Videobuf2 is now separate from V4L2 and can be now built without it, at
least in principle --- enabling videobuf2 in kernel configuration attempts
to compile videobuf2-v4l2.c but that will fail if CONFIG_VIDEO_V4L2 isn't
enabled.
Solve this by adding a separate Kconfig option for videobuf2-v4l2 an
Add a function (as well as a helper macro) to obtain the best size in a
list of device specific sizes. This helps writing drivers as well as
aligns interface behaviour across drivers.
The struct in which this information is contained in is typically specific
to the driver, therefore the existing f
Hi Sakari,
Thank you for the patch.
On Friday, 23 February 2018 10:29:46 EET Sakari Ailus wrote:
> Videobuf2 is now separate from V4L2 and can be now built without it, at
> least in principle --- enabling videobuf2 in kernel configuration attempts
> to compile videobuf2-v4l2.c but that will fail
Signed-off-by: Luca Ceresoli
---
drivers/media/i2c/imx274.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/imx274.c b/drivers/media/i2c/imx274.c
index 664e8acdf2a0..daec33f4196a 100644
--- a/drivers/media/i2c/imx274.c
+++ b/drivers/media/i2c/imx274.c
@@ -142
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0f9da844d87796ac31b04e81ee95e155e9043132
commit: 7952be9b6ece3d3c4d61f9811d7e5a984580064a media:
drivers/media/common/videobuf2: rename from videobuf
date: 4 weeks ago
config: x86_64-randconfig-s1-02231552
Hi Steve,
Thank you for the patch.
On Thursday, 22 February 2018 03:39:37 EET Steve Longerbeam wrote:
> For some subdevices, a fwnode endpoint that has no connection to a remote
> endpoint may not be an error. Let the parse_endpoint callback make that
> decision in v4l2_async_notifier_fwnode_pars
Add a function (as well as a helper macro) to obtain the best size in a
list of device specific sizes. This helps writing drivers as well as
aligns interface behaviour across drivers.
The struct in which this information is contained in is typically specific
to the driver, therefore the existing f
Hi Laurent,
On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart wrote:
> Hi Steve,
>
> Thank you for the patch.
>
> On Thursday, 22 February 2018 03:39:37 EET Steve Longerbeam wrote:
> > For some subdevices, a fwnode endpoint that has no connection to a remote
> > endpoint may not be an error. L
Hi Philipp,
On Friday, 23 February 2018 11:56:52 EET Philipp Zabel wrote:
> On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart wrote:
> > On Thursday, 22 February 2018 03:39:37 EET Steve Longerbeam wrote:
> >> For some subdevices, a fwnode endpoint that has no connection to a
> >> remote endpoint
There was a trouble with vb2-trace: instead of being part of
VB2 core, it was stored at V4L2 videodev. That was wrong,
as it doesn't actually belong to V4L2 core.
Now that vb2 is not part of v4l2-core, its trace functions
should be moved altogether. So, move it to its rightful
place: at videobuf2-
Hi guys,
On Fri, Feb 23, 2018 at 12:05:38PM +0200, Laurent Pinchart wrote:
> Hi Philipp,
>
> On Friday, 23 February 2018 11:56:52 EET Philipp Zabel wrote:
> > On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart wrote:
> > > On Thursday, 22 February 2018 03:39:37 EET Steve Longerbeam wrote:
> > >>
On Thu, Feb 22, 2018 at 12:38 AM, James Hogan wrote:
> These patches remove the metag architecture and tightly dependent
> drivers from the kernel. With the 4.16 kernel the ancient gcc 4.2.4
> based metag toolchain we have been using is hitting compiler bugs, so
> now seems a good time to drop it
On Fri, Feb 23, 2018 at 11:26:58AM +0100, Arnd Bergmann wrote:
> On Thu, Feb 22, 2018 at 12:38 AM, James Hogan wrote:
> > So lets call it a day and drop the Meta architecture port from the
> > kernel. RIP Meta.
>
> Since I brought up the architecture removal independently, I could
> pick this up
Hi Laurent,
On Fri, 2018-02-23 at 12:05 +0200, Laurent Pinchart wrote:
> Hi Philipp,
>
> On Friday, 23 February 2018 11:56:52 EET Philipp Zabel wrote:
> > On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart wrote:
> > > On Thursday, 22 February 2018 03:39:37 EET Steve Longerbeam wrote:
> > > > Fo
tree: git://linuxtv.org/media_tree.git fixes
head: 0e0751a4b9ee82ff086472ab4e81ee693fbe091a
commit: a3938f1b749cbedf47c4cb6af08f1c29e9418007 [10/11] media: dvb: update
buffer mmaped flags and frame counter
config: i386-randconfig-s0-201807 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9)
tree: git://linuxtv.org/media_tree.git fixes
head: 0e0751a4b9ee82ff086472ab4e81ee693fbe091a
commit: a3938f1b749cbedf47c4cb6af08f1c29e9418007 [10/11] media: dvb: update
buffer mmaped flags and frame counter
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reprodu
Hi Laurent,
Thankyou for the patch (update).
On 22/02/18 20:52, Laurent Pinchart wrote:
> The DRM pipelines can use either the BRU or the BRS for blending. Make
> sure the right name is used in debugging messages to avoid confusion.
>
> Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingha
On Fri, Feb 23, 2018 at 12:02 PM, James Hogan wrote:
> On Fri, Feb 23, 2018 at 11:26:58AM +0100, Arnd Bergmann wrote:
>> On Thu, Feb 22, 2018 at 12:38 AM, James Hogan wrote:
>> > So lets call it a day and drop the Meta architecture port from the
>> > kernel. RIP Meta.
>>
>> Since I brought up the
On Fri, Feb 23, 2018 at 05:10:38AM -0500, Mauro Carvalho Chehab wrote:
> There was a trouble with vb2-trace: instead of being part of
> VB2 core, it was stored at V4L2 videodev. That was wrong,
> as it doesn't actually belong to V4L2 core.
>
> Now that vb2 is not part of v4l2-core, its trace funct
Hi Philipp,
On Fri, Feb 23, 2018 at 12:16:17PM +0100, Philipp Zabel wrote:
> Hi Laurent,
>
> On Fri, 2018-02-23 at 12:05 +0200, Laurent Pinchart wrote:
> > Hi Philipp,
> >
> > On Friday, 23 February 2018 11:56:52 EET Philipp Zabel wrote:
> > > On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart
Without CONFIG_SND, we get a link error:
ERROR: "snd_soc_register_codec" [drivers/media/i2c/tda1997x.ko] undefined!
ERROR: "snd_soc_unregister_codec" [drivers/media/i2c/tda1997x.ko] undefined!
ERROR: "snd_pcm_hw_constraint_minmax" [drivers/media/i2c/tda1997x.ko] undefined!
This adds the same Kcon
tree: git://linuxtv.org/media_tree.git fixes
head: 0e0751a4b9ee82ff086472ab4e81ee693fbe091a
commit: a3938f1b749cbedf47c4cb6af08f1c29e9418007 [10/11] media: dvb: update
buffer mmaped flags and frame counter
reproduce:
# apt-get install sparse
git checkout a3938f1b749cbedf47c4cb6
On 02/23/2018 09:29 AM, Sakari Ailus wrote:
> Videobuf2 is now separate from V4L2 and can be now built without it, at
> least in principle --- enabling videobuf2 in kernel configuration attempts
> to compile videobuf2-v4l2.c but that will fail if CONFIG_VIDEO_V4L2 isn't
> enabled.
>
> Solve this b
Hi Sakari,
Thanks for your review.
On Fri 23 Feb 2018 at 07:50, Sakari Ailus wrote:
Hi Rui,
On Thu, Feb 22, 2018 at 10:23:38AM +, Rui Miguel Silva
wrote:
This patch adds V4L2 sub-device driver for OV2680 image sensor.
The OV2680 is a 1/5" CMOS color sensor from Omnivision.
Supports output
Hi Fabio,
On Thu 22 Feb 2018 at 11:31, Fabio Estevam wrote:
On Thu, Feb 22, 2018 at 7:23 AM, Rui Miguel Silva
wrote:
Add device tree binding documentation for the OV5640 camera
sensor.
s/OV5640/OV2680
Thanks for notice this ;).
---
Cheers,
Rui
Hi Sakari,
Thanks for the review.
On Thu 22 Feb 2018 at 10:59, Sakari Ailus wrote:
Hi Rui,
Thanks for the patchset.
Could you use "dt: bindings: " prefix in the subject?
Sure, no problem.
On Thu, Feb 22, 2018 at 10:23:37AM +, Rui Miguel Silva
wrote:
Add device tree binding documentat
From: Alan Chiang
Dongwoon DW9807 is a voice coil lens driver.
Also add a vendor prefix for Dongwoon for one did not exist previously.
Signed-off-by: Andy Yeh
---
Documentation/devicetree/bindings/media/i2c/dongwoon,dw9807.txt | 9 +
1 file changed, 9 insertions(+)
create mode 100644
Hi Sakari and Tomasz,
The two patches are the DT binding and driver for DW9807 VCM controller.
Alan Chiang (2):
media: dw9807: Add dw9807 vcm driver
media: dt-bindings: Add bindings for Dongwoon DW9807 voice coil
.../bindings/media/i2c/dongwoon,dw9807.txt | 9 +
MAINTAINERS
From: Alan Chiang
DW9807 is a 10 bit DAC from Dongwoon, designed for linear
control of voice coil motor.
This driver creates a V4L2 subdevice and
provides control to set the desired focus.
Signed-off-by: Andy Yeh
---
since v1:
- changed author.
since v2:
- addressed outstanding comments.
- ena
The filter callbaks now have an optional extra argument,
meant to allow reporting statistics to userspace via mmap.
Set those to NULL, in order to avoid those build errors:
+ drivers/media/pci/ttpci/av7110.c: error: too few arguments to function
'dvbdmxfilter->feed->cb.sec': => 325:10
+ driv
Hi Mauro,
Thank you for the patch.
On Friday, 23 February 2018 18:43:48 EET Mauro Carvalho Chehab wrote:
> The filter callbaks now have an optional extra argument,
> meant to allow reporting statistics to userspace via mmap.
>
> Set those to NULL, in order to avoid those build errors:
> + driv
Hi all,
On 02/23/2018 03:16 AM, Philipp Zabel wrote:
Hi Laurent,
On Fri, 2018-02-23 at 12:05 +0200, Laurent Pinchart wrote:
Hi Philipp,
On Friday, 23 February 2018 11:56:52 EET Philipp Zabel wrote:
On Fri, 2018-02-23 at 11:29 +0200, Laurent Pinchart wrote:
On Thursday, 22 February 2018 03:
Em Fri, 23 Feb 2018 19:52:48 +0200
Laurent Pinchart escreveu:
> Hi Mauro,
>
> Thank you for the patch.
>
> On Friday, 23 February 2018 18:43:48 EET Mauro Carvalho Chehab wrote:
> > The filter callbaks now have an optional extra argument,
> > meant to allow reporting statistics to userspace via
i noticed that my pinnacle 300i could accept full resolution settings:
v4l2-ctl --set-fmt-video=width=720,height=576
only the first time the command is fired.
after that, evey time i try to set that resolution with the same
command, i get instead only the half vertical resolution:
v4l2-ctl --get-
On Fri, Feb 23, 2018 at 2:30 PM, Federico Allegretti
wrote:
> i noticed that my pinnacle 300i could accept full resolution settings:
> v4l2-ctl --set-fmt-video=width=720,height=576
>
> only the first time the command is fired.
>
> after that, evey time i try to set that resolution with the same
>
On Fri, Feb 23, 2018 at 2:37 PM, Devin Heitmueller
wrote:
> On Fri, Feb 23, 2018 at 2:30 PM, Federico Allegretti
> wrote:
>> i noticed that my pinnacle 300i could accept full resolution settings:
>> v4l2-ctl --set-fmt-video=width=720,height=576
>>
>> only the first time the command is fired.
>>
>
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 Feb 24 05:00:16 CET 2018
media-tree git hash:a7bc5773cd166032e35e343dfb6067a93d8402d1
media_build git
40 matches
Mail list logo
