I did test the patch and while it doesn't seem to introduce any
negative side effects it does not provide a remedy for the original
problem that was seen after introducing
9d659ae14b545c4296e812c70493bfdc999b5c1c (you probably did not expect
that either).
Cheers,
-olli
On 27 April 2018 at 18:33,
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 Apr 28 05:00:11 CEST 2018
media-tree git hash:a2b2eff6ac2716f499defa590a6ec4ba379d765e
media_build gi
FYI: About My Previous Message
Hi,
Am Mrs Patricia William, i just want to know if you receive my
previous email i sent to you last three (3) days ago.
Is your email still Active? If YES; please can you email me back,
i have something very important to discuss with you.
Awaits your reply soon
On Sat, Apr 28, 2018 at 12:46:47AM +0300, Laurent Pinchart wrote:
> All source files of the vsp1 driver are licensed under the GPLv2+ except
> for vsp1_regs.h which is licensed under GPLv2. This is caused by a bad
> copy&paste that dates back from the initial version of the driver. Fix
> it.
>
> C
On 27/04/18 22:46, Laurent Pinchart wrote:
> All source files of the vsp1 driver are licensed under the GPLv2+ except
> for vsp1_regs.h which is licensed under GPLv2. This is caused by a bad
> copy&paste that dates back from the initial version of the driver. Fix
> it.
>
> Cc: Nobuhiro Iwamatsu
>
Hi Kieran,
On Saturday, 28 April 2018 00:25:51 EEST Kieran Bingham wrote:
> Hi Laurent,
>
> Thank you for the patch, and going through the whole driver for this update.
> On 22/04/18 23:34, Laurent Pinchart wrote:
> > Adopt the SPDX license identifier headers to ease license compliance
> > manage
All source files of the vsp1 driver are licensed under the GPLv2+ except
for vsp1_regs.h which is licensed under GPLv2. This is caused by a bad
copy&paste that dates back from the initial version of the driver. Fix
it.
Cc: Nobuhiro Iwamatsu
Cc: Kieran Bingham
Cc: Sergei Shtylyov
Cc: Niklas Söde
Hi Laurent,
Thank you for the patch, and going through the whole driver for this update.
On 22/04/18 23:34, Laurent Pinchart wrote:
> Adopt the SPDX license identifier headers to ease license compliance
> management. All files in the driver are licensed under the GPLv2+ except
> for the vsp1_regs
On Thu, Apr 26, 2018 at 08:24:42PM +0200, Jacopo Mondi wrote:
> 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
This change fixes function types for media device ioctls to avoid
indirect call mismatches with Control-Flow Integrity checking.
Signed-off-by: Sami Tolvanen
---
drivers/media/media-device.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers/media
On Mon, Apr 23, 2018 at 02:47:43PM +0100, Rui Miguel Silva wrote:
> Add bindings documentation for i.MX7 media drivers.
>
> Signed-off-by: Rui Miguel Silva
> ---
> .../devicetree/bindings/media/imx7.txt| 158 ++
> 1 file changed, 158 insertions(+)
> create mode 100644 Do
This change fixes indirect call mismatches with Control-Flow Integrity
checking, which are caused by calling standard ioctls using a function
pointer that doesn't match the type of the actual function.
Signed-off-by: Sami Tolvanen
---
drivers/media/v4l2-core/v4l2-ioctl.c | 72 ++-
Em Fri, 27 Apr 2018 20:15:00 +0200
"Jasmin J." escreveu:
> Hello Mauro!
>
> > This patch looks fine, but not for the above-mentioned.
> So I shall reword the commit message?
Yes.
>
> > The thing is that it is not consistent to have some places with
> > things like:
> > timeout = ktime_se
Hello Mauro!
> This patch looks fine, but not for the above-mentioned.
So I shall reword the commit message?
> The thing is that it is not consistent to have some places with
> things like:
> timeout = ktime_set(1, ir->polling * 100);
>
> and others with:
> timeout = ir->polling
2018-04-23 17:35 GMT+09:00 jacopo mondi :
> Hi Akinobu,
>thanks for v3
>
> On Mon, Apr 23, 2018 at 12:56:13AM +0900, Akinobu Mita wrote:
>> Depending on the v4l2 driver, calling s_power() could be nested. So the
>> actual transitions between power saving mode and normal operation mode
>> shoul
2018-04-27 6:34 GMT+09:00 Laurent Pinchart :
> Hi Mita-san,
>
> On Thursday, 26 April 2018 19:17:55 EEST Akinobu Mita wrote:
>> 2018-04-26 7:40 GMT+09:00 Laurent Pinchart:
>> > On Wednesday, 25 April 2018 19:19:11 EEST Akinobu Mita wrote:
>> >> 2018-04-24 0:54 GMT+09:00 Akinobu Mita :
>> >> > 2018-
Em Fri, 27 Apr 2018 16:25:08 +0200
Olli Salonen escreveu:
> Thanks for the suggestion Antti.
>
> I've tried to add a delay in various places, but haven't seen any
> improvement. However, what I did saw was that if I added an msleep
> after the lock:
>
> static int dvbsky_usb_generic_rw(struct d
Instead of duplicating the same code, call into coda_s_fmt_vid_out to
propagate the output format to the capture queue.
Signed-off-by: Philipp Zabel
---
Changes since v1 [1]:
- split out into a separate patch
[1] https://patchwork.linuxtv.org/patch/48266/
This is what coda_s_fmt_vid_cap curren
Do not set context colorimetry on the raw (OUTPUT) queue for encoders.
Always set colorimetry on the coded queue (CAPTURE for encoders, OUTPUT
for decoders).
This also skips propagation of capture queue format and selection
rectangle on S_FMT(OUTPUT) to the CAPTURE queue for encoders.
Signed-off-b
The driver helpfully resets the capture queue format and selection
rectangle whenever output format is changed. This only works while
the capture queue is not busy.
Signed-off-by: Philipp Zabel
---
Changes since v1 [1]:
- split out into a separate patch
[1] https://patchwork.linuxtv.org/patch/4
Thanks for the suggestion Antti.
I've tried to add a delay in various places, but haven't seen any
improvement. However, what I did saw was that if I added an msleep
after the lock:
static int dvbsky_usb_generic_rw(struct dvb_usb_device *d,
u8 *wbuf, u16 wlen, u8 *rbuf, u16 rlen)
I found a Hauppauge WinTV 44981 (bt878) with a Zilog Z8F0811. The
transmitter was not probed. Most likely there are others like this
(e.g. HVR1110).
Signed-off-by: Sean Young
---
drivers/media/i2c/ir-kbd-i2c.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i
On Thu, Jun 08, 2017 at 01:22:59AM +0300, Sakari Ailus wrote:
> Hi Hans,
>
> On Tue, Jun 06, 2017 at 10:28:26AM +0200, Hans Verkuil wrote:
> > On 05/06/17 22:39, Yong Zhi wrote:
> >
> > Commit message missing.
> >
> > > Signed-off-by: Yong Zhi
> > > ---
> > > include/uapi/linux/intel-ipu3.h |
Replace the manual validity checks for the GPIO with the
gpio_is_valid().
Arvind Yadav (2):
[PATCH 1/2] [media] platform: Use gpio_is_valid()
[PATCH 2/2] [media] sta2x11: Use gpio_is_valid() and remove unnecessary check
drivers/media/pci/sta2x11/sta2x11_vip.c | 31 +++
Replace the manual validity checks for the GPIO with the
gpio_is_valid().
In vip_gpio_reserve(), Error checking for gpio pin is not correct.
If pwr_pin = -1, It will return 0. This should be return an error.
In sta2x11_vip_init_one(), Error checking for gpio 'reset_pin'
is unnecessary. Because vi
Replace the manual validity checks for the GPIO with the
gpio_is_valid().
Signed-off-by: Arvind Yadav
---
drivers/media/platform/via-camera.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/via-camera.c
b/drivers/media/platform/via-camera.c
index e9a02
The code will be called MEDIA_BUS_FMT_Y10_2X8_PADHI_LE.
It is similar to MEDIA_BUS_FMT_SBGGR10_2X8_PADHI_LE
but MEDIA_BUS_FMT_Y10_2X8_PADHI_LE describes grayscale
data.
Signed-off-by: Todor Tomov
---
Documentation/media/uapi/v4l/subdev-formats.rst | 72 +
include/uapi/lin
The new format will be called V4L2_PIX_FMT_Y10P.
It is similar to the V4L2_PIX_FMT_SBGGR10P family formats
but V4L2_PIX_FMT_Y10P is a grayscale format.
Signed-off-by: Todor Tomov
---
Documentation/media/uapi/v4l/pixfmt-y10p.rst | 31
Documentation/media/uapi/v4l/yuv-
The following two patches add one new media bus code and one new pixel format.
Both are for 10bit grayscale data. They will be used by the future version of
the QComm CAMSS driver when receiving the frame data from the OV7251 grayscale
camera sensor.
Todor Tomov (2):
media: v4l: Add new 2X8 10-b
Hi Sam,
On Wednesday, 25 April 2018 01:11:19 EEST 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. It also
> seems that the output of the P divider cell, SCLK cell and MIPI Rate
> cell in the
30 matches
Mail list logo