Patch submission to Freescale kernel

Patch submission to Freescale kernel

[Gary Bisson]

Hi,

I was wondering what was the procedure to submit a patch to the 
Freescale maintained kernel:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/

I've just made a patch that fixes the display issue for rev T1.0 of the 
SoC which has been previously reported:
https://lists.yoctoproject.org/pipermail/meta-freescale/2014-May/008553.html
"mxc_sdc_fb fb.27: timeout when waiting for flip irq"

Then, I'd like to send that patch over to the fslc and mainline kernels 
as they seem to have the issue by checking their source code.

Regarding the mainline kernel, I can't seem to get the HDMI (on 
nitrogen6x) to work at all no matter which revision/board I use. Looking 
into the source code I've seen the evolution of the 
drivers/staging/imx-drm driver which tends to say that HDMI is 
supported. If so, would anyone have some insights on which command line 
to pass the kernel in order to get the mainline kernel to recognize the 
HDMI display properly. So far the init seems to be fine but fb0 sysfs 
modes is just rubbish.
[    1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops 
ipu_crtc_ops)
[    1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops 
ipu_crtc_ops)
[    1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops 
ipu_crtc_ops)
[    1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops 
ipu_crtc_ops)
[    1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller 
0x13:0xa:0xa0:0xc1
[    1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
[    1.868537] imx-drm display-subsystem: bound 
2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)

Thanks,
Gary

Re: Patch submission to Freescale kernel

[Otavio Salvador]

Hello Gary,

On Tue, Dec 2, 2014 at 2:18 AM, Gary Bisson <bisson.gary@gmail.com> wrote:
> I was wondering what was the procedure to submit a patch to the Freescale
> maintained kernel:
> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/

Please prepare a patch and include it in linux-imx recipe; this allow
us to include it in core BSP and than ask for Freescale to review it.

> I've just made a patch that fixes the display issue for rev T1.0 of the SoC
> which has been previously reported:
> https://lists.yoctoproject.org/pipermail/meta-freescale/2014-May/008553.html
> "mxc_sdc_fb fb.27: timeout when waiting for flip irq"

Nice!

> Then, I'd like to send that patch over to the fslc and mainline kernels as
> they seem to have the issue by checking their source code.

For mainline, it seems LKML is the right place.

> Regarding the mainline kernel, I can't seem to get the HDMI (on nitrogen6x)
> to work at all no matter which revision/board I use. Looking into the source
> code I've seen the evolution of the drivers/staging/imx-drm driver which
> tends to say that HDMI is supported. If so, would anyone have some insights
> on which command line to pass the kernel in order to get the mainline kernel
> to recognize the HDMI display properly. So far the init seems to be fine but
> fb0 sysfs modes is just rubbish.
> [    1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops
> ipu_crtc_ops)
> [    1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops
> ipu_crtc_ops)
> [    1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops
> ipu_crtc_ops)
> [    1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops
> ipu_crtc_ops)
> [    1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller
> 0x13:0xa:0xa0:0xc1
> [    1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
> [    1.868537] imx-drm display-subsystem: bound
> 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)

Eric?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Patch submission to Freescale kernel

[Gary Bisson]

Hello Otavio,

On 12/02/2014 02:42 AM, Otavio Salvador wrote:
> Hello Gary,
>
> On Tue, Dec 2, 2014 at 2:18 AM, Gary Bisson <bisson.gary@gmail.com> wrote:
>> I was wondering what was the procedure to submit a patch to the Freescale
>> maintained kernel:
>> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/
> Please prepare a patch and include it in linux-imx recipe; this allow
> us to include it in core BSP and than ask for Freescale to review it.

Will do the patch today.

Thanks for the quick feedback!
Gary

Re: Patch submission to Freescale kernel

[Fabio Estevam]

On Tue, Dec 2, 2014 at 2:18 AM, Gary Bisson <bisson.gary@gmail.com> wrote:

> Regarding the mainline kernel, I can't seem to get the HDMI (on nitrogen6x)
> to work at all no matter which revision/board I use. Looking into the source
> code I've seen the evolution of the drivers/staging/imx-drm driver which
> tends to say that HDMI is supported. If so, would anyone have some insights
> on which command line to pass the kernel in order to get the mainline kernel
> to recognize the HDMI display properly. So far the init seems to be fine but
> fb0 sysfs modes is just rubbish.
> [    1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops
> ipu_crtc_ops)
> [    1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops
> ipu_crtc_ops)
> [    1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops
> ipu_crtc_ops)
> [    1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops
> ipu_crtc_ops)
> [    1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller
> 0x13:0xa:0xa0:0xc1
> [    1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
> [    1.868537] imx-drm display-subsystem: bound
> 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)

Could you try disabling the LVDS node to see if this helps?

Re: Patch submission to Freescale kernel

[Eric Nelson]

Hi Gary,

On 12/01/2014 09:18 PM, Gary Bisson wrote:
> Hi,
> 
> I was wondering what was the procedure to submit a patch to the
> Freescale maintained kernel:
> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/
> 
> I've just made a patch that fixes the display issue for rev T1.0 of the
> SoC which has been previously reported:
> https://lists.yoctoproject.org/pipermail/meta-freescale/2014-May/008553.html
> 
> "mxc_sdc_fb fb.27: timeout when waiting for flip irq"
> 
> Then, I'd like to send that patch over to the fslc and mainline kernels
> as they seem to have the issue by checking their source code.
> 

Cool! That discussion on i.MX Community ended with the realization
that the issue was specific to TO 1.0 silicon.

Are you running on that silicon version? (this is shown in the first
few lines of U-Boot output)

> Regarding the mainline kernel, I can't seem to get the HDMI (on
> nitrogen6x) to work at all no matter which revision/board I use. Looking
> into the source code I've seen the evolution of the
> drivers/staging/imx-drm driver which tends to say that HDMI is
> supported. If so, would anyone have some insights on which command line
> to pass the kernel in order to get the mainline kernel to recognize the
> HDMI display properly. So far the init seems to be fine but fb0 sysfs
> modes is just rubbish.
> [    1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops
> ipu_crtc_ops)
> [    1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops
> ipu_crtc_ops)
> [    1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops
> ipu_crtc_ops)
> [    1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops
> ipu_crtc_ops)
> [    1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller
> 0x13:0xa:0xa0:0xc1
> [    1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
> [    1.868537] imx-drm display-subsystem: bound
> 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)
> 

Hmmm. This worked for me the last time I checked (using Shawn's tree).

I'll double check and report back.

Regards,


Eric

Re: Patch submission to Freescale kernel

[Gary Bisson]

Eric, All,

On 12/02/2014 07:05 AM, Eric Nelson wrote:
> Hi Gary,
>
> On 12/01/2014 09:18 PM, Gary Bisson wrote:
>> Hi,
>>
>> I was wondering what was the procedure to submit a patch to the
>> Freescale maintained kernel:
>> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/
>>
>> I've just made a patch that fixes the display issue for rev T1.0 of the
>> SoC which has been previously reported:
>> https://lists.yoctoproject.org/pipermail/meta-freescale/2014-May/008553.html
>>
>> "mxc_sdc_fb fb.27: timeout when waiting for flip irq"
>>
>> Then, I'd like to send that patch over to the fslc and mainline kernels
>> as they seem to have the issue by checking their source code.
>>
> Cool! That discussion on i.MX Community ended with the realization
> that the issue was specific to TO 1.0 silicon.
>
> Are you running on that silicon version? (this is shown in the first
> few lines of U-Boot output)

Yes I confirm I am running on this revision and the (ridiculously small) 
patch happens in those IMX_CHIP_REVISION test cases.

>> Regarding the mainline kernel, I can't seem to get the HDMI (on
>> nitrogen6x) to work at all no matter which revision/board I use. Looking
>> into the source code I've seen the evolution of the
>> drivers/staging/imx-drm driver which tends to say that HDMI is
>> supported. If so, would anyone have some insights on which command line
>> to pass the kernel in order to get the mainline kernel to recognize the
>> HDMI display properly. So far the init seems to be fine but fb0 sysfs
>> modes is just rubbish.
>> [    1.863506] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops
>> ipu_crtc_ops)
>> [    1.863719] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops
>> ipu_crtc_ops)
>> [    1.863955] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops
>> ipu_crtc_ops)
>> [    1.864168] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops
>> ipu_crtc_ops)
>> [    1.867758] imx-hdmi 120000.hdmi: Detected HDMI controller
>> 0x13:0xa:0xa0:0xc1
>> [    1.868066] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
>> [    1.868537] imx-drm display-subsystem: bound
>> 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)
>>
> Hmmm. This worked for me the last time I checked (using Shawn's tree).
>
> I'll double check and report back.

Great thanks! I suspect my command line to be wrong though as I think 
mxcfb0 video parameters do not apply on mainline.

But I'll try out Fabio's suggestion of removing the LVDS node.

Thanks,
Gary

[PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

It looks like a few patches are missing for SABRE Lite.

The following is essentially an aggregation of these patches
for Nitrogen6x in main-line:
	43c3c00 - ARM: dts: nitrogen6x: add i2c2
	d653620 - ARM: dts: nitrogen6x: add hdmi
	1dffdd6 - ARM: dts: nitrogen6x: add i2c3

Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
---
 arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 33 ++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
index 0a36129..0b28a9d 100644
--- a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
@@ -173,6 +173,11 @@
 	status = "okay";
 };
 
+&hdmi {
+	ddc-i2c-bus = <&i2c2>;
+	status = "okay";
+};
+
 &i2c1 {
 	clock-frequency = <100000>;
 	pinctrl-names = "default";
@@ -188,6 +193,20 @@
 	};
 };
 
