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: Wed Jan 10 05:00:15 CET 2018
media-tree git hash:e3ee691dbf24096ea51b3200946b11d68ce75361
media_build git
On Tue, 2018-01-09 at 22:26 +0100, Jesper Dangaard Brouer wrote:
>
> I've previously experienced that you can be affected by the scheduler
> granularity, which is adjustable (with CONFIG_SCHED_DEBUG=y):
>
> $ grep -H . /proc/sys/kernel/sched_*_granularity_ns
> /proc/sys/kernel/sched_min_granula
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:
- output 1600x1200 at 30fps
- test patterns
- manual exposure/gain control
- vblank and hblank
- media controller
Add device tree binding documentation for the OV2685 sensor.
Signed-off-by: Shunqian Zheng
---
.../devicetree/bindings/media/i2c/ov2685.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2685.txt
diff --git a
This adds the OV2685 and OV5695 sensor supports.
Changes of v5,
- Squash the MAINTAINERS entry to driver patch
Mainly changes of v4 are addressing the comments from Sakari,
including,
- Put dt binding before driver in series
- Add MAINTAINERS entries
- Use regulator_bulk_*()
- Fix the pm_run
Add device tree binding documentation for the OV5695 sensor.
Signed-off-by: Shunqian Zheng
---
.../devicetree/bindings/media/i2c/ov5695.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
diff --git a
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
+ 640x480 at 120fps
- test patterns
- manual exposure/gain(analog and digital) c
On 2018/1/9 21:46, Nicolas Ferre wrote:
Update Wenyou Yang email address.
Take advantage of this update to move this entry to the MICROCHIP / ATMEL
location and add the DT binding documentation link.
Signed-off-by: Nicolas Ferre
Acked-by: Wenyou Yang
---
Hi,
Patch against next-20180109
: Nicolas Ferre
Acked-by: Wenyou Yang
---
Hi,
Patch against next-20180109.
Note that I didn't find it useful to have several patches for these changes.
Tell me if you feel differently.
I would like to have the Ack from Ludovic and Wenyou obviously. I don't know if
Songjun can answer a
Hi Baruch,
On 2018年01月10日 00:54, Baruch Siach wrote:
Hi Shunqian Zheng,
On Tue, Jan 09, 2018 at 10:48:21PM +0800, Shunqian Zheng wrote:
+static int ov5695_write_array(struct i2c_client *client,
+ const struct regval *regs)
+{
+ u32 i;
+ int ret = 0;
+
+
s/pci-dma-compat: remove handling of NULL pdev
/PCI: Remove NULL device handling from DMA API/
On Tue, Jan 09, 2018 at 09:39:39PM +0100, Christoph Hellwig wrote:
> Historically some ISA drivers used the old pci DMA API with a NULL pdev
> argument, but these days this isn't used and not too useful
On Tue, Jan 09, 2018 at 09:39:37PM +0100, Christoph Hellwig wrote:
> Switch to a plain kzalloc instea of pci_zalloc_coherent to allocate
> memory for the USB DMA.
s/instea/instead/
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/media/usb/ttusb-budget/dvb-ttusb-budget.c | 13 +++--
Commit f8585ce655e9cdeabc38e8e2580b05735110e4a5 ("[media] dvb-usb-cxusb:
Geniatech T230C support") sneaked in an unrelated change for the older
T230 (not C) model. As the commit was reverted this change was reverted
too, although likely correct.
Signed-off-by: Stefan Brüns
---
drivers/media/us
From: Evgeny Plehov
This reverts commit f8585ce655e9cdeabc38e8e2580b05735110e4a5.
The T230C is handled by the dvb-usb-v2/dvbsky.c driver, which should
be preferred over a dvb-usb (v1) driver.
Signed-off-by: Stefan Brüns
---
drivers/media/usb/dvb-usb/cxusb.c | 139 +---
In 2017-02, two drivers for the T230C where submitted, but until now
only the one based on the older dvb-usb/cxusb.c driver has been part
of the mainline kernel. As a dvb-usb-v2 driver is preferable, remove
the other driver.
The cxusb.c patch also contained an unrelated change for the T230,
i.e.
Hi Alan,
On Mon, Jan 08, 2018 at 02:26:39PM +, Alan Cox wrote:
> On Mon, 8 Jan 2018 16:21:21 +0200
> Sakari Ailus wrote:
>
> > Hi Mauro,
> >
> > On Thu, Jan 04, 2018 at 02:44:41PM -0500, Mauro Carvalho Chehab wrote:
> > > There are lots of bad whitespaces at atomisp driver.
> > >
> > > Fix
Hi Mauro,
Here's a PM fix and a small cleanup for the dw9714 driver.
Please pull.
The following changes since commit e3ee691dbf24096ea51b3200946b11d68ce75361:
media: ov5640: add support of RGB565 and YUYV formats (2018-01-05 12:54:14
-0500)
are available in the git repository at:
ssh://
Hi Mauro,
Here's compile warning fix for the Intel IPU3 CIO2 driver from Arnd.
Please pull.
The following changes since commit e3ee691dbf24096ea51b3200946b11d68ce75361:
media: ov5640: add support of RGB565 and YUYV formats (2018-01-05 12:54:14
-0500)
are available in the git repository at:
On Tue, Jan 09, 2018 at 10:48:24PM +0800, Shunqian Zheng wrote:
> Add maintainer entries for the OV2685 and OV5695 V4L2 sensor drivers.
>
> Signed-off-by: Shunqian Zheng
Same patch with the driver, please.
Other than that seems good to me.
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
Hi Arnd,
On Tue, Jan 09, 2018 at 03:26:38PM +0100, Arnd Bergmann wrote:
> On Tue, Jan 9, 2018 at 2:58 PM, Sakari Ailus
> wrote:
> > Add nop variant of media_entity_cleanup. This allows calling
> > media_entity_cleanup whether or not Media controller is enabled,
> > simplifying driver code.
> >
>
Hi Shunqian,
On Tue, Jan 09, 2018 at 10:52:30PM +0800, Shunqian Zheng wrote:
> Hi Sakari,
>
>
> On 2018年01月09日 06:20, Sakari Ailus wrote:
> > Hi Shunqian,
> >
> > Could you next time add a cover page to the patchset that details the
> > changes from the previous version?
> >
> > Please also ad
On Tue, Jan 9, 2018 at 10:58 AM, Linus Torvalds
wrote:
> On Tue, Jan 9, 2018 at 9:57 AM, Eric Dumazet wrote:
>>
>> Your patch considers TASKLET_SOFTIRQ being a candidate for 'immediate
>> handling', but TCP Small queues heavily use TASKLET,
>> so as far as I am concerned a revert would have the s
On Tue, 9 Jan 2018 15:42:35 -0200 Mauro Carvalho Chehab
wrote:
> Em Mon, 8 Jan 2018 11:51:04 -0800 Linus Torvalds
> escreveu:
>
[...]
> Patch makes sense to me, although I was not able to test it myself.
The patch also make sense to me. I've done some basic testing with it
on my high-end B
On Tue, Jan 09, 2018 at 11:44:05AM -0800, Dan Williams wrote:
> On Tue, Jan 9, 2018 at 11:34 AM, Jiri Kosina wrote:
> > On Fri, 5 Jan 2018, Dan Williams wrote:
> >
> > [ ... snip ... ]
> >> Andi Kleen (1):
> >> x86, barrier: stop speculation for failed access_ok
> >>
> >> Dan Williams (13):
On Tue, 2018-01-09 at 21:39 +0100, Christoph Hellwig wrote:
> Switch to a plain kzalloc instea of pci_zalloc_coherent to allocate
> memory for the USB DMA.
[]
> diff --git a/drivers/media/usb/ttusb-budget/dvb-ttusb-budget.c
> b/drivers/media/usb/ttusb-budget/dvb-ttusb-budget.c
[]
> @@ -792,21 +791
Switch to a plain kzalloc instea of pci_zalloc_coherent to allocate
memory for the USB DMA.
Signed-off-by: Christoph Hellwig
---
drivers/media/usb/ttusb-dec/ttusb_dec.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/media/usb/ttusb-dec/ttusb_dec.c
b/d
Switch to a plain kzalloc instea of pci_zalloc_coherent to allocate
memory for the USB DMA.
Signed-off-by: Christoph Hellwig
---
drivers/media/usb/ttusb-budget/dvb-ttusb-budget.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/media/usb/ttusb-budget/dvb
Historically some ISA drivers used the old pci DMA API with a NULL pdev
argument, but these days this isn't used and not too useful due to the
per-device DMA ops, so remove it.
Signed-off-by: Christoph Hellwig
---
include/linux/pci-dma-compat.h | 27 +--
1 file changed, 1
Back before the dawn of time pci_dma_* with a NULL pci_dev argument
was used for all kinds of things, e.g. dma mapping for non-PCI
devices. All this has been long removed, but it turns out we
still care for a NULL pci_dev in the wrappers, and we still have
two odd USB drivers that use pci_dma_allo
On Fri, 5 Jan 2018, Dan Williams wrote:
[ ... snip ... ]
> Andi Kleen (1):
> x86, barrier: stop speculation for failed access_ok
>
> Dan Williams (13):
> x86: implement nospec_barrier()
> [media] uvcvideo: prevent bounds-check bypass via speculative execution
> carl9170: p
On Tue, Jan 9, 2018 at 11:34 AM, Jiri Kosina wrote:
> On Fri, 5 Jan 2018, Dan Williams wrote:
>
> [ ... snip ... ]
>> Andi Kleen (1):
>> x86, barrier: stop speculation for failed access_ok
>>
>> Dan Williams (13):
>> x86: implement nospec_barrier()
>> [media] uvcvideo: prevent bo
On Tue, Jan 9, 2018 at 9:57 AM, Eric Dumazet wrote:
>
> Your patch considers TASKLET_SOFTIRQ being a candidate for 'immediate
> handling', but TCP Small queues heavily use TASKLET,
> so as far as I am concerned a revert would have the same effect.
Does it actually?
TCP ends up dropping packets o
Hi Hugues,
On Mon, Jan 08, 2018 at 05:13:39PM +, Hugues FRUCHET wrote:
> I'm using a ST board with OV5640 wired in parallel bus output in order
> to interface to my STM32 DCMI parallel interface.
> Perhaps could you describe your setup so I could help on understanding
> the problem on your s
On Tue, Jan 9, 2018 at 9:48 AM, Linus Torvalds
wrote:
> On Tue, Jan 9, 2018 at 9:27 AM, Eric Dumazet wrote:
>>
>> So yes, commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job") has
>> shown up multiple times in various 'regressions'
>> simply because it could surface the problem more often.
>>
On Tue, Jan 9, 2018 at 9:42 AM, Mauro Carvalho Chehab
wrote:
>
> On my preliminar tests, writing to a file on an ext4 partition at a
> USB stick loses data up to the point to make it useless (1/4 of the data
> is lost!). However, writing to a class 10 microSD card is doable.
Note that most USB st
On Tue, Jan 9, 2018 at 9:27 AM, Eric Dumazet wrote:
>
> So yes, commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job") has
> shown up multiple times in various 'regressions'
> simply because it could surface the problem more often.
> But even if you revert it, you can still make the faulty
> dr
Em Mon, 8 Jan 2018 11:51:04 -0800
Linus Torvalds escreveu:
> On Mon, Jan 8, 2018 at 11:15 AM, Alan Stern wrote:
> >
> > Both dwc2_hsotg and ehci-hcd use the tasklets embedded in the
> > giveback_urb_bh member of struct usb_hcd. See usb_hcd_giveback_urb()
> > in drivers/usb/core/hcd.c; the calls
On Tue, Jan 9, 2018 at 8:51 AM, Josef Griebichler
wrote:
> Hi Linus,
>
> your patch works very good for me and others (please see
> https://forum.libreelec.tv/thread/4235-dvb-issue-since-le-switched-to-kernel-4-9-x/?postID=77006#post77006).
> No errors in recordings any more.
> The patch was als
Hi Shunqian Zheng,
On Tue, Jan 09, 2018 at 10:48:21PM +0800, Shunqian Zheng wrote:
> +static int ov5695_write_array(struct i2c_client *client,
> + const struct regval *regs)
> +{
> + u32 i;
> + int ret = 0;
> +
> + for (i = 0; ret == 0 && regs[i].addr != REG_N
Hi Linus,
your patch works very good for me and others (please see
https://forum.libreelec.tv/thread/4235-dvb-issue-since-le-switched-to-kernel-4-9-x/?postID=77006#post77006).
No errors in recordings any more.
The patch was also tested on x86_64 (Revo 3700) with positive effect.
I agree with the
Hauppauge HVR-975 is hybrid NTSC/PAL, QAM/ATSC, and DVB-C/T/T2 usb device.
Only ATSC/QAM front end is initially active. Second frontend support is
work in progress.
CX23102 + LG3306A/Si2168(WiP) + Si2157
Changes since v1:
- removed double semicolon
Signed-off-by: Brad Love
---
drivers/media/
Hauppauge HVR-975 is hybrid NTSC/PAL, QAM/ATSC, and DVB-C/T/T2 usb device.
Only ATSC/QAM front end is initially active. Second frontend support is
work in progress.
CX23102 + LG3306A/Si2168(WiP) + Si2157
Signed-off-by: Brad Love
---
drivers/media/usb/cx231xx/cx231xx-cards.c | 42 ++
HVR-935C is hybrid PAL, DVB-C/T/T2 usb device.
CX23102 + Si2168 + Si2157
Signed-off-by: Brad Love
---
drivers/media/usb/cx231xx/cx231xx-cards.c | 42 +
drivers/media/usb/cx231xx/cx231xx-dvb.c | 75 +++
drivers/media/usb/cx231xx/cx231xx.h | 1
Included is support for the following two USB devices:
- Hauppauge USB HVR935C - DVB-C/T/T2 + analog
- Hauppauge USB HVR975 - ATSC/QAM + analog
Brad Love (2):
cx231xx: Add support for Hauppauge HVR-935
cx231xx: Add support for Hauppauge HVR-975
drivers/media/usb/cx231xx/cx231xx-cards.c | 84
Add bindings documentation for Renesas Capture Engine Unit (CEU).
Signed-off-by: Jacopo Mondi
---
.../devicetree/bindings/media/renesas,ceu.txt | 81 ++
1 file changed, 81 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/renesas,ceu.txt
diff --g
Add renesas-ceu header file.
Do not remove the existing sh_mobile_ceu.h one as long as the original
driver does not go away.
Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
---
include/media/drv-intf/renesas-ceu.h | 26 ++
1 file changed, 26 insertions(+)
cre
Add driver for Renesas Capture Engine Unit (CEU).
The CEU interface supports capturing 'data' (YUV422) and 'images'
(NV[12|21|16|61]).
This driver aims to replace the soc_camera-based sh_mobile_ceu one.
Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ
platform GR-Peach.
T
Remove soc_camera framework dependencies from ov772x sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Change image format colorspace from JPEG to SRGB as the two use the
same colorspace information but JPEG makes assumpti
Add Capture Engine Unit (CEU) node to device tree.
Signed-off-by: Jacopo Mondi
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Laurent Pinchart
---
arch/arm/boot/dts/r7s72100.dtsi | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/r7s72100.dtsi
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Remove soc_camera framework dependencies from tw9910 sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Add kernel doc to driver interface header file
- Adjust build system
This commit does not remove the original soc_camera
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Migo-R platform uses sh_mobile_ceu camera driver, which is now being
replaced by a proper V4L2 camera driver named 'renesas-ceu'.
Move Migo-R platform to use the v4l2 renesas-ceu camera driver
interface and get rid of soc_camera defined components used to register
sensor drivers and of platform sp
Hello,
fourth round for Renesas CEU unit.
The only notable change compared to v3 is that we have dropped the generic
fallback compatible string "renesas,ceu" from bindings and CEU driver.
Apart from that a few minor changes in driver code as reported by Laurent and
below listed.
Most of the p
Hi Sakari,
On 2018年01月09日 06:20, Sakari Ailus wrote:
Hi Shunqian,
Could you next time add a cover page to the patchset that details the
changes from the previous version?
Please also add a MAINTAINERS entry. DT binding files should also precede
the driver.
Done.
By the way, why DT binding fi
This adds the OV2685 and OV5695 sensor supports.
Mainly changes of v4 are addressing the comments from Sakari,
including,
- Put dt binding before driver in series
- Add MAINTAINERS entries
- Use regulator_bulk_*()
- Fix the pm_runtime_* in probe()
- Fix the typo of 2685 0x3008/0x3010 regs
Sh
Add device tree binding documentation for the OV5695 sensor.
Signed-off-by: Shunqian Zheng
---
.../devicetree/bindings/media/i2c/ov5695.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
diff --git a
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
+ 640x480 at 120fps
- test patterns
- manual exposure/gain(analog and digital) c
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:
- output 1600x1200 at 30fps
- test patterns
- manual exposure/gain control
- vblank and hblank
- media controller
Add device tree binding documentation for the OV2685 sensor.
Signed-off-by: Shunqian Zheng
---
.../devicetree/bindings/media/i2c/ov2685.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2685.txt
diff --git a
Add maintainer entries for the OV2685 and OV5695 V4L2 sensor drivers.
Signed-off-by: Shunqian Zheng
---
MAINTAINERS | 14 ++
1 file changed, 14 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 85773bf..32afc69 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10032,6 +10032,1
On Tue, Jan 09, 2018 at 04:26:28PM +0200, Laurent Pinchart wrote:
> Hi Greg,
>
> On Tuesday, 9 January 2018 12:04:10 EET Greg KH wrote:
> > On Tue, Jan 09, 2018 at 10:40:21AM +0200, Laurent Pinchart wrote:
> > > On Saturday, 6 January 2018 11:40:26 EET Greg KH wrote:
> > >> On Sat, Jan 06, 2018 at
On Tue, Jan 9, 2018 at 2:58 PM, Sakari Ailus
wrote:
> Add nop variant of media_entity_cleanup. This allows calling
> media_entity_cleanup whether or not Media controller is enabled,
> simplifying driver code.
>
> Also drop #ifdefs on a few drivers around media_entity_cleanup() and drop
> the extra
Hi Greg,
On Tuesday, 9 January 2018 12:04:10 EET Greg KH wrote:
> On Tue, Jan 09, 2018 at 10:40:21AM +0200, Laurent Pinchart wrote:
> > On Saturday, 6 January 2018 11:40:26 EET Greg KH wrote:
> >> On Sat, Jan 06, 2018 at 10:09:07AM +0100, Greg KH wrote:
> >>
> >> While I'm all for fixing this typ
> MICROCHIP / ATMEL location.
>
> Signed-off-by: Nicolas Ferre
Acked-by: Ludovic Desroches
> ---
> Hi,
>
> Patch against next-20180109.
> Note that I didn't find it useful to have several patches for these changes.
> Tell me if you feel differently.
>
> I
Add nop variant of media_entity_cleanup. This allows calling
media_entity_cleanup whether or not Media controller is enabled,
simplifying driver code.
Also drop #ifdefs on a few drivers around media_entity_cleanup() and drop
the extra semicolon from media_entity_cleanup prototype.
Signed-off-by:
-20180109.
Note that I didn't find it useful to have several patches for these changes.
Tell me if you feel differently.
I would like to have the Ack from Ludovic and Wenyou obviously. I don't know if
Songjun can answer as he's not with Microchip anymore.
Best regards,
Nicolas
M
Update Wenyou Yang email address.
Take advantage of this update to move this entry to the MICROCHIP / ATMEL
location and add the DT binding documentation link.
Signed-off-by: Nicolas Ferre
---
Hi,
Patch against next-20180109.
This patch is somehow dependent on the previous one in the series
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 use a
uvc_urb pointer for
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_buffer() such that a re
Newer high definition cameras, and cameras with multiple lenses such as
the range of stereo-vision 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 destination 'manually'.
This
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
---
v2:
- fix checkpatch w
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 --
1 file cha
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() functions.
Signed-off-by: K
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 supported.
Cameras such as th
On Tue, Jan 9, 2018 at 12:17 AM, Matthias Schwarzott wrote:
> Am 05.01.2018 um 01:19 schrieb Michael Ira Krufky:
>> On Thu, Jan 4, 2018 at 7:04 PM, Brad Love wrote:
>>> If release is part of frontend ops then it is called in the
>>> course of dvb_frontend_detach. The process also decrements
>>> t
First of all a Happy New Year for all of you!
And secondly: can this v5 patch series be reviewed/merged? It's been waiting
for that for a very long time now...
Regards,
Hans
On 12/11/17 09:57, Hans Verkuil wrote:
> Ping again. Added a CC to Ville whom I inexplicably forgot to add when
>
Hello Hugues,
thank you for getting back to me, I'll look into your suggestions in the next
few days, I'll give you a feedback as soon as I know more.
Thanks,
Fab
> Subject: Re: [PATCH v5 0/5] Add OV5640 parallel interface and RGB565/YUYV
> support
>
> Hi Fabrizio,
>
> Happy to see that this p
On Tue, Jan 9, 2018 at 11:13 AM, Sakari Ailus
wrote:
> Hi Arnd,
>
> On Mon, Jan 08, 2018 at 01:52:28PM +0100, Arnd Bergmann wrote:
>> Without CONFIG_MEDIA_CONTROLLER, the new driver fails to build:
>>
>> drivers/perf/arm_dsu_pmu.c: In function 'dsu_pmu_probe_pmu':
>> drivers/perf/arm_dsu_pmu.c:661
Hi Arnd,
On Mon, Jan 08, 2018 at 01:52:28PM +0100, Arnd Bergmann wrote:
> Without CONFIG_MEDIA_CONTROLLER, the new driver fails to build:
>
> drivers/perf/arm_dsu_pmu.c: In function 'dsu_pmu_probe_pmu':
> drivers/perf/arm_dsu_pmu.c:661:2: error: implicit declaration of function
> 'bitmap_from_u3
On Tue, Jan 09, 2018 at 10:40:21AM +0200, Laurent Pinchart wrote:
> On Saturday, 6 January 2018 11:40:26 EET Greg KH wrote:
> > On Sat, Jan 06, 2018 at 10:09:07AM +0100, Greg KH wrote:
> >
> > While I'm all for fixing this type of thing, I feel like we need to do
> > something "else" for this as p
Hello Arnd,
On 2018/1/8 20:52, Arnd Bergmann wrote:
Without CONFIG_MEDIA_CONTROLLER, the new driver fails to build:
drivers/perf/arm_dsu_pmu.c: In function 'dsu_pmu_probe_pmu':
drivers/perf/arm_dsu_pmu.c:661:2: error: implicit declaration of function
'bitmap_from_u32array'; did you mean 'bitm
Reviewed-by: Wu-Cheng Li
On Tue, Jan 9, 2018 at 4:42 PM, Tomasz Figa wrote:
> Currently the driver signals the source change event only in case of
> a midstream resolution change, however the initial format detection
> is also defined as a source change by the V4L2 codec API specification.
> Fix
Hi Fabrizio,
Happy to see that this patch series is of interest ;)
As you can see in mail thread, Maxime Ripard is also testing it:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg124322.html
For BT656 support, it was not initially planned but it seems
straightforward to code it, an
Currently the driver signals the source change event only in case of
a midstream resolution change, however the initial format detection
is also defined as a source change by the V4L2 codec API specification.
Fix this by signaling the event after the initial header is parsed as
well.
Signed-off-by
Hi Greg,
On Saturday, 6 January 2018 11:40:26 EET Greg KH wrote:
> On Sat, Jan 06, 2018 at 10:09:07AM +0100, Greg KH wrote:
> > On Fri, Jan 05, 2018 at 05:10:32PM -0800, Dan Williams wrote:
> >> Static analysis reports that 'index' may be a user controlled value that
> >> is used as a data depende
On 05.01.2018 15:59, Maxime Ripard wrote:
Hi,
On Fri, Jan 05, 2018 at 12:02:53PM +, Sean Young wrote:
On Tue, Dec 19, 2017 at 09:07:41AM +0100, Philipp Rossak wrote:
This patch series adds support for the sunxi A83T ir module and enhances
the sunxi-ir driver. Right now the base clock fre
Hi Rob,
thanks for comments
On Mon, Jan 08, 2018 at 09:35:55PM -0600, Rob Herring wrote:
> On Thu, Jan 04, 2018 at 10:52:33AM +0100, Jacopo Mondi wrote:
> > Describe newly introduced OF properties for ov7670 image sensor.
> > The driver supports two standard properties to configure synchronism
88 matches
Mail list logo
