Hi Luca,
On 11/03/2018 11:00 PM, Luca Ceresoli wrote:
> Hi Vladimir,
>
> On 31/10/18 21:12, Vladimir Zapolskiy wrote:
>> Hi Luca,
>>
>> thank you for review.
>>
>> On 10/30/2018 06:43 PM, Luca Ceresoli wrote:
>>> Hi Vladimir,
>>>
&
Hi Jean-Michel,
On 10/30/2018 06:41 PM, Jean-Michel Hautbois wrote:
> Hi there,
>
> I am using the i.MX6D from Digi (connect core 6 sbc) with a mailine
> kernel (well, 4.14 right now) and have an issue with mipi-csi2
> capture.
> First I will give brief explanation of my setup, and then I will
>
Hi Luca,
On 10/30/2018 06:44 PM, Luca Ceresoli wrote:
> Hi Vladimir,
>
> On 16/10/18 14:48, Laurent Pinchart wrote:
>> Hi Vladimir,
>>
>> On Saturday, 13 October 2018 16:47:48 EEST Vladimir Zapolskiy wrote:
>>> On 10/12/2018 03:01 PM, Laurent Pinchart wrote:
&
Hi Luca,
thank you for review.
On 10/30/2018 06:43 PM, Luca Ceresoli wrote:
> Hi Vladimir,
>
> On 08/10/18 23:12, Vladimir Zapolskiy wrote:
>> From: Vladimir Zapolskiy
>>
>> TI DS90Ux9xx de-/serializers are capable to route I2C messages to
>> I2C slave
Hi Luca,
thank you for review, please find my comments below.
On 10/30/2018 06:43 PM, Luca Ceresoli wrote:
> Hi Vladimir,
>
> On 08/10/18 23:11, Vladimir Zapolskiy wrote:
>> From: Sandeep Jain
>>
>> The change adds device tree binding description of TI DS90Ux9xx
Hi Laurent,
On 10/12/2018 02:59 PM, Vladimir Zapolskiy wrote:
> Hello Laurent.
>
> On 10/12/2018 04:01 PM, Laurent Pinchart wrote:
>> Hello Vladimir,
>>
...
>> then move to the driver side. In that area I would like to have a full
>> example
>> of a sy
Hi Laurent,
On 10/16/2018 04:12 PM, Laurent Pinchart wrote:
> Hi Vladimir,
>
> On Saturday, 13 October 2018 18:10:25 EEST Vladimir Zapolskiy wrote:
>> On 10/12/2018 04:01 PM, Laurent Pinchart wrote:
>>> On Friday, 12 October 2018 14:47:52 EEST Kieran Bingham wrote
Hi Laurent,
On 10/12/2018 04:01 PM, Laurent Pinchart wrote:
> Hello Vladimir,
>
> On Friday, 12 October 2018 14:47:52 EEST Kieran Bingham wrote:
>> On 12/10/18 11:58, Vladimir Zapolskiy wrote:
[snip]
>> Essentially they are multi purpose buses - which do not yet have a
Hi Laurent,
thank you for review, please find my comments below.
On 10/12/2018 02:44 PM, Laurent Pinchart wrote:
> Hi Vladimir,
>
> Thank you for the patch.
>
> On Tuesday, 9 October 2018 00:11:59 EEST Vladimir Zapolskiy wrote:
>> From: Sandeep Jain
>>
>> Th
Hi Laurent,
thank you for review, please find my comments below.
On 10/12/2018 03:01 PM, Laurent Pinchart wrote:
> Hi Vladimir,
>
> Thank you for the patch.
>
> On Tuesday, 9 October 2018 00:12:01 EEST Vladimir Zapolskiy wrote:
>> From: Vladimir Zapolskiy
>>
>
Hi Kieran,
On 10/12/2018 02:47 PM, Kieran Bingham wrote:
> Hi Vladimir,
>
[snip]
>
> Essentially they are multi purpose buses - which do not yet have a home.
> We have used media as a home because of our use case.
>
> The use case whether they transfer frames from a camera or to a display
> a
Hi Laurent
On 10/12/2018 04:12 PM, Laurent Pinchart wrote:
> Hi Vladimir,
>
> (CC'ing Wolfram)
>
> On Friday, 12 October 2018 10:32:32 EEST Vladimir Zapolskiy wrote:
>> On 10/12/2018 09:04 AM, Lee Jones wrote:
>>> On Tue, 09 Oct 2018, Vladimir Zapolskiy w
On 10/12/2018 02:43 PM, Lee Jones wrote:
> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>
>> On 10/12/2018 11:39 AM, Lee Jones wrote:
>>> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>>>> On 10/12/2018 09:03 AM, Lee Jones wrote:
>>>>&g
Hi Lee,
On 10/12/2018 02:34 PM, Lee Jones wrote:
> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>> On 10/12/2018 12:20 PM, Kieran Bingham wrote:
>>> Hi Vladimir,
>>> On 12/10/18 09:39, Lee Jones wrote:
>>>> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
Hello Laurent.
On 10/12/2018 04:01 PM, Laurent Pinchart wrote:
> Hello Vladimir,
>
> On Friday, 12 October 2018 14:47:52 EEST Kieran Bingham wrote:
>> On 12/10/18 11:58, Vladimir Zapolskiy wrote:
>>> On 10/12/2018 12:20 PM, Kieran Bingham wrote:
>>>> On 12/10
On 10/12/2018 11:39 AM, Lee Jones wrote:
> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>> On 10/12/2018 09:03 AM, Lee Jones wrote:
>>> On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote:
>>>
>>>> From: Vladimir Zapolskiy
>>>>
>>>> The
Hi Kieran,
On 10/12/2018 12:20 PM, Kieran Bingham wrote:
> Hi Vladimir,
>
> On 12/10/18 09:39, Lee Jones wrote:
>> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>>> On 10/12/2018 09:03 AM, Lee Jones wrote:
>>>> On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote:
Hi Lee,
On 10/12/2018 09:03 AM, Lee Jones wrote:
> On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote:
>
>> From: Vladimir Zapolskiy
>>
>> The change adds I2C device driver for TI DS90Ux9xx de-/serializers,
>> support of subdevice controllers is done in separate
Hi Lee,
On 10/12/2018 09:04 AM, Lee Jones wrote:
> On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote:
>
>> From: Vladimir Zapolskiy
>>
>> The change adds TI DS90Ux9xx I2C bridge/alias subdevice driver and
>> FPD Link connection handling mechanism.
>>
>> A
On 10/09/2018 02:11 PM, Vladimir Zapolskiy wrote:
> Hi Marek,
>
> On 10/09/2018 03:13 AM, Marek Vasut wrote:
>> On 10/08/2018 11:11 PM, Vladimir Zapolskiy wrote:
>>> From: Sandeep Jain
>>>
>>> The change adds device tree binding description of
ree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Vladimir-Zapolskiy/mfd-pinctrl-add-initial-support-of-TI-DS90Ux9xx-ICs/20181009-090135
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
> f
Hi Marek,
On 10/09/2018 03:13 AM, Marek Vasut wrote:
> On 10/08/2018 11:11 PM, Vladimir Zapolskiy wrote:
>> From: Sandeep Jain
>>
>> The change adds device tree binding description of TI DS90Ux9xx
>> series of serializer and deserializer controllers which support video
s/ossalsjp18/8a/vzapolskiy_als2018.pdf
Sandeep Jain (1):
dt-bindings: mfd: ds90ux9xx: add description of TI DS90Ux9xx ICs
Vladimir Zapolskiy (6):
dt-bindings: mfd: ds90ux9xx: add description of TI DS90Ux9xx I2C bridge
dt-bindings: pinctrl: ds90ux9xx: add description of TI DS90Ux9xx pinmux
From: Vladimir Zapolskiy
TI DS90Ux9xx de-/serializers have a capability to multiplex pin functions,
in particular a pin may have selectable functions of GPIO, GPIO line
transmitter, one of I2S lines, one of RGB24 video signal lines and so on.
The change adds a description of DS90Ux9xx pin
Record TI DS90Ux9xx series of serializer and deserializer ICs
and IC subcontrollers as maintained.
Signed-off-by: Vladimir Zapolskiy
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 29c08106bd22..3952035b6b71 100644
--- a
From: Vladimir Zapolskiy
TI DS90Ux9xx de-/serializers are capable to route I2C messages to
I2C slave devices connected to a remote de-/serializer in a pair,
the change adds description of device tree bindings of the subcontroller
to configure and enable this functionality.
Signed-off-by
From: Vladimir Zapolskiy
The change adds I2C device driver for TI DS90Ux9xx de-/serializers,
support of subdevice controllers is done in separate drivers, because
not all IC functionality may be needed in particular situations, and
this can be fine grained controlled in device tree.
The
From: Vladimir Zapolskiy
The change adds an MFD cell driver for managing pin functions on
TI DS90Ux9xx de-/serializers.
Signed-off-by: Vladimir Zapolskiy
---
drivers/pinctrl/Kconfig | 11 +
drivers/pinctrl/Makefile| 1 +
drivers/pinctrl/pinctrl-ds90ux9xx.c | 970
of secondary importance]
Signed-off-by: Vladimir Zapolskiy
---
.../devicetree/bindings/mfd/ti,ds90ux9xx.txt | 66 +++
1 file changed, 66 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/ti,ds90ux9xx.txt
diff --git a/Documentation/devicetree/bindings/mfd/ti
From: Vladimir Zapolskiy
The change adds TI DS90Ux9xx I2C bridge/alias subdevice driver and
FPD Link connection handling mechanism.
Access to I2C devices connected to a remote de-/serializer is done in
a transparent way, on established link detection event such devices
are registered on an I2C
Hi Dmitry,
On 10/20/2017 12:34 AM, Dmitry Osipenko wrote:
> Add binding documentation for the Video Decoder Engine which is found
> on NVIDIA Tegra20/30/114/124/132 SoC's.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../devicetree/bindings/media/nvidia,tegra-vde.txt | 55
> +
Hi Dmitry,
On 10/20/2017 12:34 AM, Dmitry Osipenko wrote:
> From: Vladimir Zapolskiy
>
> All Tegra SoCs contain 256KiB IRAM, which is used to store CPU resume code
> and by hardware engines like a video decoder.
>
> Signed-off-by: Vladimir Zapolskiy
Please add also your o
Hi Dmitry,
I'll add just a couple of minor comments, in general the code looks
very good.
On 10/20/2017 12:34 AM, Dmitry Osipenko wrote:
> NVIDIA Tegra20/30/114/124/132 SoC's have video decoder engine that
> supports standard set of video formats like H.264 / MPEG-4 / WMV / VC1.
> Currently imple
r IRAM resource between users.
My proposal is to add a valid device tree node to describe an IRAM region
firstly, then reserve a subregion in it by using a new "iram" property.
8<
From: Vladimir Zapolskiy
Date: Thu, 12 Oct 2017 10:25:45 +0300
Subject: [PATCH] ARM: tegra:
On 06/10/2017 02:26 AM, Hans Verkuil wrote:
> On 10/06/17 01:16, Steve Longerbeam wrote:
>>
>>
>> On 06/07/2017 12:02 PM, Hans Verkuil wrote:
>>> We're still waiting for an Ack for patch 02/34, right?
>>>
>>
>> Hi Hans, Rub has provided an Ack for patch 2.
>>
>>> Other than that everything is ready
Hi Steve,
On 03/28/2017 03:40 AM, 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 and mbus configuration of the active
Hi Ramiro,
On 03/06/2017 01:16 PM, Ramiro Oliveira wrote:
> Create device tree bindings documentation.
>
> Signed-off-by: Ramiro Oliveira
The device tree binding description looks perfect from my perspective.
Reviewed-by: Vladimir Zapolskiy
--
With best wishes,
Vladimir
l updates are fine, thank you. Feel free to add my
Reviewed-by: Vladimir Zapolskiy
> ---
> MAINTAINERS| 7 +
> drivers/media/i2c/Kconfig | 11 +
> drivers/media/i2c/Makefile | 1 +
> drivers/media/i2c/ov5647.c | 636
> +
On 03/19/2017 04:22 PM, Russell King - ARM Linux wrote:
> On Sun, Mar 19, 2017 at 02:21:10PM +, Russell King - ARM Linux wrote:
>> There's a good reason why I dumped a full debug log using GST_DEBUG=*:9,
>> analysed it for the cause of the failure, and tried several different
>> pipelines, incl
Hi Russell,
On 03/18/2017 10:43 PM, Russell King - ARM Linux wrote:
> On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote:
>> Can you share your gstreamer pipeline? For now, until
>> VIDIOC_ENUM_FRAMESIZES is implemented, try a pipeline that
>> does not attempt to specify a frame rate
On 02/22/2017 12:51 PM, Ramiro Oliveira wrote:
> Hi Zakari,
>
> On 2/21/2017 8:36 PM, Vladimir Zapolskiy wrote:
>> Hi Ramiro,
>>
>> On 02/21/2017 06:42 PM, Ramiro Oliveira wrote:
>>> Hi Vladimir,
>>>
>>> Thank you for your feedback
>>&
Hi Ramiro,
On 02/22/2017 12:57 PM, Ramiro Oliveira wrote:
> Hi Vladimir
>
> On 2/21/2017 10:37 PM, Vladimir Zapolskiy wrote:
>> Hi Sakari,
>>
>> On 02/21/2017 11:48 PM, Sakari Ailus wrote:
>>> Hi, Vladimir!
>>>
>>> How do you do? :-)
>>
Hi Sakari,
On 02/21/2017 11:48 PM, Sakari Ailus wrote:
> Hi, Vladimir!
>
> How do you do? :-)
deferring execution of boring tasks by doing code review :)
> On Tue, Feb 21, 2017 at 10:48:09PM +0200, Vladimir Zapolskiy wrote:
>> Hi Ramiro,
>>
>> On 02/21/2017 1
Hi Ramiro,
On 02/21/2017 10:13 PM, Ramiro Oliveira wrote:
> Hi Vladimir,
>
> Thank you for your feedback
>
> On 2/21/2017 3:58 PM, Vladimir Zapolskiy wrote:
>> Hi Ramiro,
>>
>> On 02/17/2017 03:14 PM, Ramiro Oliveira wrote:
>>> Create device tree bin
Hi Ramiro,
On 02/21/2017 06:42 PM, Ramiro Oliveira wrote:
> Hi Vladimir,
>
> Thank you for your feedback
>
> On 2/21/2017 3:54 PM, Vladimir Zapolskiy wrote:
>> Hi Ramiro,
>>
>> please find some review comments below.
>>
>> On 02/17/2017 03:14 PM,
Hi Ramiro,
On 02/17/2017 03:14 PM, Ramiro Oliveira wrote:
> Create device tree bindings documentation.
>
> Signed-off-by: Ramiro Oliveira
> Acked-by: Rob Herring
> ---
> .../devicetree/bindings/media/i2c/ov5647.txt | 35
> ++
> 1 file changed, 35 insertions(+)
> cre
Hi Ramiro,
please find some review comments below.
On 02/17/2017 03:14 PM, Ramiro Oliveira wrote:
> The OV5647 sensor from Omnivision supports up to 2592x1944 @ 15 fps, RAW 8
> and RAW 10 output formats, and MIPI CSI-2 interface.
>
> The driver adds support for 640x480 RAW 8.
>
> Signed-off-by:
Hi Ramiro,
On 02/13/2017 09:14 PM, Ramiro Oliveira wrote:
> Hi Vladimir,
>
> Thank you for your feedback.
>
> On 2/13/2017 12:21 PM, Vladimir Zapolskiy wrote:
>> Hello Ramiro,
>>
>> On 02/13/2017 01:25 PM, Ramiro Oliveira wrote:
>>> Modes supported:
>
Hello Ramiro,
On 02/13/2017 01:25 PM, Ramiro Oliveira wrote:
> Modes supported:
> - 640x480 RAW 8
>
It is a pretty short commit message, please consider to write a couple
of words about the sensor.
> Signed-off-by: Ramiro Oliveira
> ---
[snip]
> +
> +struct cfg_array {
> + struct regval
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> Adds MIPI CSI-2 Receiver subdev driver. This subdev is required
> for sensors with a MIPI CSI2 interface.
>
> Signed-off-by: Steve Longerbeam
> ---
> drivers/staging/media/imx/Makefile| 1 +
> drivers/staging/media/imx/imx-mipi-csi2.c |
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> This is the camera interface driver that provides the v4l2
> user interface. Frames can be received from various sources:
>
> - directly from SMFC for capturing unconverted images directly from
> camera sensors.
>
> - from the IC pre-process enc
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> This is a set of three media entity subdevice drivers for the i.MX
> Image Converter. The i.MX IC module contains three independent
> "tasks":
>
> - Pre-processing Encode task: video frames are routed directly from
> the CSI and can be scaled, co
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> This is a media entity subdevice driver for the i.MX Sensor Multi-FIFO
> Controller module. Video frames are received from the CSI and can
> be routed to various sinks including the i.MX Image Converter for
> scaling, color-space conversion, motion
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> This is a media entity subdevice for the i.MX Camera
> Serial Interface module.
>
> Signed-off-by: Steve Longerbeam
> ---
[snip]
> diff --git a/drivers/staging/media/imx/imx-csi.c
> b/drivers/staging/media/imx/imx-csi.c
> new file mode 100644
>
Hi Steve,
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> Add the core media driver for i.MX SOC.
>
> Signed-off-by: Steve Longerbeam
> ---
> Documentation/devicetree/bindings/media/imx.txt | 205 +
v2 was sent before getting Rob's review comments, but still they
should be addressed in
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> Enables the ADV7180 decoder sensor. The ADV7180 connects to the
> parallel-bus mux input on ipu1_csi0_mux.
>
> On the sabreauto, two analog video inputs are routed to the ADV7180,
> composite on Ain1, and composite on Ain3. Those inputs are defined
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> Enables the OV5642 parallel-bus sensor, and the OV5640 MIPI CSI-2 sensor.
>
> The OV5642 connects to the parallel-bus mux input port on ipu1_csi0_mux.
>
> The OV5640 connects to the input port on the MIPI CSI-2 receiver on
> mipi_csi. It is set to
Hi Steve,
On 01/03/2017 10:57 PM, Steve Longerbeam wrote:
> Enables the OV5642 parallel-bus sensor, and the OV5640 MIPI CSI-2 sensor.
> Both hang off the same i2c2 bus, so they require different (and non-
> default) i2c slave addresses.
>
> The OV5642 connects to the parallel-bus mux input port o
Hi Peter,
On 24.03.2016 13:05, Peter Rosin wrote:
> Hi Vladimir,
>
> On 2016-03-24 10:50, Vladimir Zapolskiy wrote:
>> Hi Peter,
>>
>> On 05.01.2016 17:57, Peter Rosin wrote:
>>> From: Peter Rosin
>>>
>>> The initial core mux structure sta
Hi Peter,
On 05.01.2016 17:57, Peter Rosin wrote:
> From: Peter Rosin
>
> The initial core mux structure starts off small with only the parent
> adapter pointer, which all muxes have, and a priv pointer for mux
> driver private data.
>
> Add i2c_mux_alloc function to unify the creation of a mux
On 16.03.2016 20:53, Heiner Kallweit wrote:
> Access to dev->initialized is atomic, therefore we don't have to
> protect it with a mutex.
Mutexes are used to split the code to mutually exclusive execution blocks,
so not arguing about the apparently correct change itself I want to
emphasize that th
On 15.03.2016 12:28, Antonio Ospite wrote:
> On Tue, 15 Mar 2016 09:10:59 +0200
> Ran Shalit wrote:
>
>> Hello,
>>
>> This is a bit offtopic, so I will understand if you rather not discuss
>> that...
>>
>> I am trying to use gstreamer with v4l2 vivi device,
>> I first check the capabilities with
The devm_gpiod_get() function returns either a valid pointer to
struct gpio_desc or ERR_PTR() error value, check for NULL is bogus.
Signed-off-by: Vladimir Zapolskiy
---
drivers/media/i2c/adp1653.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/adp1653
ned-off-by: Vladimir Zapolskiy
---
Documentation/video4linux/v4l2-controls.txt | 1 -
drivers/media/v4l2-core/v4l2-ctrls.c| 16
include/media/v4l2-ctrls.h | 12
3 files changed, 29 deletions(-)
diff --git a/Documentation/video4linux/v4l2-contr
e only one gen_pool
per device, this implies two possible error codes returned by the
function, account it on client side (only misc/sram). This completes
client side changes related to genalloc updates.
Signed-off-by: Vladimir Zapolskiy
Cc: Philipp Zabel
Cc: Greg Kroah-Hartman
Cc: Russell King
C
e only
one gen_pool per device, this implies two possible error codes
returned by the function, account it on client side (only misc/sram).
This completes client side changes related to genalloc updates.
Signed-off-by: Vladimir Zapolskiy
---
arch/arm/mach-at91/pm.c | 2 +-
arch/ar
- minor updates in of_gen_pool_get() change to respect OF_DYNAMIC
- instead of adding two new functions the existing functions
gen_pool_get() (at91, imx5m, imx6 and CODA driver clients) and
devm_gen_pool_create() (sram client) are updated.
Vladimir Zapolskiy (2):
genalloc: add name arg to gen
a gen_pool object.
Due to a weak relation and to avoid any confusion (e.g. in future
possible scenario if gen_pool objects are named) the suffix is
removed.
Signed-off-by: Vladimir Zapolskiy
---
drivers/dma/mmp_tdma.c| 2 +-
drivers/media/platform/coda/coda-common.c | 2 +
based and tested on linux-next.
Vladimir Zapolskiy (2):
genalloc: rename dev_get_gen_pool() to gen_pool_get()
genalloc: rename of_get_named_gen_pool() to of_gen_pool_get()
arch/arm/mach-at91/pm.c | 2 +-
arch/arm/mach-imx/pm-imx5.c | 2 +-
arch/arm/mach-imx
To be consistent with other genalloc interface namings, rename
dev_get_gen_pool() to gen_pool_get(). The original omitted "dev_"
prefix is removed, since it points to argument type of the function,
and so it does not bring any useful information.
Signed-off-by: Vladimir Zapolskiy
---
Cc:, because imx-hdmi->dw-hdmi]
>>
>> Am Montag, den 01.12.2014, 17:39 +0200 schrieb Vladimir Zapolskiy:
>>> On 01.12.2014 17:11, Philipp Zabel wrote:
>>>> Am Montag, den 01.12.2014, 16:54 +0200 schrieb Vladimir Zapolskiy:
>>>>> Hi Philipp and Sha
On 01.12.2014 17:11, Philipp Zabel wrote:
> Am Montag, den 01.12.2014, 16:54 +0200 schrieb Vladimir Zapolskiy:
>> Hi Philipp and Shawn,
>>
>> On 15.11.2014 19:49, Vladimir Zapolskiy wrote:
>>> Provide information about how to bind internal iMX6Q/DL HDMI DDC I2C
>&
Hi Philipp and Shawn,
On 15.11.2014 19:49, Vladimir Zapolskiy wrote:
> Provide information about how to bind internal iMX6Q/DL HDMI DDC I2C
> master controller. The property is set as optional one, because iMX6
> HDMI DDC bus may be represented by one of general purpose I2C busses
>
Provide information about how to bind internal iMX6Q/DL HDMI DDC I2C
master controller. The property is set as optional one, because iMX6
HDMI DDC bus may be represented by one of general purpose I2C busses
found on SoC.
Signed-off-by: Vladimir Zapolskiy
Cc: Wolfram Sang
Cc: Philipp Zabel
Cc
74 matches
Mail list logo
