AnsweredAssumed Answered

Issue in Display bringup in imx6 sololite

Question asked by Shrimanth Ramesh on Jun 9, 2015

We are porting 3.10 kernel for our custom board based on imx6sl.
In imx6sl.dtsi file, It is shown that driver is compatible with "fsl,imx28-lcdif", so we are enabling it to bringup the display.
when we enable "MXS LCD framebuffer support" to bringup the display, the kernel stops in between(Please see the below log)

Memory: 447MB 64MB = 511MB total
Memory: 243392k/243392k available, 280896k reserved, 0K highmem
Virtual kernel memory layout:
  vector : 0xffff0000 - 0xffff1000 ( 4 kB)
  fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
  vmalloc : 0xa0800000 - 0xff000000 (1512 MB)
  lowmem : 0x80000000 - 0xa0000000 ( 512 MB)
  pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
  modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
  .text : 0x80008000 - 0x809fa4b0 (10186 kB)
  .init : 0x809fb000 - 0x80a57600 ( 370 kB)
  .data : 0x80a58000 - 0x80a80ca0 ( 164 kB)
  .bss : 0x80affc44 - 0x80b8f9d0 ( 576 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
NR_IRQS:16 nr_irqs:16 16
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32030000, Cache size: 262144 B


But when we disable the "Support for frame buffer devices" option in device drivers --> graphics, we are able to successfully boot the system.(without display)

We are using following:
bootargs:
setenv bootargs console=ttymxc2,115200 init=/init androidboot.console=ttymxc2 consoleblank=0 androidboot.hardware=freescale

dts:
imx6sl-evk-ldo.dts

Please let us know what we are missing. Thanks in advance

Outcomes