Hi,
On 05/13/2018 07:54 PM, Adam Baker wrote:
On 05/05/18 09:22, Hans de Goede wrote:
The recent "x86 ZONE_DMA love" discussion at LSF/MM pointed out that some
gspca sub-drivvers are using GFP_DMA to allocate buffers which are used
for USB bulk transfers, there is absolutely no need for this, d
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: Mon May 14 05:00:14 CEST 2018
media-tree git hash:2a5f2705c97625aa1a4e1dd4d584eaa05392e060
media_build gi
Mein Name ist Friedrich Mayrhofer und ich habe eine Spende von 2.800.000 Euro.
Ich brauche Sie für mich. Kontaktieren Sie mich unter
friedrichmayrhofer.foundat...@gmail.com
Hi Jacopo,
Thank you for the patch.
On Friday, 11 May 2018 12:59:37 EEST Jacopo Mondi wrote:
> Add R-Car R8A77995 SoC to the rcar-vin supported ones.
>
> Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
> ---
> drivers/media/platform/rcar-vin/rcar-core.c | 16
> 1
Hi Niklas,
Thank you for the patch.
On Sunday, 13 May 2018 22:00:23 EEST Niklas Söderlund wrote:
> Add the SoC specific information for Renesas r8a77965.
>
> Signed-off-by: Niklas Söderlund
Reviewed-by: Laurent Pinchart
> ---
> drivers/media/platform/rcar-vin/rcar-core.c | 48 ++
Hi Niklas,
Thank you for the patch.
On Sunday, 13 May 2018 22:19:17 EEST Niklas Söderlund wrote:
> A V4L2 driver for Renesas R-Car MIPI CSI-2 receiver. The driver
> supports the R-Car Gen3 SoCs where separate CSI-2 hardware blocks are
> connected between the video sources and the video grabbers (
Hi Niklas,
On Sunday, 13 May 2018 22:19:15 EEST Niklas Söderlund wrote:
> Hi,
>
> This is the latest incarnation of R-Car MIPI CSI-2 receiver driver. It's
> based on top of the media-tree and are tested on Renesas Salvator-X and
> Salvator-XS together with adv7482 and the now in tree rcar-vin dri
Em Mon, 14 May 2018 03:13:44 +0900
Akihiro TSUKADA escreveu:
> Hi,
> thanks for the review.
>
> >> +gl861_i2c_rawwrite(struct dvb_usb_device *d, u8 addr, u8 *wbuf, u16
> >> wlen)>> +{>> +u8 *buf;>> +int ret;>> +>> +buf =
> >> kmalloc(wlen, GFP_KERNEL);>> +if (!buf)>> +
A V4L2 driver for Renesas R-Car MIPI CSI-2 receiver. The driver
supports the R-Car Gen3 SoCs where separate CSI-2 hardware blocks are
connected between the video sources and the video grabbers (VIN).
Driver is based on a prototype by Koji Matsuoka in the Renesas BSP.
Signed-off-by: Niklas Söderlu
Documentation for Renesas R-Car MIPI CSI-2 receiver. The CSI-2 receivers
are located between the video sources (CSI-2 transmitters) and the video
grabbers (VIN) on Gen3 of Renesas R-Car SoC.
Each CSI-2 device is connected to more than one VIN device which
simultaneously can receive video from the
Hi,
This is the latest incarnation of R-Car MIPI CSI-2 receiver driver. It's
based on top of the media-tree and are tested on Renesas Salvator-X and
Salvator-XS together with adv7482 and the now in tree rcar-vin driver :-)
I hope this is the last incarnation of this patch-set, I do think it is
r
Hi Laurent,
On 2018-04-28 19:01:37 +0300, Laurent Pinchart wrote:
> Hi Niklas,
>
> On Friday, 27 April 2018 02:28:32 EEST Niklas Söderlund wrote:
> > On 2018-04-27 00:30:25 +0300, Laurent Pinchart wrote:
> > > On Thursday, 26 April 2018 23:21:21 EEST Niklas Söderlund wrote:
> > >> A V4L2 driver f
On 05/05/18 09:22, Hans de Goede wrote:
> The recent "x86 ZONE_DMA love" discussion at LSF/MM pointed out that some
> gspca sub-drivvers are using GFP_DMA to allocate buffers which are used
> for USB bulk transfers, there is absolutely no need for this, drop it.
>
The documentation for kmalloc()
Add the SoC specific information for Renesas r8a77965.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 48 +
1 file changed, 48 insertions(+)
diff --git a/drivers/media/platform/rcar-vin/rcar-core.c
b/drivers/media/platform/rcar-vin/rcar-co
Signed-off-by: Niklas Söderlund
---
Documentation/devicetree/bindings/media/rcar_vin.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
b/Documentation/devicetree/bindings/media/rcar_vin.txt
index a19517e1c669eb35..c2c57dcf73f4851b 100644
Hi,
thanks for the review.
>> +gl861_i2c_rawwrite(struct dvb_usb_device *d, u8 addr, u8 *wbuf, u16 wlen)>>
>> +{>> + u8 *buf;>> +int ret;>> +>> +buf = kmalloc(wlen,
>> GFP_KERNEL);>> +if (!buf)>> + return -ENOMEM;>> +>> +
>> usleep_range(1000, 2000); /* avoid I2C erro
Hi Simon,
Thanks for your patch.
On 2018-05-09 20:45:58 +0200, Simon Horman wrote:
> The example vin port node does not have an address and thus does not
> need address-cells or address size-properties.
>
> Signed-off-by: Simon Horman
Acked-by: Niklas Söderlund
> ---
> Documentation/devicet
Hi Mauro,
Here is a fix for the lirc docs warning, a fix for the topseed mceusb
device which did not like having its IR timeout set, and some patches
which validate the IR raw events drivers produce.
Thanks
Sean
The following changes since commit 2a5f2705c97625aa1a4e1dd4d584eaa05392e060:
medi
Any spaces events received after a reset or startup should be discarded,
so ensure the rc device is in idle mode.
This also makes it much easier to detect incorrect raw events, as we will
do in a following commit.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-ir-raw.c | 1 +
include/media/r
Hi Sean,
On Thu, May 10, 2018 at 01:01:34PM +0200, Matthias Reichl wrote:
> On Wed, May 09, 2018 at 10:44:42PM +0100, Sean Young wrote:
> > On Mon, May 07, 2018 at 05:54:55PM +0200, Matthias Reichl wrote:
> > > The original reporter gave up before I could get enough info
> > > to understand what's
Hi Sean,
On Fri, May 11, 2018 at 09:36:48AM +0100, Sean Young wrote:
> A mceusb device has been observed producing invalid irdata. Proactively
> guard against this.
Thanks a lot, the patch series looks good to me! Good catch on the
missing break BTW.
We've included this patch in LibreELEC testbu
The minimum possible timeout of ite-cir is 8 samples, which is
typically about 70us. The driver however changes the FIFO trigger
level from the hardware's default of 1 byte to 17 bytes, so the minimum
usable timeout value is 17 * 8 samples, which is typically about 1.2ms.
Tests showed that using t
From: Hans Verkuil
This driver hasn't been tested in a long, long time. The hardware is
ancient and pretty much obsolete. This driver also needs to be converted
to newer media frameworks (vb2!) but due to the lack of time and interest
that is unlikely to happen.
So this driver is a prime candida
From: Hans Verkuil
Since we're going to deprecate the zoran driver (and remove it in a
year), I thought that this is a good time to look at some other
drivers that 1) do not use the proper frameworks (vb2!) and 2) are
for ancient hardware for which there are easily available working
alternatives.
From: Hans Verkuil
This driver hasn't been tested in a long, long time. The hardware is
ancient and pretty much obsolete. This driver also needs to be converted
to newer media frameworks (vb2!) but due to the lack of time and interest
that is unlikely to happen.
So this driver is a prime candida
From: Hans Verkuil
This driver hasn't been tested in a long, long time. The hardware is
ancient and pretty much obsolete. This driver also needs to be converted
to newer media frameworks (vb2!) but due to the lack of time and interest
that is unlikely to happen.
So this driver is a prime candida
Great to see an OK here! And it's going to change to warnings for the
next build: I've updated the compiler to gcc-8.1.
A quick look at the warnings shows mostly warnings of this type:
warning: '__builtin_strncpy' output truncated copying 15 bytes from a string of
length 17 [-Wstringop-truncatio
From: Hans Verkuil
Zero the reserved capture/output array.
Zero the extendedmode (it is never used in drivers).
Clear all flags in capture/outputmode except for V4L2_MODE_HIGHQUALITY,
as that is the only valid flag.
Signed-off-by: Hans Verkuil
Reviewed-by: Hans de Goede
---
drivers/media/v4
From: Hans Verkuil
Signed-off-by: Hans Verkuil
Reviewed-by: Hans de Goede
---
drivers/media/usb/gspca/Kconfig| 1 +
drivers/media/usb/gspca/gspca.c| 900 -
drivers/media/usb/gspca/gspca.h| 38 +-
drivers/media/usb/gspca/m5602/m5602_cor
From: Hans Verkuil
The last user of this 'feature' was the gspca driver. Now that
that driver has been converted to vb2 we can delete this code.
Signed-off-by: Hans Verkuil
Reviewed-by: Hans de Goede
---
drivers/media/v4l2-core/v4l2-ioctl.c | 2 --
include/media/v4l2-dev.h | 15 -
From: Hans Verkuil
Fix v4l2-compliance error: s_parm never set V4L2_CAP_TIMEPERFRAME.
Also various g/s_parm-related cleanups.
Signed-off-by: Hans Verkuil
Reviewed-by: Hans de Goede
---
drivers/media/usb/gspca/gspca.c | 29 -
drivers/media/usb/gspca/ov534.c | 1 -
From: Hans Verkuil
The first patch converts the gspca driver to the vb2 framework.
It was much easier to do than I expected and it saved almost 600
lines of gspca driver code.
The second patch fixes v4l2-compliance warnings for g/s_parm.
The third patch clears relevant fields in v4l2_streamparm
Hi,
On 05/13/2018 11:32 AM, Hans Verkuil wrote:
On 05/12/2018 08:00 PM, Hans de Goede wrote:
Hi Hans,
Overall looks good, 1 comment inline.
- if (ret == 0 && gspca_dev->sd_desc->dq_callback) {
- mutex_lock(&gspca_dev->usb_lock);
- gspca_dev->usb_err = 0;
-
On 05/12/2018 08:00 PM, Hans de Goede wrote:
> Hi Hans,
>
> Overall looks good, 1 comment inline.
>
>> -if (ret == 0 && gspca_dev->sd_desc->dq_callback) {
>> -mutex_lock(&gspca_dev->usb_lock);
>> -gspca_dev->usb_err = 0;
>> -if (gspca_dev->present)
>> -
Hi Luca,
My apologies for the long delay in reviewing this.
It all looks very good and if you can post a v2 with these small issues
fixed, then I'll merge it for 4.18.
Regards,
Hans
On 05/13/2018 11:13 AM, Hans Verkuil wrote:
> On 04/03/2018 11:15 PM, Luca Ceresoli wrote:
>
> Please a
On 04/03/2018 11:15 PM, Luca Ceresoli wrote:
> These files have an automatically-generated numbering. Replaname them
Replaname -> Replace
> to something that suggests their meaning.
to -> with
Regards,
Hans
>
> Reported-by: Hans Verkuil
> Cc: Hans Verkuil
> Signed-off-by: Luca Cere
On 04/03/2018 11:15 PM, Luca Ceresoli wrote:
Please add a commit message here. Yes, it can be as simple as 'Fixed typos in
the
selection documentation.'
Regards,
Hans
> Cc: Hans Verkuil
> Signed-off-by: Luca Ceresoli
> ---
> Documentation/media/uapi/v4l/selection-api-004.rst | 2 +-
On 04/03/2018 11:15 PM, Luca Ceresoli wrote:
> Having two somewhat similar and largely overlapping APIs is confusing,
> especially since the older one appears in the docs before the newer
> and most featureful counterpart.
>
> Clarify all of this in several ways:
> - swap the two sections
> - gi
Hello Brad!
> Are the build logs public?
Look for the eMail
cron job: media_tree daily build: ?
The ? is OK, WARNINGS or ERRORS
In this eMail there are links to the short and long logfile.
Hans uses a complete build system which can download the Kernel sources, build
media-build agai
39 matches
Mail list logo