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 Jun 12 05:00:13 CEST 2019
media-tree git hash:4e8c120de9268fc26f583268b9d22e7d37c4595f
media_build gi
Hi Philipp,
Version 9 will also need to fix merge conflicts due to the recent module
re-org and the switch to sync registration for the IPU internal subdevs.
I've done that work already, feel free to cherry-pick it from my github
fork if you agree with the merge fixes:
g...@github.com:slong
Le mardi 11 juin 2019 à 20:12 -0400, Nicolas Dufresne a écrit :
> Le mardi 11 juin 2019 à 13:56 +0200, Marek Szyprowski a écrit :
> > Hi Hans,
> >
> > On 2019-06-11 09:52, Hans Verkuil wrote:
> > > On 6/7/19 9:43 PM, Nicolas Dufresne wrote:
> > > > Le vendredi 07 juin 2019 à 16:39 +0200, Marek Szy
On 6/12/19 1:49 AM, Antti Palosaari wrote:
On 6/12/19 2:27 AM, JP wrote:
On 6/12/19 12:28 AM, Antti Palosaari wrote:
On 6/8/19 5:49 AM, JP wrote:
I made the Mygica T230c2 work on kernel 5.1.7, but I have no idea
how to submit this.
http://jpvw.nl/pub/test/dvb/linux-5.1.7-t230c2.patch
Le mardi 11 juin 2019 à 13:56 +0200, Marek Szyprowski a écrit :
> Hi Hans,
>
> On 2019-06-11 09:52, Hans Verkuil wrote:
> > On 6/7/19 9:43 PM, Nicolas Dufresne wrote:
> > > Le vendredi 07 juin 2019 à 16:39 +0200, Marek Szyprowski a écrit :
> > > > Hi Hans,
> > > >
> > > > On 2019-06-07 16:11, Han
Le mardi 11 juin 2019 à 13:24 +0300, Laurent Pinchart a écrit :
> Hi Nicolas,
>
> On Fri, Jun 07, 2019 at 03:38:39PM -0400, Nicolas Dufresne wrote:
> > Le vendredi 07 juin 2019 à 16:58 +0300, Laurent Pinchart a écrit :
> > > On Fri, Jun 07, 2019 at 03:55:05PM +0200, Marek Szyprowski wrote:
> > > >
On 6/12/19 2:49 AM, Antti Palosaari wrote:
+ /* set ts clock freq to 10Mhz */
+ memcpy(cmd.args, "\x14\x00\x0d\x10\xe8\x03", 6);
+ cmd.wlen = 6;
+ cmd.rlen = 4;
+ ret = si2168_cmd_execute(client, &cmd);
+ if (ret) return ret;
+
0x03e8 is 1000 and value used is 10 000Hz step
On 6/12/19 2:27 AM, JP wrote:
On 6/12/19 12:28 AM, Antti Palosaari wrote:
On 6/8/19 5:49 AM, JP wrote:
I made the Mygica T230c2 work on kernel 5.1.7, but I have no idea
how to submit this. http://jpvw.nl/pub/test/dvb/linux-5.1.7-t230c2.patch
Please can someone help me out. It looks like
On 6/12/19 1:27 AM, JP wrote:
On 6/12/19 12:28 AM, Antti Palosaari wrote:
On 6/8/19 5:49 AM, JP wrote:
I made the Mygica T230c2 work on kernel 5.1.7, but I have no idea
how to submit this.
http://jpvw.nl/pub/test/dvb/linux-5.1.7-t230c2.patch
Please can someone help me out. It looks li
On 6/12/19 12:28 AM, Antti Palosaari wrote:
On 6/8/19 5:49 AM, JP wrote:
I made the Mygica T230c2 work on kernel 5.1.7, but I have no idea
how to submit this. http://jpvw.nl/pub/test/dvb/linux-5.1.7-t230c2.patch
Please can someone help me out. It looks like the extra code in the
demodulat
On 6/8/19 5:49 AM, JP wrote:
I made the Mygica T230c2 work on kernel 5.1.7, but I have no idea
how to submit this. http://jpvw.nl/pub/test/dvb/linux-5.1.7-t230c2.patch
Please can someone help me out. It looks like the extra code in the
demodulator does not effect other drivers that use it. Te
On 6/11/19 10:25 PM, Johan Korsnes wrote:
> Thank you for the review Hans. My comments are inline. A v2 of this
> series is under way.
>
> On 5/29/19 12:39 AM, Hans Verkuil wrote:
>> Hi Johan,
>>
>> Thanks for this patch series!
>>
>> The previous patches all look good, but this one needs a bit mo
Thank you for the review Hans. My comments are inline. A v2 of this
series is under way.
On 5/29/19 12:39 AM, Hans Verkuil wrote:
> Hi Johan,
>
> Thanks for this patch series!
>
> The previous patches all look good, but this one needs a bit more work:
>
> On 5/28/19 7:19 PM, johan.kors...@gmail
On Tue, Jun 11, 2019 at 5:09 AM Robin Gong wrote:
>
> Sven, no any dependency from sdma driver view. The only difference between
> directly loading firmware
> from kernel and rootfs is the former spend more time during kernel boot and
> such timing may cause
> the crash. The issue is not 100% in
On Tue, Jun 11, 2019 at 10:13 AM Hans Verkuil wrote:
>
> On 6/9/19 4:38 PM, Maxime Jourdan wrote:
> > Hello,
> >
> > This RFC proposes a new format flag - V4L2_FMT_FLAG_DYN_RESOLUTION - used
> > to tag coded formats for which the device supports dynamic resolution
> > switching, via V4L2_EVENT_SOU
Hi Tomasz,
On Mon, Jun 10, 2019 at 5:48 AM Tomasz Figa wrote:
>
> Hi Maxime,
>
> On Sun, Jun 9, 2019 at 11:38 PM Maxime Jourdan wrote:
> >
> > Add a enum_fmt format flag to specifically tag coded formats where
> > dynamic resolution switching is supported by the device.
> >
> > This is useful for
Hi Laurent,
Em Sat, 8 Jun 2019 15:02:22 +0300
Laurent Pinchart escreveu:
> Hi Mauro,
>
> The following changes since commit edadd68031e5b7c1ba0c413a9549dce62a02844c:
>
> media: MAINTAINERS: update email address (2019-06-05 15:58:40 -0400)
>
> are available in the Git repository at:
>
> g
On Tuesday, June 11, 2019 2:08:23 PM CEST Hans Verkuil (hansverk) wrote:
> Instead of filling in the struct v4l2_capability device_caps
> field, fill in the struct video_device device_caps field.
>
> That way the V4L2 core knows what the capabilities of the
> video device are.
>
> But this only r
On Wed, Jun 05, 2019 at 03:44:27PM -0500, Brad Love wrote:
> Includes support to identify and use two Hauppauge device.
> HVR-1955:
> - LGDT3306a ATSC/QAM demod
> - si2177 tuner
> - cx25840 decoder for analog tv/composite/s-video/audio
>
> HVR-1975 dual-frontend:
> - LGDT3306a ATSC/QAM demod
> - s
When the upstream endpoint is neither a mux nor a CSI2 module, just get
the source pad directly upstream from the CSI.
Fixes: 05f634040c0d ("media: staging/imx7: add imx7 CSI subdev driver")
Reported-by: Sebastien Szymanski
Signed-off-by: Rui Miguel Silva
---
drivers/staging/media/imx/imx7-medi
Sehr geehrte Damen und Herren,
nach unserem Besuch Ihrer Homepage möchten wir Ihnen ein Angebot von Produkten
vorstellen, das Ihnen ermöglichen wird, den Verkauf Ihrer Produkte sowie
Dienstleistungen deutlich zu erhöhen.
Die Datenbanken der Firmen sind in für Sie interessante und relevante
Zi
Hi Sakari,
On Fri, 2019-05-31 at 20:03 +0300, Sakari Ailus wrote:
> Hi Dongchun,
>
> On Thu, May 23, 2019 at 06:22:02PM +0800, dongchun@mediatek.com wrote:
> > From: Dongchun Zhu
> >
> > Add a V4L2 sub-device driver for the OmniVision image sensor.
> > This is a camera sensor using the I2C
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| 16 +-
drivers/staging/media/hantro/Makefile | 3 +
drivers/staging/media/hantro/hantro_drv.c | 3 +
drivers/staging/media/hantro/han
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 br-v5.3g
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
Dynamically allocate clocks and move clock names out of struct
hantro_variant. This lifts the four clock limit and allows to use
ARRAY_SIZE() to fill .num_clocks to reduce the risk of mismatches.
Signed-off-by: Philipp Zabel
Reviewed-by: Boris Brezillon
---
Changed since v3:
- Moved before addi
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 | 139
Add support for multiple register ranges with SoC specific names.
Signed-off-by: Philipp Zabel
Reviewed-by: Boris Brezillon
---
Changes since v3 [1]:
- Renamed bases to reg_bases
[1] https://patchwork.linuxtv.org/patch/56467/
---
drivers/staging/media/hantro/hantro.h | 8 ++--
driver
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
Reviewed-by: Boris Brezillon
---
drivers/staging/media/hant
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
Reviewed-by: Boris
It can be helpful to know which video device was registered at which
device node.
Signed-off-by: Philipp Zabel
Reviewed-by: Boris Brezillon
---
drivers/staging/media/hantro/hantro_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/media/hantro/hantro_drv
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
Reviewed-by: Boris Brezillon
---
drivers/staging/media/hantro/hantro.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/media
On Sat, 2019-06-01 at 11:18 +0200, Boris Brezillon wrote:
> On Fri, 31 May 2019 10:55:20 +0200
> Philipp Zabel wrote:
>
> > 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
> > ---
> >
On 2019-06-10 22:55, Ezequiel Garcia wrote:
> Some drivers need to access a vb2 buffer from its
> queue index. Introduce an accessor to abstract this,
> and avoid drivers from accessing private members.
>
> Reviewed-by: Boris Brezillon
> Signed-off-by: Ezequiel Garcia
Acked-by: Marek Szyprowsk
Instead of filling in the struct v4l2_capability device_caps
field, fill in the struct video_device device_caps field.
That way the V4L2 core knows what the capabilities of the
video device are.
But this only really works if all drivers use this, so convert
all pci drivers in this patch.
Signed-
Hi Hans,
On 2019-06-11 09:52, Hans Verkuil wrote:
> On 6/7/19 9:43 PM, Nicolas Dufresne wrote:
>> Le vendredi 07 juin 2019 à 16:39 +0200, Marek Szyprowski a écrit :
>>> Hi Hans,
>>>
>>> On 2019-06-07 16:11, Hans Verkuil wrote:
On 6/7/19 3:55 PM, Marek Szyprowski wrote:
> On 2019-06-07 15:
Hi Sebastien,
On Tue 11 Jun 2019 at 11:03, Sébastien Szymanski wrote:
> On 6/11/19 11:40 AM, Rui Miguel Silva wrote:
>> Hi Sebastien,
>> On Tue 11 Jun 2019 at 09:16, Sébastien Szymanski wrote:
>>> Hi Rui,
>>>
>>> thanks for the review!
>>>
>>> On 6/10/19 12:28 PM, Rui Miguel Silva wrote:
Hi Se
On Tue, 2019-06-04 at 12:42 +0200, Hans Verkuil wrote:
> On 6/3/19 10:02 PM, Boris Brezillon wrote:
> > On Mon, 3 Jun 2019 14:45:37 +0200
> > Hans Verkuil wrote:
> >
> > > On 5/31/19 10:55 AM, Philipp Zabel wrote:
> > > > For now this just enables MPEG-2 decoding on the Hantro G1 on i.MX8MQ.
> >
On Mon, 2019-06-03 at 14:54 +0200, Hans Verkuil wrote:
> On 5/31/19 10:55 AM, Philipp Zabel wrote:
> > This should enable MPEG-2 decoding on the Hantro G1 and JPEG encoding on
> > the Hantro H1 on i.MX8MM.
>
> That's the i.MX8M Mini, right? I think that's the official name for this
> SoC.
Correct
On Thu, 2019-06-06 at 17:06 +0200, Boris Brezillon wrote:
> On Wed, 5 Jun 2019 13:22:42 +0200
> Boris Brezillon wrote:
>
> > On Fri, 31 May 2019 10:55:14 +0200
> > Philipp Zabel wrote:
> >
> > > Rename the driver and all relevant identifiers from Rockchip to Hantro,
> > > as other Hantro IP bas
Hi Nicolas,
On Fri, Jun 07, 2019 at 03:38:39PM -0400, Nicolas Dufresne wrote:
> Le vendredi 07 juin 2019 à 16:58 +0300, Laurent Pinchart a écrit :
> > On Fri, Jun 07, 2019 at 03:55:05PM +0200, Marek Szyprowski wrote:
> >> On 2019-06-07 15:40, Hans Verkuil wrote:
> >>> On 6/7/19 2:47 PM, Hans Verku
Hi Laurent,
On 6/8/19 2:38 PM, Laurent Pinchart wrote:
> When debugging issues that involve more than one video queue, messages
> related to multiple queues get interleaved without any easy way to tell
> which queue they relate to. Fix this by printing the queue pointer for
> all debug messages in
On Tue, Jun 4, 2019 at 5:21 PM Enric Balletbo i Serra
wrote:
>
> There is a bit of mess between cros-ec mfd includes and platform
> includes. For example, we have a linux/mfd/cros_ec.h include that
> exports the interface implemented in platform/chrome/cros_ec_proto.c. Or
> we have a linux/mfd/cro
hi Tomasz:
Thanks for your review comments, the corresponding modification
& explanation is under preparation, will update soon.
Thanks.
BR
Daoyuan
On Tue, 2019-06-04 at 20:20 +0900, Tomasz Figa wrote:
> Hi Daoyuan,
>
> On Thu, May 16, 2019 at 11:23:32AM +0800, Daoyuan Huang wrote:
> > From: d
Sorry, forgot disable ipu1:
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
index b352ea2..b884490 100644
--- a/arch/arm/boot/dts/imx6qdl.dtsi
+++ b/arch/arm/boot/dts/imx6qdl.dtsi
@@ -1291,7 +1291,7 @@
<&clks IMX6QDL_CLK_IPU1_DI1>;
> -Original Message-
> From: Sven Van Asbroeck
> Sent: 2019年6月10日 23:47
> To: Robin Gong
> Subject: Re: [v8] media: imx: add mem2mem device
> On Mon, Jun 10, 2019 at 5:09 AM Robin Gong wrote:
> >
> > I can reproduce once enable your config to build firmware in kernel,
> > but no such iss
Dear Tomasz,
I'd like to elaborate more about the tuning_data.va.
Would you like to give us some advice about our improvement proposal inline?
Thank you very much.
On Wed, 2019-05-22 at 03:14 +0800, Frederic Chen wrote:
> Dear Tomasz,
>
> I appreciate your comment. It is very helpful for us.
>
On 6/9/19 4:38 PM, Maxime Jourdan wrote:
> Hello,
>
> This RFC proposes a new format flag - V4L2_FMT_FLAG_DYN_RESOLUTION - used
> to tag coded formats for which the device supports dynamic resolution
> switching, via V4L2_EVENT_SOURCE_CHANGE.
> This includes the initial "source change" where the d
On 6/10/19 5:48 AM, Tomasz Figa wrote:
> Hi Maxime,
>
> On Sun, Jun 9, 2019 at 11:38 PM Maxime Jourdan wrote:
>>
>> Add a enum_fmt format flag to specifically tag coded formats where
>> dynamic resolution switching is supported by the device.
>>
>> This is useful for some codec drivers that can't
On 6/9/19 4:38 PM, Maxime Jourdan wrote:
> Tag all the coded formats where the venus vdec supports dynamic
> resolution switching.
>
> Signed-off-by: Maxime Jourdan
> ---
> drivers/media/platform/qcom/venus/core.h | 1 +
> drivers/media/platform/qcom/venus/vdec.c | 11 +++
> 2 files cha
On 6/9/19 4:38 PM, Maxime Jourdan wrote:
> Add a enum_fmt format flag to specifically tag coded formats where
> dynamic resolution switching is supported by the device.
>
> This is useful for some codec drivers that can't support dynamic
can't -> can
> resolution switching for all their listed c
On 6/7/19 9:43 PM, Nicolas Dufresne wrote:
> Le vendredi 07 juin 2019 à 16:39 +0200, Marek Szyprowski a écrit :
>> Hi Hans,
>>
>> On 2019-06-07 16:11, Hans Verkuil wrote:
>>> On 6/7/19 3:55 PM, Marek Szyprowski wrote:
On 2019-06-07 15:40, Hans Verkuil wrote:
> On 6/7/19 2:47 PM, Hans Verku
On 6/7/19 4:34 PM, Tomasz Figa wrote:
> On Fri, Jun 7, 2019 at 11:11 PM Hans Verkuil wrote:
>>
>> On 6/7/19 3:55 PM, Marek Szyprowski wrote:
>>> Hi Hans,
>>>
>>> On 2019-06-07 15:40, Hans Verkuil wrote:
On 6/7/19 2:47 PM, Hans Verkuil wrote:
> On 6/7/19 2:23 PM, Hans Verkuil wrote:
>>
53 matches
Mail list logo
