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 May 25 05:00:13 CEST 2019
media-tree git hash:2c41cc0be07b5ee2f1167f41cd8a86fc5b53d82c
media_build gi
There are cases that interrupt bits are cleared by a 500ms delayed
work which causes unnecessary irq calls. Also, the current
interrupt handler returns IRQ_HANDLED always but it should return
IRQ_NONE if there is any unhandled interrupt. So this commit
refines the interrupt handling logic to fix th
Mode detection doesn't require source buffer allocation so this
commit removes that.
Signed-off-by: Jae Hyun Yoo
---
v1 -> v2:
New.
drivers/media/platform/aspeed-video.c | 21 -
1 file changed, 21 deletions(-)
diff --git a/drivers/media/platform/aspeed-video.c
b/drivers/m
There is an incorrect timeout checking in mode detection logic so
it misses resolution detecting chances. This commit fixes the bug.
Signed-off-by: Jae Hyun Yoo
---
v1 -> v2:
New.
drivers/media/platform/aspeed-video.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/
In case of watchdog timeout detected while doing mode detection,
it's better triggering video engine hardware reset immediately so
this commit fixes code for the case. Other than the case, it will
trigger video engine hardware reset after RESOLUTION_CHANGE_DELAY.
Signed-off-by: Jae Hyun Yoo
---
v
Currently, this driver prints out too much log messages when a
mode change happens, video turned off by screen saver and etc.
Actually, all cases are reported to user space properly. Also,
these are not critical errors but recoverable things, so this
commit changes the log level of some noisy print
Video engine clock control can be double disabled and eventually
it causes a kernel warning with stack dump printing out like below:
[ 515.540498] [ cut here ]
[ 515.545174] WARNING: CPU: 0 PID: 1310 at drivers/clk/clk.c:684
clk_core_unprepare+0x13c/0x170
[ 515.553806]
Video Engine has a dedicated interrupt line so this driver doesn't
need to use IRQF_SHARED flag so remove it. Also, it'd be good for
following what Thomas recommended in the IRQF_ONESHOT support
patch like below:
"Note that for now IRQF_ONESHOT cannot be used with IRQF_SHARED to
avoid complex acco
Currently, this driver calls clk_prepare and clk_unprepare from
interrupt context too but these should be called from sleepable
context only. To fix this issue, this commit splits out
clk_enable/disable and clk_prepare/unprepare, and it places
clk_prepare/unprepare calls into the module probe/remov
Differently from other Aspeed drivers, this driver calls clock
control APIs in interrupt context. Since ECLK is coupled with a
reset bit in clk-aspeed module, aspeed_clk_enable will make 10ms of
busy waiting delay for triggering the reset and it will eventually
disturb other drivers' interrupt hand
VE_INTERRUPT_CAPTURE_COMPLETE and VE_INTERRUPT_COMP_COMPLETE are
not set at the same time but the current interrupt handling
mechanism of this driver doesn't clear the interrupt flag until
both two are set, and this behavior causes unnecessary interrupt
handler calls. In fact, this driver provides
This patch series improves stability of Aspeed video engine driver by fixing
clock control and irq handling logic in the driver. Also, it adds a couple of
bug fixes and a workaroud for a silicon bug.
Changes since v1:
- Removed spinlock handling code from 0001 patch.
- Added 4 more patches.
Jae H
AST2500 silicon revision A1 and A2 have a silicon bug which causes
extremly long capturing time on specific resolutions (1680 width).
To fix the bug, this commit adjusts the capturing window register
setting to 1728 if detected width is 1680. The compression window
register setting will be kept as
media/master v4l2-compliance on vivid: 236 tests, 0 regressions
(v5.2-rc1-55-g2c41cc0be07b)
Test results summary
V4L2 Compliance on the vivid driver.
This test ran "v4l2-compliance -s" from v4l-utils:
https://www.linuxtv.org/wiki/index.php/V4l2-utils
See each detailed
Hi Jungo,
On Fri, May 10, 2019 at 09:58:04AM +0800, Jungo Lin wrote:
> This patch adds the Mediatek ISP P1 HW control device driver.
> It handles the ISP HW configuration, provides interrupt handling and
> initializes the V4L2 device nodes and other functions.
A few comments inline.
>
> Signed-
Hi Jungo,
On Fri, May 10, 2019 at 09:58:02AM +0800, Jungo Lin wrote:
> Implement standard V4L2 video driver that utilizes V4L2
> and media framework APIs. In this driver, supports one media
> device, one sub-device and six video devices during
> initialization. Moreover, it also connects with sens
media/master v4l2-compliance on vivid: 236 tests, 0 regressions
(v5.2-rc1-53-g2f39cce96363)
Test results summary
V4L2 Compliance on the vivid driver.
This test ran "v4l2-compliance -s" from v4l-utils:
https://www.linuxtv.org/wiki/index.php/V4l2-utils
See each detailed
There are several other SoCs that contain Hantro IP based VPUs, such as
NXP i.MX8MQ (Hantro G1 and G2) and i.MX8MM (Hantro G1, G2, and H1). To
maximize code sharing, add initial support for these SoCs to the
Rockchip VPU driver, after renaming it to Hantro VPU.
This series is based on the for-v5.2
It seems that on i.MX8MQ the power domain controller does not propagate
resets to the VPU cores on resume. Add a callback to allow implementing
manual reset of the VPU cores after ungating the power domain.
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/hantro.h | 2 ++
drive
On i.MX8MQ/MM a separate control block contains registers for per-core
resets, clock gating, and fuse register control.
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/hantro.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/media/hantro/hantro.h
b/drivers/st
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/hantro_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/media/hantro/hantro_drv.c
b/drivers/staging/media/hantro/hantro_drv.c
index c1ed3a2eda3f..1d4d5ec8ab19 100644
--- a/drivers/staging/med
Add support for multiple register ranges with SoC specific names.
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/hantro.h | 7 ++-
drivers/staging/media/hantro/hantro_drv.c | 25 +--
2 files changed, 25 insertions(+), 7 deletions(-)
diff --git a/drive
This should enable MPEG-2 decoding on the Hantro G1 and JPEG encoding on
the Hantro H1 on i.MX8MM.
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/hantro_drv.c | 1 +
drivers/staging/media/hantro/hantro_hw.h| 1 +
drivers/staging/media/hantro/imx8m_vpu_hw.c | 134
The i.MX8MQ bindings will use different IRQ names ("g1" instead of
"vdpu", and "g2"), so make them configurable. This also allows to
register more than two IRQs, which will be required for i.MX8MM support
later (it will add "h1" instead of "vepu").
Signed-off-by: Philipp Zabel
---
drivers/stagin
Rename the driver and all relevant identifiers from Rockchip to Hantro,
as other Hantro IP based VPU implementations can be supported by the
same driver.
The RK3288 decoder is Hantro G1 based, the encoder is Hantro H1.
This patch just renames, no functional changes.
Signed-off-by: Philipp Zabel
For now this just enables MPEG-2 decoding on the Hantro G1 on i.MX8MQ.
Signed-off-by: Philipp Zabel
---
drivers/staging/media/hantro/Kconfig| 8 +-
drivers/staging/media/hantro/Makefile | 1 +
drivers/staging/media/hantro/hantro_drv.c | 1 +
drivers/staging/media/hantro/han
Add devicetree binding documentation for the Hantro G1/G2 VPU on i.MX8MQ
and for the Hantro G1/G2/H1 VPU on i.MX8MM.
Signed-off-by: Philipp Zabel
---
.../devicetree/bindings/media/imx8m-vpu.txt | 56 +++
1 file changed, 56 insertions(+)
create mode 100644 Documentation/devicet
Remove unused function and struct declarations from the
rockchip_vpu_common.h header file.
Signed-off-by: Philipp Zabel
---
.../media/rockchip/vpu/rockchip_vpu_common.h | 25 ---
1 file changed, 25 deletions(-)
diff --git a/drivers/staging/media/rockchip/vpu/rockchip_vpu_common
Update:
I opened the case and got the following component information based on model
numbers:
Demodulator: MN88436
Tuner: MXL603
USB Microcontroller: CY7C68013
-Justin
> On May 23, 2019 at 9:52 PM Justin Overfelt wrote:
>
>
> Hello!
>
> I recently purchased a Geniatech A681, which is an A
modify registers to fix bayer order in test pattern mode
Signed-off-by: Shawnx Tu
---
drivers/media/i2c/ov8856.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/media/i2c/ov8856.c b/drivers/media/i2c/ov8856.c
index dbf1095..cd347d6 100644
--- a/drivers/me
On Fri, May 24, 2019 at 11:45:25AM +0200, Frédéric Deghetto wrote:
> Hi Sean,
>
> Here are the outputs:
> ir-keytable:
> Found /sys/class/rc/rc0/ (/dev/input/event1) with:
> Driver gpio_ir_recv, table rc-rc6-mce
> Supported protocols: other lirc rc-5 rc-5-sz jvc sony nec sanyo
> mc
On 24/05/2019 10:20, Hans Verkuil wrote:
> On 5/24/19 11:05 AM, Guillaume Tucker wrote:
>> On 24/05/2019 09:44, Hans Verkuil wrote:
>>> On 5/24/19 10:38 AM, Guillaume Tucker wrote:
Hi Hans,
On 16/05/2019 07:41, Hans Verkuil wrote:
> Hi Guillaume,
>
> I have a few question
On 5/24/19 11:05 AM, Guillaume Tucker wrote:
> On 24/05/2019 09:44, Hans Verkuil wrote:
>> On 5/24/19 10:38 AM, Guillaume Tucker wrote:
>>> Hi Hans,
>>>
>>> On 16/05/2019 07:41, Hans Verkuil wrote:
Hi Guillaume,
I have a few questions/suggestions:
>>>
>>> Thanks for the feedback! It
On 24/05/2019 09:44, Hans Verkuil wrote:
> On 5/24/19 10:38 AM, Guillaume Tucker wrote:
>> Hi Hans,
>>
>> On 16/05/2019 07:41, Hans Verkuil wrote:
>>> Hi Guillaume,
>>>
>>> I have a few questions/suggestions:
>>
>> Thanks for the feedback! It's good to start seeing these reports
>> on the linux-me
On 5/24/19 10:38 AM, Guillaume Tucker wrote:
> Hi Hans,
>
> On 16/05/2019 07:41, Hans Verkuil wrote:
>> Hi Guillaume,
>>
>> I have a few questions/suggestions:
>
> Thanks for the feedback! It's good to start seeing these reports
> on the linux-media mailing list. And sorry for the slow reply, I
Hi Hans,
On 16/05/2019 07:41, Hans Verkuil wrote:
> Hi Guillaume,
>
> I have a few questions/suggestions:
Thanks for the feedback! It's good to start seeing these reports
on the linux-media mailing list. And sorry for the slow reply, I
was away.
> On 5/15/19 9:04 PM, kernelci.org bot wrote:
>
On Fri, May 24, 2019 at 07:31:03AM +0200, Frédéric Deghetto wrote:
> Probably related to this issue; ir-keytable -a /etc/rc_maps.conf -v gives:
>
> /sys/class/rc/rc0/protocols protocol rc-5 (disabled)
> /sys/class/rc/rc0/protocols protocol nec (disabled)
> /sys/class/rc/rc0/protocols protocol rc-6
37 matches
Mail list logo