+&i2c2 {
+	clock-frequency = <100000>;
+	pinctrl-names = "default";
+	pinctrl-0 = <&pinctrl_i2c2>;
+	status = "okay";
+};
+
+&i2c3 {
+	clock-frequency = <100000>;
+	pinctrl-names = "default";
+	pinctrl-0 = <&pinctrl_i2c3>;
+	status = "okay";
+};
+
 &iomuxc {
 	pinctrl-names = "default";
 	pinctrl-0 = <&pinctrl_hog>;
@@ -265,6 +284,20 @@
 			>;
 		};
 
+		pinctrl_i2c2: i2c2grp {
+			fsl,pins = <
+				MX6QDL_PAD_KEY_COL3__I2C2_SCL		0x4001b8b1
+				MX6QDL_PAD_KEY_ROW3__I2C2_SDA		0x4001b8b1
+			>;
+		};
+
+		pinctrl_i2c3: i2c3grp {
+			fsl,pins = <
+				MX6QDL_PAD_GPIO_5__I2C3_SCL		0x4001b8b1
+				MX6QDL_PAD_GPIO_16__I2C3_SDA		0x4001b8b1
+			>;
+		};
+
 		pinctrl_pwm1: pwm1grp {
 			fsl,pins = <
 				MX6QDL_PAD_SD1_DAT3__PWM1_OUT 0x1b0b1
-- 
1.9.1

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

On 12/02/2014 12:09 PM, Eric Nelson wrote:
> It looks like a few patches are missing for SABRE Lite.
> 
> The following is essentially an aggregation of these patches
> for Nitrogen6x in main-line:
> 	43c3c00 - ARM: dts: nitrogen6x: add i2c2
> 	d653620 - ARM: dts: nitrogen6x: add hdmi
> 	1dffdd6 - ARM: dts: nitrogen6x: add i2c3
> 
> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>

N.B. This is **not a patch for fsl-community-bsp**.

I just sent as a patch to make it easy for Gary to apply to
his main-line kernel tree.

Regards,


Eric

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Gary Bisson]

