On 04/05/2017 02:26 AM, Dmitry Torokhov wrote:
> Hi Hans,
>
> On Fri, Feb 03, 2017 at 03:46:01PM +0100, Hans Verkuil wrote:
>> Hi Dmitry,
>>
>> Thanks for the feedback. See my comments below:
>>
>> On 03/01/17 07:51, Dmitry Torokhov wrote:
>>> Hi Hans,
>>>
>>> On Thu, Dec 15, 2016 at 02:02:07PM +0
On 4/3/2017 22:54, Hans Verkuil wrote:
The driver moved to drivers/media/platform/atmel.
Signed-off-by: Hans Verkuil
---
After the atmel-isi v6 patch series this atmel-isi entry is no longer correct.
Fixed.
Songjun, I don't think Ludovic is still maintainer of this driver. Should that
be cha
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 Apr 5 05:00:20 CEST 2017
media-tree git hash:7ca0ef3da09888b303991edb80cd0283ee641c9e
media_build gi
On 04/04/2017 05:40 PM, Steve Longerbeam wrote:
On 04/04/2017 04:10 PM, Russell King - ARM Linux wrote:
On Thu, Mar 30, 2017 at 07:25:49PM +0200, Philipp Zabel wrote:
The TVP5150 DT bindings specify a single output port (port 0) that
corresponds to the video output pad (pad 1, DEMOD_PAD_VID
On 04/04/2017 04:10 PM, Russell King - ARM Linux wrote:
On Thu, Mar 30, 2017 at 07:25:49PM +0200, Philipp Zabel wrote:
The TVP5150 DT bindings specify a single output port (port 0) that
corresponds to the video output pad (pad 1, DEMOD_PAD_VID_OUT).
Signed-off-by: Philipp Zabel
---
I'm tryin
Hi Hans,
On Fri, Feb 03, 2017 at 03:46:01PM +0100, Hans Verkuil wrote:
> Hi Dmitry,
>
> Thanks for the feedback. See my comments below:
>
> On 03/01/17 07:51, Dmitry Torokhov wrote:
> >Hi Hans,
> >
> >On Thu, Dec 15, 2016 at 02:02:07PM +0100, Hans Verkuil wrote:
> >>From: Hans Verkuil
> >>
> >>
On Fri, Feb 03, 2017 at 04:26:32PM +0100, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Add a new serio ID for the RainShadow Tech USB HDMI CEC adapter.
>
> Signed-off-by: Hans Verkuil
Acked-by: Dmitry Torokhov
> ---
> include/uapi/linux/serio.h | 1 +
> 1 file changed, 1 insertion(+)
>
> d
On Thu, Mar 30, 2017 at 07:25:49PM +0200, Philipp Zabel wrote:
> The TVP5150 DT bindings specify a single output port (port 0) that
> corresponds to the video output pad (pad 1, DEMOD_PAD_VID_OUT).
>
> Signed-off-by: Philipp Zabel
> ---
> I'm trying to get this to work with a TVP5150 analog TV de
On Tue, Mar 28, 2017 at 03:37:29PM +0800, Andrew-CT Chen wrote:
> Hi linux-firmware maintainers,
>
> The following changes since commit 44d8e8d4fdcdff56e9e21208d4b4aa7cd6962656:
>
> Merge branch 'master' of https://github.com/Netronome/linux-firmware
> (2017-03-24 09:43:35 -0700)
>
> are avai
On 03/30/2017 10:25 AM, Philipp Zabel wrote:
The TVP5150 DT bindings specify a single output port (port 0) that
corresponds to the video output pad (pad 1, DEMOD_PAD_VID_OUT).
Signed-off-by: Philipp Zabel
---
I'm trying to get this to work with a TVP5150 analog TV decoder, and the
first probl
It is a bit confusing how CEC_CAP_RC and IS_REACHABLE(CONFIG_RC_CORE)
interact. By stripping CEC_CAP_RC at the beginning rather than after #else
it should be a bit clearer what is going on.
Signed-off-by: Hans Verkuil
Reported-by: Lee Jones
---
diff --git a/drivers/media/cec/cec-core.c b/drivers
On Tue, Apr 04, 2017 at 05:10:05PM +0100, Lee Jones wrote:
> @@ -237,7 +241,6 @@ struct cec_adapter *cec_allocate_adapter(const struct
> cec_adap_ops *ops,
> if (!(caps & CEC_CAP_RC))
> return adap;
>
> -#if IS_REACHABLE(CONFIG_RC_CORE)
> /* Prepare the RC input device
Currently users have to use all sorts of ugly #ifery within
their drivers in order to avoid linking issues at build time.
This patch allows users to safely call these functions when
!CONFIG_RC_CORE and make decisions based on the return value
instead. This is a much more common and clean way of do
If a user specifies the use of RC as a capability, they should
really be enabling RC Core code. If they do not we WARN() them
of this and disable the capability for them.
Once we know RC Core code has not been enabled, we can update
the user's capabilities and use them as a term of reference for
On 04/04/2017 05:36 PM, Russell King - ARM Linux wrote:
> On Tue, Apr 04, 2017 at 04:19:39PM +0100, Lee Jones wrote:
>> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>>
>>> On 04/04/2017 04:43 PM, Lee Jones wrote:
If a user specifies the use of RC as a capability, they should
really be enablin
On 04/04/2017 05:19 PM, Lee Jones wrote:
> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>
>> On 04/04/2017 04:43 PM, Lee Jones wrote:
>>> If a user specifies the use of RC as a capability, they should
>>> really be enabling RC Core code. If they do not we WARN() them
>>> of this and disable the capab
On 04/04/2017 02:31 PM, Neil Armstrong wrote:
> The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller
> in combination with a very custom PHY.
>
> Thanks to Laurent Pinchart's changes, the HW report the following :
> Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_ph
Enable DCMI camera interface on STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 3c99466..87733d3 100644
---
This patchset introduces a basic support for Digital Camera Memory Interface
(DCMI) of STMicroelectronics STM32 SoC series.
This first basic support implements RGB565 & YUV frame grabbing.
Cropping and JPEG support will be added later on.
This has been tested on STM324x9I-EVAL evaluation board em
This adds documentation of device tree bindings for the STM32 DCMI
(Digital Camera Memory Interface).
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/st,stm32-dcmi.txt| 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bi
Enable STMPE1600 GPIO expander.
Signed-off-by: Hugues Fruchet
---
arch/arm/configs/stm32_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig
index a9d8e3c..84adc88 100644
--- a/arch/arm/configs/stm32_defconfig
+++ b/
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32f429.dtsi | 37 +
1 file changed, 37 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index ee0da97..e1ff978 100644
--- a/arch/arm/boot/dts/stm32f429.dtsi
++
Enable DCMI camera interface and OV2640 camera sensor drivers.
Signed-off-by: Hugues Fruchet
---
arch/arm/configs/stm32_defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig
index 84adc88..3f2e4ce 100644
--- a/arc
Enable STMPE1600 gpio expander of STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 87733d3..7ffcf0
Thanks Rob for review, find answers below.
On 04/03/2017 06:23 PM, Rob Herring wrote:
> On Thu, Mar 30, 2017 at 05:27:40PM +0200, Hugues Fruchet wrote:
>> This adds documentation of device tree bindings for the STM32 DCMI
>> (Digital Camera Memory Interface).
>>
>> Signed-off-by: Hugues Fruchet
>
Enable OV2640 camera support of STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 7ffc
This V4L2 subdev driver enables Digital Camera Memory Interface (DCMI)
of STMicroelectronics STM32 SoC series.
Reviewed-by: Hans Verkuil
Signed-off-by: Yannick Fertre
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/Kconfig| 12 +
drivers/media/platform/Makefile
On Tue, Apr 04, 2017 at 04:19:39PM +0100, Lee Jones wrote:
> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>
> > On 04/04/2017 04:43 PM, Lee Jones wrote:
> > > If a user specifies the use of RC as a capability, they should
> > > really be enabling RC Core code. If they do not we WARN() them
> > > of t
On Tue, 04 Apr 2017, Hans Verkuil wrote:
> On 04/04/2017 04:43 PM, Lee Jones wrote:
> > If a user specifies the use of RC as a capability, they should
> > really be enabling RC Core code. If they do not we WARN() them
> > of this and disable the capability for them.
> >
> > Once we know RC Core
On 04/04/2017 04:43 PM, Lee Jones wrote:
> If a user specifies the use of RC as a capability, they should
> really be enabling RC Core code. If they do not we WARN() them
> of this and disable the capability for them.
>
> Once we know RC Core code has not been enabled, we can update
> the user's
If a user specifies the use of RC as a capability, they should
really be enabling RC Core code. If they do not we WARN() them
of this and disable the capability for them.
Once we know RC Core code has not been enabled, we can update
the user's capabilities and use them as a term of reference for
Hi Mauro,
The following changes since commit 7ca0ef3da09888b303991edb80cd0283ee641c9e:
Merge tag 'v4.11-rc5' into patchwork (2017-04-04 11:11:43 -0300)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git vsp1/next
for you to fetch changes up to b116ebc56310945bde3
Le 28/03/2017 à 10:23, Hans Verkuil a écrit :
> From: Hans Verkuil
>
> This patch series converts the soc-camera atmel-isi to a standalone V4L2
> driver.
>
> The same is done for the ov7670 and ov2640 sensor drivers: the ov7670 was
> used to test the atmel-isi driver. The ov2640 is needed becaus
On Tue, 04 Apr 2017, Hans Verkuil wrote:
> On 04/04/2017 03:01 PM, Lee Jones wrote:
> > On Tue, 04 Apr 2017, Lee Jones wrote:
> >
> >> On Tue, 04 Apr 2017, Hans Verkuil wrote:
> >>
> >>> On 04/04/2017 02:32 PM, Lee Jones wrote:
> If CONFIG_RC_CORE is not enabled then none of the RC code will
Hi Helen,
On Mon, Apr 03, 2017 at 12:11:54PM -0300, Helen Koike wrote:
> Hi,
>
> On 2017-03-31 06:57 AM, Mauro Carvalho Chehab wrote:
> >Em Fri, 31 Mar 2017 10:29:04 +0200
> >Hans Verkuil escreveu:
> >
> >>On 30/03/17 18:02, Helen Koike wrote:
> >>>Add V4L2_INPUT_TYPE_DEFAULT and helpers functio
On 04/04/2017 03:01 PM, Lee Jones wrote:
> On Tue, 04 Apr 2017, Lee Jones wrote:
>
>> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>>
>>> On 04/04/2017 02:32 PM, Lee Jones wrote:
If CONFIG_RC_CORE is not enabled then none of the RC code will be
executed anyway, so we're placing the capabilit
On Tue, 04 Apr 2017, Lee Jones wrote:
> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>
> > On 04/04/2017 02:32 PM, Lee Jones wrote:
> > > If CONFIG_RC_CORE is not enabled then none of the RC code will be
> > > executed anyway, so we're placing the capability check inside the
> > >
> > > Signed-off-b
On 04/04/2017 02:54 PM, Lee Jones wrote:
> On Tue, 04 Apr 2017, Hans Verkuil wrote:
>
>> On 04/04/2017 02:32 PM, Lee Jones wrote:
>>> If CONFIG_RC_CORE is not enabled then none of the RC code will be
>>> executed anyway, so we're placing the capability check inside the
>>>
>>> Signed-off-by: Lee J
On Tue, 04 Apr 2017, Hans Verkuil wrote:
> On 04/04/2017 02:32 PM, Lee Jones wrote:
> > Currently when the RC Core is enabled (reachable) core code located
> > in cec_register_adapter() attempts to populate the RC structure with
> > a pointer to the 'parent' passed in by the caller.
> >
> > Unfor
On Tue, 04 Apr 2017, Hans Verkuil wrote:
> On 04/04/2017 02:32 PM, Lee Jones wrote:
> > If CONFIG_RC_CORE is not enabled then none of the RC code will be
> > executed anyway, so we're placing the capability check inside the
> >
> > Signed-off-by: Lee Jones
> > ---
> > drivers/media/cec/cec-core
Hi Steve, Philipp and Pavel,
On Mon, Mar 27, 2017 at 05:40:34PM -0700, Steve Longerbeam wrote:
> From: Philipp Zabel
>
> This driver can handle SoC internal and external video bus multiplexers,
> controlled either by register bit fields or by a GPIO. The subdevice
> passes through frame interval
Converts atmel-isi to a regular v4l2 driver instead of relying on soc-camera.
The ov2640 and ov7670 drivers are also converted to normal i2c drivers.
Tested with my sama5d3-Xplained board, the ov2640 sensor and two ov7670
sensors: one with and one without reset/pwdn pins. Also tested with my
em28
On 04/04/2017 02:32 PM, Lee Jones wrote:
> Currently when the RC Core is enabled (reachable) core code located
> in cec_register_adapter() attempts to populate the RC structure with
> a pointer to the 'parent' passed in by the caller.
>
> Unfortunately if the caller did not specify RC capibility w
On 04/04/2017 02:32 PM, Lee Jones wrote:
> If CONFIG_RC_CORE is not enabled then none of the RC code will be
> executed anyway, so we're placing the capability check inside the
>
> Signed-off-by: Lee Jones
> ---
> drivers/media/cec/cec-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(
Em Sun, 2 Apr 2017 14:34:18 -0600
Jonathan Corbet escreveu:
> On Thu, 30 Mar 2017 17:11:27 -0300
> Mauro Carvalho Chehab wrote:
>
> > This series converts just two documents, adding them to the
> > core-api.rst book. It addresses the errors/warnings that popup
> > after the conversion.
> >
> >
From: Laurent Pinchart
In preparation for adding PHY operations to handle RX SENSE and HPD,
group all the PHY interrupt setup code in a single location and extract
it to a separate function.
Signed-off-by: Laurent Pinchart
Reviewed-by: Jose Abreu
[narmstrong: renamed dw_hdmi_fb_registered to d
The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller
in combination with a very custom PHY.
Thanks to Laurent Pinchart's changes, the HW report the following :
Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
The following differs from common PHY integration as
Switch code to use the newly introduced V4L bus formats IDs instead of custom
defines. Also use the V4L encoding defines.
Some display pipelines can only provide non-RBG input pixels to the HDMI TX
Controller, this patch takes the pixel format from the plat_data if provided.
Reviewed-by: Jose Abr
This patch adds a new DRM documentation entry and links to the input
format table added in the dw_hdmi header.
Reviewed-by: Archit Taneja
Acked-by: Laurent Pinchart
Signed-off-by: Neil Armstrong
---
Documentation/gpu/bridge/dw-hdmi.rst | 15 +++
Documentation/gpu/index.rst
Currently when the RC Core is enabled (reachable) core code located
in cec_register_adapter() attempts to populate the RC structure with
a pointer to the 'parent' passed in by the caller.
Unfortunately if the caller did not specify RC capibility when calling
cec_allocate_adapter(), then there will
If CONFIG_RC_CORE is not enabled then none of the RC code will be
executed anyway, so we're placing the capability check inside the
Signed-off-by: Lee Jones
---
drivers/media/cec/cec-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/cec/cec-core.c b/drivers
The HDMI TX controller support HPD and RXSENSE signaling from the PHY
via it's STAT0 PHY interface, but some vendor PHYs can manage these
signals independently from the controller, thus these STAT0 handling
should be moved to PHY specific operations and become optional.
The existing STAT0 HPD and
Hi Gustavo,
Thank you for the patchset. Please see my comments below.
On Mon, Mar 13, 2017 at 04:20:25PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Hi,
>
> This RFC adds support for Explicit Synchronization of shared buffers in V4L2.
> It uses the Sync File Framework[1] as vecto
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:38 Neil Armstrong wrote:
> The HDMI TX controller support HPD and RXSENSE signaling from the PHY
> via it's STAT0 PHY interface, but some vendor PHYs can manage these
> signals independently from the controller, thus these STAT0 handli
Hi Sakari,
Thank you for the time to review this again.
On 04/04/2017 12:31 PM, Sakari Ailus wrote:
> Hi Todor,
>
> On Mon, Apr 03, 2017 at 05:02:28PM +0300, Todor Tomov wrote:
>> Add the document for ov5645 device tree binding.
>>
>> Signed-off-by: Todor Tomov
>> Reviewed-by: Laurent Pinchart
On Mon, 2017-04-03 at 10:28 +0200, Hans Verkuil wrote:
> On 03/31/2017 11:06 AM, Smitha T Murthy wrote:
> > Added V4l2 controls for HEVC encoder
> >
> > Signed-off-by: Smitha T Murthy
> > ---
> > Documentation/media/uapi/v4l/extended-controls.rst | 355
> > +
> > 1 file chan
Hi Evgeni,
On Monday 03 Apr 2017 08:53:44 Raikhel, Evgeni wrote:
> Hi Laurent,
> Can you please update on the status of the submission?
> The last version has been reviewed a month ago.
> Is there any estimate on when it is going to be staged/triaged/merged into
> media tree?
I've just sent a pul
Hi Mauro,
The following changes since commit c3d4fb0fb41f4b5eafeee51173c14e50be12f839:
[media] rc: sunxi-cir: simplify optional reset handling (2017-03-24 08:30:03
-0300)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git uvc/next
for you to fetch changes up to
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:37 Neil Armstrong wrote:
> This patch adds a new DRM documentation entry and links to the input
> format table added in the dw_hdmi header.
>
> Reviewed-by: Archit Taneja
> Signed-off-by: Neil Armstrong
Acked-by: Laurent Pinchart
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:36 Neil Armstrong wrote:
> Some display pipelines can only provide non-RBG input pixels to the HDMI TX
> Controller, this patch takes the pixel format from the plat_data if
> provided.
The commit message doesn't seem to match the subj
Hi Todor,
On Mon, Apr 03, 2017 at 05:02:28PM +0300, Todor Tomov wrote:
> Add the document for ov5645 device tree binding.
>
> Signed-off-by: Todor Tomov
> Reviewed-by: Laurent Pinchart
> ---
> .../devicetree/bindings/media/i2c/ov5645.txt | 54
> ++
> 1 file changed,
Hi Todor,
On Mon, Apr 03, 2017 at 05:02:52PM +0300, Todor Tomov wrote:
...
> +power_down:
> + ov5645_s_power(&ov5645->sd, false);
> +free_entity:
> + media_entity_cleanup(&ov5645->sd.entity);
> +free_ctrl:
> + v4l2_ctrl_handler_free(&ov5645->ctrls);
> + mutex_destroy(&ov5645->power
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:35 Neil Armstrong wrote:
> Add documentation for added Bus Formats to describe RGB and YUV formats used
> as input to the Synopsys DesignWare HDMI TX Controller.
>
> Acked-by: Hans Verkuil
> Reviewed-by: Archit Taneja
> Acked-by: Ma
Hi Neil,
Thank you for the patch.
On Monday 03 Apr 2017 16:42:34 Neil Armstrong wrote:
> In order to describe the RGB and YUV bus formats used to feed the
> Synopsys DesignWare HDMI TX Controller, add missing formats to the
> list of Bus Formats.
>
> Documentation for these formats is added in a
64 matches
Mail list logo
