vers/media/i2c/ov5693.c b/drivers/media/i2c/ov5693.c
> new file mode 100644
> index ..da2ca99a7ad3
> --- /dev/null
> +++ b/drivers/media/i2c/ov5693.c
> @@ -0,0 +1,1557 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (c) 2013 Intel Corporation. All Rights
When trying to convert a CCM matrix for IPU3, extreme values for the
Color Correction Matrix.
Specify the precision to ease userspace integration.
Signed-off-by: Jean-Michel Hautbois
---
drivers/staging/media/ipu3/include/intel-ipu3.h | 14 --
1 file changed, 8 insertions(+), 6
Hi Daniel,
Thanks for the patch !
On 30/11/2020 14:31, Daniel Scally wrote:
> On platforms where ACPI is designed for use with Windows, resources
> that are intended to be consumed by sensor devices are sometimes in
> the _CRS of a dummy INT3472 device upon which the sensor depends. This
>
Hi there !
Le mar. 6 nov. 2018 à 10:57, Alexander Dahl a écrit :
>
> Hei hei,
>
> Am Freitag, 2. November 2018, 14:35:26 CET schrieb Jean-Michel Hautbois:
> > Then, after looking into deeper details in the datasheet I understand
> > it is connected through EBI and
Hi there !
Le mar. 6 nov. 2018 à 10:57, Alexander Dahl a écrit :
>
> Hei hei,
>
> Am Freitag, 2. November 2018, 14:35:26 CET schrieb Jean-Michel Hautbois:
> > Then, after looking into deeper details in the datasheet I understand
> > it is connected through EBI and
Hi all,
I have a custom board based on a sama5d3 chip. The SoC is connected to
2 pef24628 SHDSL transceivers, the first one on ebi@4000 and the
second one on ebi@5000.
I tried to write a basic char driver, using request_mem_region and
ioremap but I can't read or write into the device.
I
Hi all,
I have a custom board based on a sama5d3 chip. The SoC is connected to
2 pef24628 SHDSL transceivers, the first one on ebi@4000 and the
second one on ebi@5000.
I tried to write a basic char driver, using request_mem_region and
ioremap but I can't read or write into the device.
I
Hi !
2016-02-01 15:46 GMT+01:00 Rob Herring <r...@kernel.org>:
> On Sun, Jan 31, 2016 at 04:33:00PM +0100, Jean-Michel Hautbois wrote:
>> Some I2C devices have multiple addresses assigned, for example each address
>> corresponding to a different internal register map page of
Hi !
2016-02-01 15:46 GMT+01:00 Rob Herring :
> On Sun, Jan 31, 2016 at 04:33:00PM +0100, Jean-Michel Hautbois wrote:
>> Some I2C devices have multiple addresses assigned, for example each address
>> corresponding to a different internal register map page of the device.
>>
Hi Rob,
Thanks a lot for your review !
2016-02-09 1:15 GMT+01:00 Rob Herring :
> On Mon, Feb 08, 2016 at 12:20:24PM +0100, Jean-Michel Hautbois wrote:
>> This device is a SPI based device from TI.
>> It is a 3 Gbps HD/SD SDI Dual Output Low Power
>> Extended Reach Ada
Hi Rob,
Thanks a lot for your review !
2016-02-09 1:15 GMT+01:00 Rob Herring <r...@kernel.org>:
> On Mon, Feb 08, 2016 at 12:20:24PM +0100, Jean-Michel Hautbois wrote:
>> This device is a SPI based device from TI.
>> It is a 3 Gbps HD/SD SDI Dual Output Low Power
>> Ex
is on bus SPI2 with CS number 1.
Controls should be accessible from userspace too.
This will have to be done later.
Signed-off-by: Jean-Michel Hautbois
---
v2: Add DT support
v3: Change the bit set/clear in output_type as disabled means 'set the bit'
v4: Clearer description of endpoints usage
is on bus SPI2 with CS number 1.
Controls should be accessible from userspace too.
This will have to be done later.
Signed-off-by: Jean-Michel Hautbois <jean-michel.hautb...@veo-labs.com>
---
v2: Add DT support
v3: Change the bit set/clear in output_type as disabled means 'set the bit'
v4: C
the function returns NULL.
For now the function only supports look-up of the secondary address
from devicetree, but it can be extended in the future
to for example support board files and/or ACPI.
Signed-off-by: Jean-Michel Hautbois
---
v2: adding some DT bindings documentation (more than one
the function returns NULL.
For now the function only supports look-up of the secondary address
from devicetree, but it can be extended in the future
to for example support board files and/or ACPI.
Signed-off-by: Jean-Michel Hautbois <jean-michel.hautb...@veo-labs.com>
---
v2: adding s
Hi Russell,
2015-08-27 10:42 GMT+02:00 Philipp Zabel :
>
> Am Samstag, den 08.08.2015, 17:09 +0100 schrieb Russell King - ARM
> Linux:
> > Following on from the previous sub-series, this sub-series adds audio
> > support to dw-hdmi.
> >
> > The two different variants are now in this patch: AHB
Hi Russell,
2015-08-27 10:42 GMT+02:00 Philipp Zabel :
>
> Am Samstag, den 08.08.2015, 17:09 +0100 schrieb Russell King - ARM
> Linux:
> > Following on from the previous sub-series, this sub-series adds audio
> > support to dw-hdmi.
> >
> > The two different variants are
When power up, a "pop" is heard on line-in and mic-in.
An analysis of the PCM shows it lasts ~400ms
and looks like a filter response.
VAG power up should be delayed by 400ms as VAG power down is.
Signed-off-by: Jean-Michel Hautbois
---
sound/soc/codecs/sgtl5000.c | 1 +
1 file
When power up, a "pop" is heard on line-in and mic-in.
An analysis of the PCM shows it lasts ~400ms
and looks like a filter response.
VAG power up should be delayed by 400ms as VAG power down is.
Signed-off-by: Jean-Michel Hautbois <jean-michel.hautb...@veo-labs.com>
---
2015-11-06 20:12 GMT+01:00 Joshua Clayton :
> On Friday, November 06, 2015 05:32:30 PM Jean-Michel Hautbois wrote:
>> Hi !
>>
>> I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
>> When I connect a USB key, and then disconnect it, it oopses and
Hi Arnd,
2015-11-06 17:38 GMT+01:00 Arnd Bergmann :
> On Friday 06 November 2015 17:32:30 Jean-Michel Hautbois wrote:
>> I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
>> When I connect a USB key, and then disconnect it, it oopses and
>> reboots (as
Hi !
I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
When I connect a USB key, and then disconnect it, it oopses and
reboots (as I have panic on oops, and reboot on panic).
Seems to be on the umount part...
The USB is connected through a smsc95xx but I don't think this
2015-11-06 20:12 GMT+01:00 Joshua Clayton <joshua.clay...@uniwest.com>:
> On Friday, November 06, 2015 05:32:30 PM Jean-Michel Hautbois wrote:
>> Hi !
>>
>> I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
>> When I connect a USB key,
Hi !
I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
When I connect a USB key, and then disconnect it, it oopses and
reboots (as I have panic on oops, and reboot on panic).
Seems to be on the umount part...
The USB is connected through a smsc95xx but I don't think this
Hi Arnd,
2015-11-06 17:38 GMT+01:00 Arnd Bergmann <a...@arndb.de>:
> On Friday 06 November 2015 17:32:30 Jean-Michel Hautbois wrote:
>> I have an issue on my i.MX6 board I don't understand (kernel is a 4.2)...
>> When I connect a USB key, and then disconnect it, it oopses
2015-11-04 18:04 GMT+01:00 Jon Nettleton :
> On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
> wrote:
>> Hi !
>>
>> I can see in FSL kernel that VPU is configurable to 352M (it defaults
>> at 264MHz in mainline I think).
>> In the TRM, it is even specif
Hi !
I can see in FSL kernel that VPU is configurable to 352M (it defaults
at 264MHz in mainline I think).
In the TRM, it is even specified at 352MHz as a default frequency,
with a maximum of 540MHz.
Would it be possible to allow this clock rating modification if, for
instance, we select a
2015-11-04 18:04 GMT+01:00 Jon Nettleton <jon.nettle...@gmail.com>:
> On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
> <jean-michel.hautb...@veo-labs.com> wrote:
>> Hi !
>>
>> I can see in FSL kernel that VPU is configurable to 352M (it defau
Hi !
I can see in FSL kernel that VPU is configurable to 352M (it defaults
at 264MHz in mainline I think).
In the TRM, it is even specified at 352MHz as a default frequency,
with a maximum of 540MHz.
Would it be possible to allow this clock rating modification if, for
instance, we select a
A copy-paste from DECODER_CMD : replace decoded by encoded.
Signed-off-by: Jean-Michel Hautbois
---
Documentation/DocBook/media/v4l/vidioc-encoder-cmd.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/DocBook/media/v4l/vidioc-encoder-cmd.xml
b/Documentation
A copy-paste from DECODER_CMD : replace decoded by encoded.
Signed-off-by: Jean-Michel Hautbois <jean-michel.hautb...@veo-labs.com>
---
Documentation/DocBook/media/v4l/vidioc-encoder-cmd.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/DocBook/med
2015-09-19 19:56 GMT+02:00 Mark Brown :
> On Fri, Sep 18, 2015 at 02:38:27PM +0200, Jean-Michel Hautbois wrote:
>> Hi,
>>
>> I am wondering why in spi-imx the spi_imx_pio_transfer() function is
>> calling wait_for_completion() and not wait_for_completion_timeout() as
>
2015-09-19 19:56 GMT+02:00 Mark Brown <broo...@kernel.org>:
> On Fri, Sep 18, 2015 at 02:38:27PM +0200, Jean-Michel Hautbois wrote:
>> Hi,
>>
>> I am wondering why in spi-imx the spi_imx_pio_transfer() function is
>> calling wait_for_completion() an
Hi,
I am wondering why in spi-imx the spi_imx_pio_transfer() function is
calling wait_for_completion() and not wait_for_completion_timeout() as
in the spi_imx_dma_transfer() one.
I can't see a good reason for this, maybe should it be calculated
based on the spi clock and transfer->len, or at
Hi,
I am wondering why in spi-imx the spi_imx_pio_transfer() function is
calling wait_for_completion() and not wait_for_completion_timeout() as
in the spi_imx_dma_transfer() one.
I can't see a good reason for this, maybe should it be calculated
based on the spi clock and transfer->len, or at
Hi,
I am planning to add support for DT parsing in the Lattice ECP3 driver.
The main goal is to add support for INITN, DONE and PROGRAMN pins,
which should be driven when programming the FPGA, according to the
doc.
Basic question, what should be used in the of_device_id compatible field ?
For
Hi,
I am planning to add support for DT parsing in the Lattice ECP3 driver.
The main goal is to add support for INITN, DONE and PROGRAMN pins,
which should be driven when programming the FPGA, according to the
doc.
Basic question, what should be used in the of_device_id compatible field ?
For
All masks for timings are different between ADV7604 and ADV7611.
Most of the values have 1 precision bit more in the latter.
Fix this by adding new fields to the chip_info structure.
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 69
All masks for timings are different between ADV7604 and ADV7611.
Most of the values have 1 precision bit more in the latter.
Fix this by adding new fields to the chip_info structure.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/media/i2c/adv7604.c | 69
Hi Tim,
2015-03-24 16:11 GMT+01:00 Tim Harvey :
> On Tue, Feb 24, 2015 at 1:36 PM, Jean-Michel Hautbois
> wrote:
>> Hi Tim,
>>
>> 2014-10-31 5:27 GMT+01:00 Tim Harvey :
>>> The IMX6 has some internal LDO regulators provided by the anatop regulator
>>>
Hi Tim,
2015-03-24 16:11 GMT+01:00 Tim Harvey thar...@gateworks.com:
On Tue, Feb 24, 2015 at 1:36 PM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Hi Tim,
2014-10-31 5:27 GMT+01:00 Tim Harvey thar...@gateworks.com:
The IMX6 has some internal LDO regulators provided by the anatop
All drivers use custom notifications, in particular when source changes.
The bridge only has to map the subdev that sends it to whatever video node it
is connected to.
Signed-off-by: Jean-Michel Hautbois
---
Documentation/video4linux/v4l2-framework.txt | 4
include/media/v4l2-subdev.h
All drivers use custom notifications, in particular when source changes.
The bridge only has to map the subdev that sends it to whatever video node it
is connected to.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
Documentation/video4linux/v4l2-framework.txt | 4
Hi Sudip,
2015-02-25 19:23 GMT+01:00 Jeremiah Mahler :
> Sudip,
>
> On Wed, Feb 25, 2015 at 03:29:22PM +0800, Sudip JAIN wrote:
>> Dear Maintainer,
>>
>> PFA attached patch that prevents user from being returned garbage bytesused
>> value from vb2 framework.
>>
>> Regards,
>> Sudip Jain
>>
>
>
Hi Sudip,
2015-02-25 19:23 GMT+01:00 Jeremiah Mahler jmmah...@gmail.com:
Sudip,
On Wed, Feb 25, 2015 at 03:29:22PM +0800, Sudip JAIN wrote:
Dear Maintainer,
PFA attached patch that prevents user from being returned garbage bytesused
value from vb2 framework.
Regards,
Sudip Jain
Hi Tim,
2014-10-31 5:27 GMT+01:00 Tim Harvey :
> The IMX6 has some internal LDO regulators provided by the anatop regulator
> block that can regulate the arm, soc, gpu/vpu core supplies. Alternatively a
> design can supply vdd_arm and vdd_soc externally via a PMIC to provide a lower
> power draw
Hi Tim,
2014-10-31 5:27 GMT+01:00 Tim Harvey thar...@gateworks.com:
The IMX6 has some internal LDO regulators provided by the anatop regulator
block that can regulate the arm, soc, gpu/vpu core supplies. Alternatively a
design can supply vdd_arm and vdd_soc externally via a PMIC to provide a
The CP_NON_STD_VIDEO bit indicates an input not aligned with DV timings.
If there is no input, and chip is in free run mode, consider we are locked.
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff
The CP_NON_STD_VIDEO bit indicates an input not aligned with DV timings.
If there is no input, and chip is in free run mode, consider we are locked.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/media/i2c/adv7604.c | 14 +++---
1 file changed, 11
The bits are the same, but register is 0xf4 on ADV7611 instead of 0xfc.
When reading back the value in log_status, differentiate both.
Signed-off-by: Jean-Michel Hautbois
---
v2: Use adv7604_chip_info to get register instead of testing the chip ID
drivers/media/i2c/adv7604.c | 5 -
1 file
s (both for functions and defines) to
>> adv76xx whenever they are common.
>>
>> Signed-off-by: Pablo Anton
>> Signed-off-by: Jean-Michel Hautbois
>
> I'm happy with this, except for three small changes:
>
> - I had to rebase
Sorry about that, not the media-tree used f
for functions and defines) to
adv76xx whenever they are common.
Signed-off-by: Pablo Anton pablo.an...@vodalys-labs.com
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
I'm happy with this, except for three small changes:
- I had to rebase
Sorry about that, not the media-tree used
The bits are the same, but register is 0xf4 on ADV7611 instead of 0xfc.
When reading back the value in log_status, differentiate both.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
v2: Use adv7604_chip_info to get register instead of testing the chip ID
drivers/media
This is a preliminary patch in order to add support for ALSA.
It replaces all current i2c access with regmap.
Add the registers which will then be used too, as these are declared at init.
Signed-off-by: Pablo Anton
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 428
This is a preliminary patch in order to add support for ALSA.
It replaces all current i2c access with regmap.
Add the registers which will then be used too, as these are declared at init.
Signed-off-by: Pablo Anton pablo.an...@vodalys-labs.com
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb
The bits are the same, but register is 0xf4 on ADV7611 instead of 0xfc.
When reading back the value in log_status, differentiate both.
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c
The bits are the same, but register is 0xf4 on ADV7611 instead of 0xfc.
When reading back the value in log_status, differentiate both.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/media/i2c/adv7604.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion
Hi Laurent,
Thanks for the review.
2014-11-03 14:13 GMT+01:00 Laurent Pinchart :
> Hi Jean-Michel,
>
> Thank you for the patch.
>
> On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
>> This device is a SPI based device from TI.
>> It is a 3 Gbps HD/S
Hi,
2014-10-27 0:30 GMT+01:00 Laurent Pinchart :
> Hi Jean-Michel,
>
> On Thursday 23 October 2014 07:51:50 Jean-Michel Hautbois wrote:
>> 2014-10-23 1:53 GMT+02:00 Laurent Pinchart:
>> > On Wednesday 22 October 2014 17:34:21 Jean-Michel Hautbois wrote:
>> >
Hi,
2014-10-27 0:30 GMT+01:00 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi Jean-Michel,
On Thursday 23 October 2014 07:51:50 Jean-Michel Hautbois wrote:
2014-10-23 1:53 GMT+02:00 Laurent Pinchart:
On Wednesday 22 October 2014 17:34:21 Jean-Michel Hautbois wrote:
This patch adds
Hi Laurent,
Thanks for the review.
2014-11-03 14:13 GMT+01:00 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi Jean-Michel,
Thank you for the patch.
On Wednesday 10 September 2014 11:43:54 Jean-Michel Hautbois wrote:
This device is a SPI based device from TI.
It is a 3 Gbps HD/SD
2014-12-16 15:50 GMT+01:00 Nicolas Dufresne :
>
> Le 2014-12-16 09:27, Jean-Michel Hautbois a écrit :
>>
>> Have you already started something about that ?
>
> Yes, currently I do cropping right if there is no scaling. Doing this with
> S_CROP is really ackward, but v
2014-12-16 15:50 GMT+01:00 Nicolas Dufresne nicolas.dufre...@collabora.com:
Le 2014-12-16 09:27, Jean-Michel Hautbois a écrit :
Have you already started something about that ?
Yes, currently I do cropping right if there is no scaling. Doing this with
S_CROP is really ackward, but very few
Hi,
2014-12-16 15:15 GMT+01:00 Nicolas Dufresne :
>
> Le 2014-12-16 08:30, Philipp Zabel a écrit :
>>
>> For the IPU IC mem2mem scaler/CSC, v4l2transform with scaling capability
>> would be the perfect fit
>
> Thanks you for clarifying. Jean-Michel, are you going to work on this ? If
> so, feel
Hi,
2014-12-16 15:15 GMT+01:00 Nicolas Dufresne nicolas.dufre...@collabora.com:
Le 2014-12-16 08:30, Philipp Zabel a écrit :
For the IPU IC mem2mem scaler/CSC, v4l2transform with scaling capability
would be the perfect fit
Thanks you for clarifying. Jean-Michel, are you going to work on
2014-12-15 19:52 GMT+01:00 Nicolas Dufresne :
>
>
> Le 12/15/2014 01:23 PM, Steve Longerbeam a écrit :
>> You would need to write a gstreamer plugin to make use of the
>> mem2mem device for h/w CSC and scaling.
Thank you Steve, this is of a great help !
> There is an element already
Hi Steve, Philipp,
I see in the kernel sources you created a ipu-ic.c file which helps
working with the Color Space Converter on i.MX6.
We would like to use it on our board with GStreamer, as the conversion
done by the CPU is not very efficient :).
What is the easiest/best approach to this ?
Hi Steve, Philipp,
I see in the kernel sources you created a ipu-ic.c file which helps
working with the Color Space Converter on i.MX6.
We would like to use it on our board with GStreamer, as the conversion
done by the CPU is not very efficient :).
What is the easiest/best approach to this ?
2014-12-15 19:52 GMT+01:00 Nicolas Dufresne nicolas.dufre...@collabora.com:
Le 12/15/2014 01:23 PM, Steve Longerbeam a écrit :
You would need to write a gstreamer plugin to make use of the
mem2mem device for h/w CSC and scaling.
Thank you Steve, this is of a great help !
There is an
2014-12-03 17:07 GMT+01:00 Grant Likely :
> On Wed, Dec 3, 2014 at 4:04 PM, Fabio Estevam wrote:
>> On Wed, Dec 3, 2014 at 1:41 PM, Grant Likely
>> wrote:
>>
>>> From a quick reading of the backlog, for some reason the new device is
>>> getting assigned NULL as the device name in
2014-12-03 16:22 GMT+01:00 Grant Likely :
> On Wed, Dec 3, 2014 at 1:27 PM, Jean-Michel Hautbois
> wrote:
>> Hi,
>>
>> I am using linux-next on a i.MX6 board, and it seems that there is a
>> regression probably in DT parsing.
>
> Are you able to bisect down t
Hi,
I am using linux-next on a i.MX6 board, and it seems that there is a
regression probably in DT parsing.
Here is the DT I am using :
vbx-leds {
compatible = "gpio-leds";
pinctrl-names = "default";
pinctrl-0 = <_gpio_leds>;
led0-red {
gpios = <
Hi,
I am using linux-next on a i.MX6 board, and it seems that there is a
regression probably in DT parsing.
Here is the DT I am using :
vbx-leds {
compatible = gpio-leds;
pinctrl-names = default;
pinctrl-0 = pinctrl_gpio_leds;
led0-red {
gpios =
2014-12-03 16:22 GMT+01:00 Grant Likely grant.lik...@secretlab.ca:
On Wed, Dec 3, 2014 at 1:27 PM, Jean-Michel Hautbois
jean-michel.hautb...@vodalys.com wrote:
Hi,
I am using linux-next on a i.MX6 board, and it seems that there is a
regression probably in DT parsing.
Are you able to bisect
2014-12-03 17:07 GMT+01:00 Grant Likely grant.lik...@secretlab.ca:
On Wed, Dec 3, 2014 at 4:04 PM, Fabio Estevam feste...@gmail.com wrote:
On Wed, Dec 3, 2014 at 1:41 PM, Grant Likely grant.lik...@secretlab.ca
wrote:
From a quick reading of the backlog, for some reason the new device is
In order to have v4l2-compliance tool pass the G/S_EDID some modifications
where needed in the driver.
In particular, the edid.reserved zone must be blanked.
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 24
1 file changed, 16 insertions(+), 8
In order to have v4l2-compliance tool pass the G/S_EDID some modifications
where needed in the driver.
In particular, the edid.reserved zone must be blanked.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/media/i2c/adv7604.c | 24
1 file
Hi Laurent,
Thank you for reviewing,
2014-10-23 1:44 GMT+02:00 Laurent Pinchart :
> Hi Jean-Michel,
>
> Thank you for the patch.
>
> On Wednesday 22 October 2014 17:30:48 Jean-Michel Hautbois wrote:
>> The ADV7604 has thirteen 256-byte maps that can be accessed via the ma
Hi Laurent,
Thank you for your review,
2014-10-23 1:37 GMT+02:00 Laurent Pinchart :
> Hi Jean-Michel,
>
> Thank you for the patch.
>
> On Wednesday 22 October 2014 17:30:47 Jean-Michel Hautbois wrote:
>> Some I2C devices have multiple addresses assigned, for example each add
Hi Laurent,
Thank you for your review,
2014-10-23 1:37 GMT+02:00 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi Jean-Michel,
Thank you for the patch.
On Wednesday 22 October 2014 17:30:47 Jean-Michel Hautbois wrote:
Some I2C devices have multiple addresses assigned, for example
Hi Laurent,
Thank you for reviewing,
2014-10-23 1:44 GMT+02:00 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi Jean-Michel,
Thank you for the patch.
On Wednesday 22 October 2014 17:30:48 Jean-Michel Hautbois wrote:
The ADV7604 has thirteen 256-byte maps that can be accessed via
Hi Laurent,
Thank you for reviewing,
2014-10-23 1:53 GMT+02:00 Laurent Pinchart :
> Hi Jean-Michel,
>
> Thank you for the patch.
>
> On Wednesday 22 October 2014 17:34:21 Jean-Michel Hautbois wrote:
>> This patch adds support for DT parsing of ADV7604 as well as
This patch adds support for DT parsing of ADV7604 as well as ADV7611.
It needs to be improved in order to get ports parsing too.
Signed-off-by: Jean-Michel Hautbois
---
Documentation/devicetree/bindings/media/i2c/adv7604.txt | 1 +
drivers/media/i2c/adv7604.c | 1
-Michel Hautbois
---
.../devicetree/bindings/media/i2c/adv7604.txt | 16 +-
drivers/media/i2c/adv7604.c| 59 ++
2 files changed, 53 insertions(+), 22 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/adv7604.txt
b
the function returns NULL.
For now the function only supports look-up of the secondary address
from devicetree, but it can be extended in the future
to for example support board files and/or ACPI.
Signed-off-by: Jean-Michel Hautbois
---
drivers/i2c/i2c-core.c | 40
Hi Laurent,
Thank you for reviewing,
2014-10-23 1:53 GMT+02:00 Laurent Pinchart laurent.pinch...@ideasonboard.com:
Hi Jean-Michel,
Thank you for the patch.
On Wednesday 22 October 2014 17:34:21 Jean-Michel Hautbois wrote:
This patch adds support for DT parsing of ADV7604 as well as ADV7611
the function returns NULL.
For now the function only supports look-up of the secondary address
from devicetree, but it can be extended in the future
to for example support board files and/or ACPI.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/i2c/i2c-core.c
-Michel Hautbois jean-michel.hautb...@vodalys.com
---
.../devicetree/bindings/media/i2c/adv7604.txt | 16 +-
drivers/media/i2c/adv7604.c| 59 ++
2 files changed, 53 insertions(+), 22 deletions(-)
diff --git a/Documentation/devicetree/bindings
This patch adds support for DT parsing of ADV7604 as well as ADV7611.
It needs to be improved in order to get ports parsing too.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
Documentation/devicetree/bindings/media/i2c/adv7604.txt | 1 +
drivers/media/i2c/adv7604.c
2014-09-21 19:48 GMT+02:00 Pavel Machek :
> On Mon 2014-09-15 19:44:28, Jaehoon Chung wrote:
>> On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
>> > Hi Jaehoon,
>> >
>> >> On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
>> >>
2014-09-21 19:48 GMT+02:00 Pavel Machek pa...@ucw.cz:
On Mon 2014-09-15 19:44:28, Jaehoon Chung wrote:
On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
Hi Jaehoon,
On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
Tested on a i.MX6 board, with Sandisk SDIN5D1-2G.
Without
Hi,
I have a custom i.MX6 board, and have a sgtl5000 connected on it. I
would like to have it used in master mode (it is used only for audio
capture) but I get a "pcm_read:2031: read error: Input/output error"
when using arecord.
I am wondering if I forgot something in my DT or if I need to do
Hi,
I have a custom i.MX6 board, and have a sgtl5000 connected on it. I
would like to have it used in master mode (it is used only for audio
capture) but I get a pcm_read:2031: read error: Input/output error
when using arecord.
I am wondering if I forgot something in my DT or if I need to do
2014-09-15 12:53 GMT+02:00 Jean-Michel Hautbois
:
> 2014-09-15 12:44 GMT+02:00 Jaehoon Chung :
>> On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
>>> Hi Jaehoon,
>>>
>>>> On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
>>>>> Tested on
2014-09-15 12:44 GMT+02:00 Jaehoon Chung :
> On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
>> Hi Jaehoon,
>>
>>> On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
>>>> Tested on a i.MX6 board, with Sandisk SDIN5D1-2G.
>>>> Without this patch
Hi Jaehoon,
> On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
>> Tested on a i.MX6 board, with Sandisk SDIN5D1-2G.
>> Without this patch, I/O errors occur.
>> This eMMC seems to have a different Manufacturer ID as it reads 0x45
>> and not 0x2 as specified in datash
Hi Jaehoon,
On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
Tested on a i.MX6 board, with Sandisk SDIN5D1-2G.
Without this patch, I/O errors occur.
This eMMC seems to have a different Manufacturer ID as it reads 0x45
and not 0x2 as specified in datasheet.
I think this patch don't merge
2014-09-15 12:44 GMT+02:00 Jaehoon Chung jh80.ch...@samsung.com:
On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
Hi Jaehoon,
On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
Tested on a i.MX6 board, with Sandisk SDIN5D1-2G.
Without this patch, I/O errors occur.
This eMMC seems
2014-09-15 12:53 GMT+02:00 Jean-Michel Hautbois
jean-michel.hautb...@vodalys.com:
2014-09-15 12:44 GMT+02:00 Jaehoon Chung jh80.ch...@samsung.com:
On 09/15/2014 07:08 PM, Jean-Michel Hautbois wrote:
Hi Jaehoon,
On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote:
Tested on a i.MX6 board
.
v2: Add DT support
v3: Change the bit set/clear in output_type as disabled means 'set the bit'
v4: Clearer description of endpoints usage in Doc, and some init changes.
Add a dependency on OF and don't test CONFIG_OF anymore.
Signed-off-by: Jean-Michel Hautbois
---
.../devicetree/bindings
1 - 100 of 165 matches
Mail list logo