Hi Eric,

On 12/02/2014 11:11 AM, Eric Nelson wrote:
> On 12/02/2014 12:09 PM, Eric Nelson wrote:
>> It looks like a few patches are missing for SABRE Lite.
>>
>> The following is essentially an aggregation of these patches
>> for Nitrogen6x in main-line:
>> 	43c3c00 - ARM: dts: nitrogen6x: add i2c2
>> 	d653620 - ARM: dts: nitrogen6x: add hdmi
>> 	1dffdd6 - ARM: dts: nitrogen6x: add i2c3
>>
>> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
> N.B. This is **not a patch for fsl-community-bsp**.
>
> I just sent as a patch to make it easy for Gary to apply to
> his main-line kernel tree.
>
> Regards,
>
>
> Eric

I ported those changes already during my testing. Then I've tried a 
Nitrogen board directly and got the same results.
Do you confirm HDMI is working fine on mainline?

Thanks,
Gary

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Fabio Estevam]

On Tue, Dec 2, 2014 at 5:14 PM, Gary Bisson <bisson.gary@gmail.com> wrote:

> I ported those changes already during my testing. Then I've tried a Nitrogen
> board directly and got the same results.

Can you share your full log (from U-boot to the kernel)?

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Gary Bisson]

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

Hi Fabio,

On Tue, Dec 02, 2014 at 05:17:29PM -0200, Fabio Estevam wrote:
> On Tue, Dec 2, 2014 at 5:14 PM, Gary Bisson <bisson.gary@gmail.com> wrote:
> 
> > I ported those changes already during my testing. Then I've tried a Nitrogen
> > board directly and got the same results.
> 
> Can you share your full log (from U-boot to the kernel)?

I've attached both my full log and the EDID I read once booted up. The
log shows that the fb0 modes seems not to reflect what should be
supported.
As a FYI, I've used a Nitrogen6-rev2 (SoC T1.2) for this test.

Thanks,
Gary

[-- Attachment #2: mx6_nit6x_mainline.log --]
[-- Type: text/plain, Size: 18962 bytes --]

U-Boot 2014.07 (Dec 01 2014 - 14:10:10)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Nitrogen6X
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2 MiB
auto-detected panel HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6
FEC [PRIME], usb_ether
Hit any key to stop autoboot:  1 \b\b\b 0 
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part 
No port device detected!
** Bad device size - sata 0 **

SATA device 1: unknown device
** Bad device sata 1 **
MMC: no card present
MMC: no card present
** Bad device mmc 0 **
switch to partitions #0, OK
mmc1 is current device
3207 bytes read in 34 ms (91.8 KiB/s)
## Executing script at 10008000
** File not found uEnv.txt **
Setting bus to 1
Valid chip addresses: 50
Setting bus to 2
Valid chip addresses:
------ no Freescale display
Valid chip addresses:
------ no ft5x06 touch controller
Valid chip addresses:
------ no 800x480 display
32631 bytes read in 71 ms (448.2 KiB/s)
only CEA modes allowed on HDMI port
5484216 bytes read in 373 ms (14 MiB/s)
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.18.0-rc7-00001-g4e03159-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5484152 Bytes = 5.2 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob at 0x12000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 12000000, end 1200af76

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.0-rc7-00001-g4e03159-dirty (gbisson@e6430) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #2 SMP Mon Dec 1 19:33:38 PST 2014
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Freescale i.MX6 Quad Nitrogen6x Board
[    0.000000] cma: Reserved 16 MiB at 0x4f000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 10 pages/cpu @be7a0000 s8960 r8192 d23808 u40960
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
[    0.000000] Kernel command line: enable_wait_mode=off video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p1 mxc_hdmi.only_cea=1
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1004472K/1048576K available (6855K kernel code, 406K rwdata, 2344K rodata, 360K init, 8349K bss, 44104K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xc0800000 - 0xff000000   (1000 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
[    0.000000]     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
[    0.000000]     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
[    0.000000]       .text : 0x80008000 - 0x80903f9c   (9200 kB)
[    0.000000]       .init : 0x80904000 - 0x8095e000   ( 360 kB)
[    0.000000]       .data : 0x8095e000 - 0x809c3860   ( 407 kB)
[    0.000000]        .bss : 0x809c3860 - 0x811eaed4   (8350 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c7, AUX_CTRL 0x76070001
[    0.000000] Switching to timer-based delay loop, resolution 333ns
[    0.000006] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns
[    0.000977] Console: colour dummy device 80x30
[    0.001005] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[    0.001015] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.001023] ... MAX_LOCK_DEPTH:          48
[    0.001031] ... MAX_LOCKDEP_KEYS:        8191
[    0.001038] ... CLASSHASH_SIZE:          4096
[    0.001046] ... MAX_LOCKDEP_ENTRIES:     32768
[    0.001053] ... MAX_LOCKDEP_CHAINS:      65536
[    0.001061] ... CHAINHASH_SIZE:          32768
[    0.001068]  memory used by lock dependency info: 5167 kB
[    0.001076]  per task-struct memory footprint: 1152 bytes
[    0.001102] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
[    0.001121] pid_max: default: 32768 minimum: 301
[    0.001478] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001497] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.003094] CPU: Testing write buffer coherency: ok
[    0.003833] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.003933] Setting up static identity map for 0x106b7908 - 0x106b7978
[    0.007881] CPU1: Booted secondary processor
[    0.007917] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.009445] CPU2: Booted secondary processor
[    0.009477] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.010880] CPU3: Booted secondary processor
[    0.010915] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.011091] Brought up 4 CPUs
[    0.011124] SMP: Total of 4 processors activated.
[    0.011134] CPU: All CPU(s) started in SVC mode.
[    0.012865] devtmpfs: initialized
[    0.021957] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.024163] pinctrl core: initialized pinctrl subsystem
[    0.025496] regulator-dummy: no parameters
[    0.048812] NET: Registered protocol family 16
[    0.052864] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.054980] CPU identified as i.MX6Q, silicon rev 1.2
[    0.074733] vdd1p1: 800 <--> 1375 mV at 1100 mV 
[    0.075674] vdd3p0: 2800 <--> 3150 mV at 3000 mV 
[    0.076570] vdd2p5: 2000 <--> 2750 mV at 2400 mV 
[    0.077571] vddarm: 725 <--> 1450 mV at 1150 mV 
[    0.078515] vddpu: 725 <--> 1450 mV at 1150 mV 
[    0.079481] vddsoc: 725 <--> 1450 mV at 1175 mV 
[    0.096376] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.096390] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.098848] imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
[    0.146695] mxs-dma 110000.dma-apbh: initialized
[    0.148153] 2P5V: 2500 mV 
[    0.148747] 3P3V: 3300 mV 
[    0.149438] usb_otg_vbus: 5000 mV 
[    0.151460] vgaarb: loaded
[    0.152390] SCSI subsystem initialized
[    0.153449] usbcore: registered new interface driver usbfs
[    0.153607] usbcore: registered new interface driver hub
[    0.153813] usbcore: registered new device driver usb
[    0.157914] i2c i2c-0: IMX I2C adapter registered
[    0.158525] i2c i2c-1: IMX I2C adapter registered
[    0.159127] i2c i2c-2: IMX I2C adapter registered
[    0.159318] Linux video capture interface: v2.00
[    0.159538] pps_core: LinuxPPS API ver. 1 registered
[    0.159549] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.159603] PTP clock support registered
[    0.160320] Advanced Linux Sound Architecture Driver Initialized.
[    0.164149] cfg80211: Calling CRDA to update world regulatory domain
[    0.165498] Switched to clocksource mxc_timer1
[    0.191674] NET: Registered protocol family 2
[    0.193148] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.193393] TCP bind hash table entries: 8192 (order: 6, 294912 bytes)
[    0.196223] TCP: Hash tables configured (established 8192 bind 8192)
[    0.196376] TCP: reno registered
[    0.196409] UDP hash table entries: 512 (order: 3, 40960 bytes)
[    0.196790] UDP-Lite hash table entries: 512 (order: 3, 40960 bytes)
[    0.197995] NET: Registered protocol family 1
[    0.198914] RPC: Registered named UNIX socket transport module.
[    0.198929] RPC: Registered udp transport module.
[    0.198940] RPC: Registered tcp transport module.
[    0.198951] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.200113] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.203374] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.220041] VFS: Disk quotas dquot_6.5.2
[    0.220451] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.226942] NFS: Registering the id_resolver key type
[    0.227115] Key type id_resolver registered
[    0.227131] Key type id_legacy registered
[    0.227302] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.228991] fuse init (API version 7.23)
[    0.229768] msgmni has been set to 1993
[    0.231833] io scheduler noop registered
[    0.231861] io scheduler deadline registered
[    0.231956] io scheduler cfq registered (default)
[    0.232643] imx-weim 21b8000.weim: Driver registered.
[    0.444236] imx6q-pcie 1ffc000.pcie: phy link never came up
[    0.444788] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
[    0.444810] pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
[    0.444827] pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
[    0.444845] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.446057] PCI: bus0: Fast back to back transfers disabled
[    0.446405] PCI: bus1: Fast back to back transfers enabled
[    0.446536] pci 0000:00:00.0: BAR 0: assigned [mem 0x01000000-0x010fffff]
[    0.446565] pci 0000:00:00.0: BAR 6: assigned [mem 0x01100000-0x0110ffff pref]
[    0.446584] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.447168] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    0.454830] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2
[    0.454854] imx-sdma 20ec000.sdma: firmware not found
[    0.461902] imx-sdma 20ec000.sdma: initialized
[    0.462820] Serial: IMX driver
[    0.463507] imx-uart 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58, base_baud = 5000000) is a IMX
[    0.465170] imx-uart 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59, base_baud = 5000000) is a IMX
[    1.278142] console [ttymxc1] enabled
[    1.283003] serial: Freescale lpuart driver
[    1.288071] [drm] Initialized drm 1.1.0 20060810
[    1.295772] imx-ipuv3 2400000.ipu: IPUv3H probed
[    1.302169] imx-ipuv3 2800000.ipu: IPUv3H probed
[    1.324518] brd: module loaded
[    1.337528] loop: module loaded
[    1.342280] ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024
[    1.350254] ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480
[    1.358300] ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000
[    1.366515] ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000
[    1.377301] ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled
[    1.384309] ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[    1.393146] ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst 
[    1.405115] scsi host0: ahci_platform
[    1.409980] ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71
[    1.426164] m25p80 spi0.0: sst25vf016b (2048 Kbytes)
[    1.434886] spi_imx 2008000.ecspi: probed
[    1.439833] CAN device driver interface
[    1.445405] 2188000.ethernet supply phy not found, using dummy regulator
[    1.466828] pps pps0: new PPS source ptp0
[    1.478417] libphy: fec_enet_mii_bus: probed
[    1.484284] fec 2188000.ethernet eth0: registered PHC device 0
[    1.491348] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.497926] ehci-pci: EHCI PCI platform driver
[    1.502533] ehci-mxc: Freescale On-Chip EHCI Host driver
[    1.508245] usbcore: registered new interface driver usb-storage
[    1.523382] 2184200.usb supply vbus not found, using dummy regulator
[    1.533923] ci_hdrc ci_hdrc.1: doesn't support gadget
[    1.539032] ci_hdrc ci_hdrc.1: EHCI Host Controller
[    1.544091] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[    1.565553] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[    1.574285] hub 1-0:1.0: USB hub found
[    1.578289] hub 1-0:1.0: 1 port detected
[    1.585284] mousedev: PS/2 mouse device common for all mice
[    1.594544] rtc-isl1208 0-006f: chip found, driver version 0.3
[    1.611278] rtc-isl1208 0-006f: rtc core: registered rtc-isl1208 as rtc0
[    1.618727] rtc-isl1208 0-006f: rtc power failure detected, please set clock.
[    1.627789] snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc1
[    1.636340] i2c /dev entries driver
[    1.642588] IR NEC protocol handler initialized
[    1.647176] IR RC5(x/sz) protocol handler initialized
[    1.652252] IR RC6 protocol handler initialized
[    1.656828] IR JVC protocol handler initialized
[    1.661379] IR Sony protocol handler initialized
[    1.666030] IR SANYO protocol handler initialized
[    1.670753] IR Sharp protocol handler initialized
[    1.675497] IR MCE Keyboard/mouse protocol handler initialized
[    1.681349] IR XMP protocol handler initialized
[    1.688766] imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
[    1.695280] sdhci: Secure Digital Host Controller Interface driver
[    1.701501] sdhci: Copyright(c) Pierre Ossman
[    1.705899] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.712673] sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
[    1.723196] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
[    1.755539] ata1: SATA link down (SStatus 0 SControl 300)
[    1.761004] ahci-imx 2200000.sata: no device found, disabling link.
[    1.767317] ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug
[    1.775857] mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
[    1.783755] sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
[    1.793247] sdhci-esdhc-imx 219c000.usdhc: No vqmmc regulator found
[    1.846230] mmc1: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
[    1.856841] usbcore: registered new interface driver usbhid
[    1.862429] usbhid: USB HID core driver
[    1.876701] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.885355] [drm] No driver support for vblank timestamp query.
[    1.895987] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
[    1.903661] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
[    1.911362] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops ipu_crtc_ops)
[    1.915615] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.925643] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops ipu_crtc_ops)
[    1.933678] imx-hdmi 120000.hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
[    1.941174] imx-drm display-subsystem: bound 120000.hdmi (ops hdmi_ops)
[    1.948379] imx-drm display-subsystem: bound 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)
[    1.964413] mmc1: host does not support reading read-only switch, assuming write-enable
[    1.979427] mmc1: new high speed SDHC card at address 1234
[    1.986580] mmcblk0: mmc1:1234 SA04G 3.67 GiB 
[    1.995026]  mmcblk0: p1
[    2.067918] Console: switching to colour frame buffer device 240x67
[    2.068539] hub 1-1:1.0: USB hub found
[    2.068776] hub 1-1:1.0: 3 ports detected
[    2.095400] imx-drm display-subsystem: fb0:  frame buffer device
[    2.101446] imx-drm display-subsystem: registered panic notifier
[    2.135552] [drm] Initialized imx-drm 1.0.0 20120507 on minor 0
[    2.145818] sgtl5000 0-000a: sgtl5000 revision 0x11
[    2.187055] 0-000a: 1200 mV normal 
[    2.190846] sgtl5000 0-000a: Using internal LDO instead of VDDD
[    2.212679] imx-sgtl5000 sound: sgtl5000 <-> 2028000.ssi mapping ok
[    2.226740] TCP: cubic registered
[    2.231497] NET: Registered protocol family 10
[    2.238978] sit: IPv6 over IPv4 tunneling driver
[    2.245407] NET: Registered protocol family 17
[    2.249933] can: controller area network core (rev 20120528 abi 9)
[    2.256302] NET: Registered protocol family 29
[    2.260776] can: raw protocol (rev 20120528)
[    2.265136] can: broadcast manager protocol (rev 20120528 t)
[    2.270883] can: netlink gateway (rev 20130117) max_hops=1
[    2.277007] Key type dns_resolver registered
[    2.285953] Registering SWP/SWPB emulation handler
[    2.296295] input: gpio-keys as /devices/soc0/gpio-keys/input/input0
[    2.305793] rtc-isl1208 0-006f: hctosys: invalid date/time
[    2.347290] usb_otg_vbus: disabling
[    2.351187] ALSA device list:
[    2.354184]   #0: imx6q-nitrogen6x-sgtl5000
[    2.370120] EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
[    2.381668] EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (244)
[    2.394361] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
[    2.401702] EXT4-fs (mmcblk0p1): write access will be enabled during recovery
[    5.347411] EXT4-fs (mmcblk0p1): recovery complete
[    6.053887] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[    6.062214] VFS: Mounted root (ext4 filesystem) readonly on device 179:1.
[    6.073707] devtmpfs: mounted
[    6.077670] Freeing unused kernel memory: 360K (80904000 - 8095e000)
[    6.307308] EXT4-fs (mmcblk0p1): re-mounted. Opts: data=ordered
Starting logging: OK
Populating /dev using udev: [    6.607953] udevd[90]: starting version 1.9
[    6.628613] random: udevd urandom read with 33 bits of entropy available
done
Initializing random number generator... done.
Starting network...

Welcome to Buildroot
buildroot login: root
# cat /sys/class/graphics/fb0/modescat /sys/class/graphics/fb0/modes
U:1920x1080p-0
# cat /sys/devices/soc0/display-subsystem/drm/card0/card0-HDMI-A-1/edid > edid.mx6.bin 

[-- Attachment #3: edid.mx6.bin --]
[-- Type: application/octet-stream, Size: 256 bytes --]

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

Hi Gary,

On 12/02/2014 12:52 PM, Gary Bisson wrote:
> Hi Fabio,
> 
> On Tue, Dec 02, 2014 at 05:17:29PM -0200, Fabio Estevam wrote:
>> On Tue, Dec 2, 2014 at 5:14 PM, Gary Bisson <bisson.gary@gmail.com> wrote:
>>
>>> I ported those changes already during my testing. Then I've tried a Nitrogen
>>> board directly and got the same results.
>>
>> Can you share your full log (from U-boot to the kernel)?
> 
> I've attached both my full log and the EDID I read once booted up. The
> log shows that the fb0 modes seems not to reflect what should be
> supported.
>

What tree did you pull this kernel from? I'm not finding commit 4e03159
on linux-next or torvalds/linux.git.

> As a FYI, I've used a Nitrogen6-rev2 (SoC T1.2) for this test.
> 

I should have read this before responding to your earlier message.

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Gary Bisson]

Hi Eric,

On 12/02/2014 12:11 PM, Eric Nelson wrote:
> Hi Gary,
>
> On 12/02/2014 12:52 PM, Gary Bisson wrote:
>> Hi Fabio,
>>
>> On Tue, Dec 02, 2014 at 05:17:29PM -0200, Fabio Estevam wrote:
>>> On Tue, Dec 2, 2014 at 5:14 PM, Gary Bisson <bisson.gary@gmail.com> wrote:
>>>
>>>> I ported those changes already during my testing. Then I've tried a Nitrogen
>>>> board directly and got the same results.
>>> Can you share your full log (from U-boot to the kernel)?
>> I've attached both my full log and the EDID I read once booted up. The
>> log shows that the fb0 modes seems not to reflect what should be
>> supported.
>>
> What tree did you pull this kernel from? I'm not finding commit 4e03159
> on linux-next or torvalds/linux.git.

This is the linux-stable git I use. However the 4e03159 is the SHA1 id 
of my patch for the T1.0 which is actually based on 009d0431 (linux 
3.18-rc7).
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/

>> As a FYI, I've used a Nitrogen6-rev2 (SoC T1.2) for this test.
>>
> I should have read this before responding to your earlier message.

No problem. Could you share your command line? Do you see any 
differences between your log and mine?

Also, do you plan on submitting your sabrelite patches to the lkml?

Thanks,
Gary

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

Hi Gary,

On 12/02/2014 01:16 PM, Gary Bisson wrote:
> On 12/02/2014 12:11 PM, Eric Nelson wrote:
>> On 12/02/2014 12:52 PM, Gary Bisson wrote:
>>
>> <snip>
>>
>>> I've attached both my full log and the EDID I read once booted up. The
>>> log shows that the fb0 modes seems not to reflect what should be
>>> supported.
>>>
>> What tree did you pull this kernel from? I'm not finding commit 4e03159
>> on linux-next or torvalds/linux.git.
> 
> This is the linux-stable git I use. However the 4e03159 is the SHA1 id
> of my patch for the T1.0 which is actually based on 009d0431 (linux
> 3.18-rc7).
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
> 

Cool. I'll re-test based on that.

>>> As a FYI, I've used a Nitrogen6-rev2 (SoC T1.2) for this test.
>>>
>> I should have read this before responding to your earlier message.
> 
> No problem. Could you share your command line? Do you see any
> differences between your log and mine?
> 
I don't see anything different with respect to displays, and
my "modes" entry is coming up the same as yours:

	root@trusty-dev:~# cat /sys/class/graphics/fb0/modes
	U:1920x1080p-0

My command-line also matches yours with respect to video:
	root@trusty-dev:~# cat /proc/cmdline
enable_wait_mode=off video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24,bpp=32
video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait fixrtc
root=/dev/mmcblk0p1 mxc_hdmi.only_cea=1 splash quiet
plymouth.ignore-serial-consoles

Note that the mode request (720P) isn't supported by the
kernel, and I'm getting 1080P resolution.

I'm currently booting an image that contains X acceleration, and
the Vivante drivers aren't coming up, so I'm getting a login
prompt on /dev/tty0.

What userspace are you running?

Is it possible that you're up and running, but nothing is
starting because of an X configuration problem?

> Also, do you plan on submitting your sabrelite patches to the lkml?
> 

Sure. I'd be happy to.

Regards,


Eric

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

On 12/02/2014 02:04 PM, Eric Nelson wrote:
> On 12/02/2014 01:16 PM, Gary Bisson wrote:
>>
>> Also, do you plan on submitting your sabrelite patches to the lkml?
>>
> 
> Sure. I'd be happy to.
> 

Done.

	http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/thread.html#308161

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Fabio Estevam]

On Tue, Dec 2, 2014 at 5:52 PM, Gary Bisson <bisson.gary@gmail.com> wrote:

> I've attached both my full log and the EDID I read once booted up. The
> log shows that the fb0 modes seems not to reflect what should be
> supported.
> As a FYI, I've used a Nitrogen6-rev2 (SoC T1.2) for this test.

I would recommend to remove all the 'video=' parameters from the
kernel command line, as they do not apply to mainline.

Also, there is a known issue with ldb and hdmi working at the same
time. On my sabresd I can get HDMI to work with LVDS if I disconnect
and reconnect the HDMI cable or if I remove the LVDS node from dts.

Try to change your dtsi file so that HDMI becomes the only display output.

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

Hi Gary,

On 12/02/2014 12:14 PM, Gary Bisson wrote:
> Hi Eric,
> 
> On 12/02/2014 11:11 AM, Eric Nelson wrote:
>> On 12/02/2014 12:09 PM, Eric Nelson wrote:
>>> It looks like a few patches are missing for SABRE Lite.
>>>
>>> The following is essentially an aggregation of these patches
>>> for Nitrogen6x in main-line:
>>>     43c3c00 - ARM: dts: nitrogen6x: add i2c2
>>>     d653620 - ARM: dts: nitrogen6x: add hdmi
>>>     1dffdd6 - ARM: dts: nitrogen6x: add i2c3
>>>
>>> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
>> N.B. This is **not a patch for fsl-community-bsp**.
>>
>> I just sent as a patch to make it easy for Gary to apply to
>> his main-line kernel tree.
>>
>> Regards,
>>
>>
>> Eric
> 
> I ported those changes already during my testing. Then I've tried a
> Nitrogen board directly and got the same results.
> Do you confirm HDMI is working fine on mainline?
> 

It worked fine in my testing of 3.18-rc1 on both SABRE Lite
and Nitrogen6x.

Are both of your machines TO 1.0? If so, the problem may be
similar to what you've seen on 3.10.17.

Fabio, have you tested HDMI on older silicon in recent
main-line kernels?

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Fabio Estevam]

On Tue, Dec 2, 2014 at 6:06 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:

> Fabio, have you tested HDMI on older silicon in recent
> main-line kernels?

No, I haven't, but as per Gary's description his issue also appears with TO1.2.

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

On 12/02/2014 02:16 PM, Fabio Estevam wrote:
> On Tue, Dec 2, 2014 at 6:06 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
> 
>> Fabio, have you tested HDMI on older silicon in recent
>> main-line kernels?
> 
> No, I haven't, but as per Gary's description his issue also appears with TO1.2.
> 

Thanks for the feedback Fabio.

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Gary Bisson]

Fabio, Eric,

On 12/02/2014 01:20 PM, Eric Nelson wrote:
> On 12/02/2014 02:16 PM, Fabio Estevam wrote:
>> On Tue, Dec 2, 2014 at 6:06 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>
>>> Fabio, have you tested HDMI on older silicon in recent
>>> main-line kernels?
>> No, I haven't, but as per Gary's description his issue also appears with TO1.2.
>>
> Thanks for the feedback Fabio.

Thank you both for your support. Fabio was right, by removing the ldb 
node in the device tree did the trick, HDMI is now working properly. 
I'll try to look into this issue later.

I will submit my kernel patch for T1.0 on both lkml and this mailing 
today or worst case scenario tomorrow (I have to go back to other issues 
now).

Thanks again!
Gary

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

Hi Gary,

On 12/02/2014 02:37 PM, Gary Bisson wrote:
> Fabio, Eric,
> 
> On 12/02/2014 01:20 PM, Eric Nelson wrote:
>> On 12/02/2014 02:16 PM, Fabio Estevam wrote:
>>> On Tue, Dec 2, 2014 at 6:06 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>>> Fabio, have you tested HDMI on older silicon in recent
>>>> main-line kernels?
>>> No, I haven't, but as per Gary's description his issue also appears
>>> with TO1.2.
>>>
>> Thanks for the feedback Fabio.
> 
> Thank you both for your support. Fabio was right, by removing the ldb
> node in the device tree did the trick, HDMI is now working properly.
> I'll try to look into this issue later.
> 

I'm not sure why you're both seeing this. I was able to get
proper HDMI operation without hacking the device tree.

> I will submit my kernel patch for T1.0 on both lkml and this mailing
> today or worst case scenario tomorrow (I have to go back to other issues
> now).
> 

I'm looking forward to it. There are others out there with
the older silicon, and most users want HDMI support.

Regards,


Eric

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Gary Bisson]

Hi Eric,

On 12/02/2014 02:44 PM, Eric Nelson wrote:
>> [snip]
>> Thank you both for your support. Fabio was right, by removing the ldb
>> node in the device tree did the trick, HDMI is now working properly.
>> I'll try to look into this issue later.
>>
> I'm not sure why you're both seeing this. I was able to get
> proper HDMI operation without hacking the device tree.
>

Do you have an LVDS display connected to the board in your case? My 
setup only has the HDMI is connected.

>> I will submit my kernel patch for T1.0 on both lkml and this mailing
>> today or worst case scenario tomorrow (I have to go back to other issues
>> now).
>>
> I'm looking forward to it. There are others out there with
> the older silicon, and most users want HDMI support.

Don't expect something fancy, it's just one mis-configured clock ;-)

Gary

Re: [PATCH] imx6qdl-sabrelite: DT: Add I2C2/3 and HDMI support

[Eric Nelson]

On 12/02/2014 03:54 PM, Gary Bisson wrote:
> 
> Don't expect something fancy, it's just one mis-configured clock ;-)
> 

All the better.

I'll need to find an old board to give a "Tested-By'...