RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, Mar 18, 2011 at 11:13 AM, Anand Gadiyar gadi...@ti.com wrote: i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand Sorry for the spam - my mailer went berserk. I offlined it for now while I figure out what's going on. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi, On Wed, 2011-03-16 at 18:49 -0500, Stephan Raue wrote: i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ Have the HDMI on your setup worked in any (prebuilt) image? What I'm asking is if you are sure the HDMI HW works on your board? Powering off quietly sounds strange. Is your power supply sufficient? Well, I don't think that would explain the first crash you posted... Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Raue, -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi Sent: Thursday, March 17, 2011 4:41 PM To: Stephan Raue Cc: K, Mythri P; linux-omap@vger.kernel.org Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 Hi, On Wed, 2011-03-16 at 18:49 -0500, Stephan Raue wrote: i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ Is it possible for you to enable low-level debugging and pass omapfb.debug=1 omapdss.debug=1 in your bootargs? This would show the Framebuffer and DSSDBG prints. We would get an idea if kernel is getting stuck in DSS/OMAPFB. Let me know if you any help in enabling debug prints. Also one more suggestion/ question, are you seeing a hang if DSS is not enabled in kernel? -Thanks, Mayuresh Have the HDMI on your setup worked in any (prebuilt) image? What I'm asking is if you are sure the HDMI HW works on your board? Powering off quietly sounds strange. Is your power supply sufficient? Well, I don't think that would explain the first crash you posted... Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 17.03.2011 17:20, schrieb Janorkar, Mayuresh: Raue, -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi Sent: Thursday, March 17, 2011 4:41 PM To: Stephan Raue Cc: K, Mythri P; linux-omap@vger.kernel.org Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 Hi, On Wed, 2011-03-16 at 18:49 -0500, Stephan Raue wrote: i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ Is it possible for you to enable low-level debugging and pass omapfb.debug=1 omapdss.debug=1 in your bootargs? This would show the Framebuffer and DSSDBG prints. We would get an idea if kernel is getting stuck in DSS/OMAPFB. Let me know if you any help in enabling debug prints. Also one more suggestion/ question, are you seeing a hang if DSS is not enabled in kernel? -Thanks, Mayuresh i have done, there is not more output with enable low level debugging and passing this options... :-( disabling DSS lets boot the kernel and start initramfs (see: http://paste.pocoo.org/show/355262/) Have the HDMI on your setup worked in any (prebuilt) image? What I'm asking is if you are sure the HDMI HW works on your board? yes, prebuild ubuntu images based on TI's 2.6.35 kernel with hdmi support gives me output on my monitor. Powering off quietly sounds strange. Is your power supply sufficient? Well, I don't think that would explain the first crash you posted... i have seen the board dont poweroff, i have also added LED support so the LED's begins to flash after kernel start. but only for a very short time until the kernel crashes. so i was thinking it does a power off, but the chips on the board are not cold even after some minutes/hours, so the board is powered on. The powersupply is the recommended powersupply from digikey, so its ok. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 17.03.2011 21:16, schrieb Stephan Raue: Am 17.03.2011 17:20, schrieb Janorkar, Mayuresh: ... Is it possible for you to enable low-level debugging and pass omapfb.debug=1 omapdss.debug=1 in your bootargs? This would show the Framebuffer and DSSDBG prints. We would get an idea if kernel is getting stuck in DSS/OMAPFB. Let me know if you any help in enabling debug prints. Also one more suggestion/ question, are you seeing a hang if DSS is not enabled in kernel? -Thanks, Mayuresh i have done, there is not more output with enable low level debugging and passing this options... :-( disabling DSS lets boot the kernel and start initramfs (see: http://paste.pocoo.org/show/355262/) an update: compiled with DSS/HDMI support as modules, loading modules with: modprobe omapdss modprobe omapfb and doing a dmesg in the init script gives me: modprobe: can't load module omapdss (kernel/drivers/video/omap2/dss/omapdss.ko): invalid module format modprobe: can't load module cfbcopyarea (kernel/drivers/video/cfbcopyarea.ko): invalid module format see: http://paste.pocoo.org/show/355300/ line 254,255,514,515 why? the complete kernel with modules is rebuild from scratch thanks much Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 17.03.2011 22:13, schrieb Stephan Raue: Am 17.03.2011 21:16, schrieb Stephan Raue: an update: compiled with DSS/HDMI support as modules, loading modules with: modprobe omapdss modprobe omapfb and doing a dmesg in the init script gives me: modprobe: can't load module omapdss (kernel/drivers/video/omap2/dss/omapdss.ko): invalid module format modprobe: can't load module cfbcopyarea (kernel/drivers/video/cfbcopyarea.ko): invalid module format see: http://paste.pocoo.org/show/355300/ line 254,255,514,515 why? the complete kernel with modules is rebuild from scratch next update: disable: CONFIG_LOCALVERSION_AUTO CONFIG_MODULE_FORCE_LOAD CONFIG_MODULE_FORCE_UNLOAD CONFIG_MODVERSIONS CONFIG_MODULE_SRCVERSION_ALL gives: [3.934814] Bad mode in data abort handler detected [3.939941] Internal error: Oops - bad mode: 0 [#1] SMP [3.945404] last sysfs file: /sys/devices/virtual/graphics/fbcon/cursor_blink [3.952911] Modules linked in: omapdss(+) [3.957122] CPU: 0Not tainted (2.6.38 #1) [3.961791] PC is at 0x0018 [3.965179] LR is at omap_dsshw_probe+0x1d4/0x358 [omapdss] [3.971008] pc : [0018]lr : [bf000d14]psr: 6092 [3.971038] sp : ef149d08 ip : c0e2bcd8 fp : [3.983093] r10: 0028 r9 : c0ef4338 r8 : [3.988555] r7 : bf012904 r6 : r5 : ef947c40 r4 : [3.995422] r3 : f08fc000 r2 : 02102006 r1 : ef149cf0 r0 : [4.002288] Flags: nZCv IRQs off FIQs on Mode IRQ_32 ISA ARM Segment user [4.009857] Control: 10c53c7d Table: af3b404a DAC: 0015 [4.015899] Process modprobe (pid: 559, stack limit = 0xef1482f8) [4.022308] Stack: (0xef149d08 to 0xef14a000) [4.026885] 9d00: ef149cf0 02102006 f08fc000 ef947c40 [4.035461] 9d20: bf012904 c0ef4338 0028 c0e2bcd8 ef149d08 [4.044067] 9d40: bf000d14 0018 6092 bf013050 ef947c40 bf000d14 [4.052642] 9d60: ef954008 ef95403c bf012904 c067b8b4 c067b8a0 c067aacc ef954008 [4.061248] 9d80: ef95403c bf012904 c067abf0 bf012904 ef149da0 c067ab88 c0679d38 [4.069824] 9da0: ef84f658 ef949730 bf012904 bf012904 ef1e7a60 c09cac08 c067a3d0 [4.078430] 9dc0: bf00e65b 0468 bf012904 c09b4d90 c09b0b28 bf012848 [4.087005] 9de0: 0028 c067ae44 bf013034 c09b4d90 c09b0b28 bf012848 [4.095611] 9e00: 0028 bf00053c c09b4d90 efa72690 c0aa1380 c09b4d98 c09b4dcc bf012848 [4.104217] 9e20: bf012848 0028 c067b8b4 c067b8a0 c067aacc c09b4d98 [4.112792] 9e40: c09b4dcc bf012848 c067abf0 bf012848 ef149e60 c067ab88 c0679d38 [4.121398] 9e60: ef84f658 ef9491b0 bf012848 bf012848 ef1e7c60 c09cac08 c067a3d0 [4.129974] 9e80: bf00e09e 0468 bf012848 ef27f9a0 bf01d000 [4.138580] 9ea0: 0028 c067ae44 c067b8d8 ef27f9a0 bf01d000 [4.147155] 9ec0: 0028 bf01d064 bf012ed4 c0431694 0001 bf012ed4 bf012ed4 [4.155761] 9ee0: 0001 bf012ed4 ef27f9a0 bf012f1c 0001 0028 c04af9e4 [4.164337] 9f00: bf012ee0 000aa048 0003 c04ad17c c0ef4330 c07f45bc bf013018 000aa048 [4.172943] 9f20: f08d9000 000201b0 f08ec450 f08ec2dc f08f11a8 ef385800 00014740 [4.181518] 9f40: 000186a0 0023 0024 0019 000f [4.190124] 9f60: bf011a34 0016 0080 [4.198699] 9f80: 6010 400368e0 0080 c043b5c8 ef148000 [4.207305] 9fa0: 0003 c043b400 400368e0 4020e000 000201b0 000aa048 0003 [4.215881] 9fc0: 400368e0 0080 000aa048 0003 [4.224487] 9fe0: bee1a880 bee1a870 00036138 401ab0a0 6010 4020e000 [4.233093] [bf000d14] (omap_dsshw_probe+0x1d4/0x358 [omapdss]) from [f08fc000] (0xf08fc000) [4.242340] Code: e59ff410 eabb ea9a eafa (ea78) [4.248748] [ cut here ] [4.253601] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:98 l3_interrupt_handler+0xb8/0x134() [4.262664] L3 standard error: SOURCE:DSS at address 0x10 [4.268402] Modules linked in: omapdss(+) [4.272644] [c044239c] (unwind_backtrace+0x0/0xe4) from [c047457c] (warn_slowpath_common+0x4c/0x64) [4.282531] [c047457c] (warn_slowpath_common+0x4c/0x64) from [c0474614] (warn_slowpath_fmt+0x2c/0x3c) [4.292572] [c0474614] (warn_slowpath_fmt+0x2c/0x3c) from [c0455898] (l3_interrupt_handler+0xb8/0x134) [4.302734] [c0455898] (l3_interrupt_handler+0xb8/0x134) from [c04b46f8] (handle_IRQ_event+0x6c/0x15c) [4.312896] [c04b46f8] (handle_IRQ_event+0x6c/0x15c) from [c04b6344] (handle_level_irq+0xdc/0x160) [4.322692] [c04b6344]
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Thu, 2011-03-17 at 16:13 -0500, Stephan Raue wrote: compiled with DSS/HDMI support as modules, loading modules with: modprobe omapdss modprobe omapfb and doing a dmesg in the init script gives me: modprobe: can't load module omapdss (kernel/drivers/video/omap2/dss/omapdss.ko): invalid module format modprobe: can't load module cfbcopyarea (kernel/drivers/video/cfbcopyarea.ko): invalid module format see: http://paste.pocoo.org/show/355300/ line 254,255,514,515 why? the complete kernel with modules is rebuild from scratch I don't see how that could be a problem in DSS. I mostly use DSS as modules, so it works ok. Are you sure DSS compiled fine, and those modules are right for the kernel you run? Can you load any other module compiled at that time? Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Just a hunch, but could you please turn off CONFIG_OMAP2_DSS_SDI and try again? - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Mon, 2011-03-14 at 04:35 -0500, Hiremath, Vaibhav wrote: -Original Message- From: Valkeinen, Tomi Sent: Monday, March 14, 2011 2:55 PM To: Hiremath, Vaibhav Cc: K, Mythri P; Stephan Raue; linux-omap@vger.kernel.org Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 snip Personally I don't know any platform is implementing this function OR how one should make use of it. I remember last time we had similar discussion and the comment came was, restore only required in case of off mode. I feel, this is not applicable here, since irrespective of retention/inactive/off mode if driver is disabling clock for the peripheral we must restore the context. I don't know about OMAP4, but on OMAP3 the register contents are only lost when DSS goes to OFF mode. If you just turn off the clocks and OFF mode is not enabled in the PM, context restore is not needed. I am not sure of the current status of OFF mode in the mainline kernel. However, for some reason DSS works fine on my Overo board. I would imagine that it would break also if OFF is enabled for all omap boards... As for get_last_off_on_transaction_id(), it seems to be called get_context_loss_count() in the mainline kernel and returns u32, not int. I haven't tested it, but get_last_off_on_transaction_id pointer in the dss platform data should be set to get_context_loss_count in the board file (or in arch/arm/plat-omap/display.c if using the dss2 tree). [Hiremath, Vaibhav] Let me try this out. Did you have time to test this? Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message- From: Valkeinen, Tomi Sent: Wednesday, March 16, 2011 12:15 PM To: Hiremath, Vaibhav Cc: K, Mythri P; Stephan Raue; linux-omap@vger.kernel.org Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 On Mon, 2011-03-14 at 04:35 -0500, Hiremath, Vaibhav wrote: -Original Message- From: Valkeinen, Tomi Sent: Monday, March 14, 2011 2:55 PM To: Hiremath, Vaibhav Cc: K, Mythri P; Stephan Raue; linux-omap@vger.kernel.org Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 snip Personally I don't know any platform is implementing this function OR how one should make use of it. I remember last time we had similar discussion and the comment came was, restore only required in case of off mode. I feel, this is not applicable here, since irrespective of retention/inactive/off mode if driver is disabling clock for the peripheral we must restore the context. I don't know about OMAP4, but on OMAP3 the register contents are only lost when DSS goes to OFF mode. If you just turn off the clocks and OFF mode is not enabled in the PM, context restore is not needed. I am not sure of the current status of OFF mode in the mainline kernel. However, for some reason DSS works fine on my Overo board. I would imagine that it would break also if OFF is enabled for all omap boards... As for get_last_off_on_transaction_id(), it seems to be called get_context_loss_count() in the mainline kernel and returns u32, not int. I haven't tested it, but get_last_off_on_transaction_id pointer in the dss platform data should be set to get_context_loss_count in the board file (or in arch/arm/plat-omap/display.c if using the dss2 tree). [Hiremath, Vaibhav] Let me try this out. Did you have time to test this? [Hiremath, Vaibhav] Yesterday got pulled into different issue, will try today. Thanks, Vaibhav Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Sun, 2011-03-13 at 11:20 -0500, Stephan Raue wrote: Am 13.03.2011 15:32, schrieb Stephan Raue: snip i have tried this omap2plus defconfig now too, with some little changes needed to boot my system (config: http://paste.pocoo.org/show/352917/). Now i get this error (see also: http://paste.pocoo.org/show/352915/) [3.255065] omapdss HDMI: fallback to VGA [3.271636] omapdss HDMI error: Failed to set PHY_PWR_STATUS [3.277587] omapdss HDMI error: failed to power on device [3.283325] omapdss error: failed to power on [3.287902] omapfb omapfb: Failed to enable display 'hdmi' [3.293853] Console: switching to colour dummy device 80x30 [3.304595] omapfb omapfb: failed to setup omapfb [3.309539] omapfb: probe of omapfb failed with error -5 using omap2plus defconfig with my little changes i need to boot my system i get the error above, also if i remove CONFIG_ARCH_OMAP2. but if i remove CONFIG_ARCH_OMAP3 too i get the error i reported originally (the kernel begins to boot, but crashes) (diff between omap2plus defconfig without CONFIG_ARCH_OMAP2 and omap2plus defconfig without CONFIG_ARCH_OMAP2, CONFIG_ARCH_OMAP3: http://paste.pocoo.org/show/352960/) I'm currently traveling for this week so I have quite limited ability to test this. Mythri still haven't been able to reproduce any of these errors, right? Anybody else there to test HDMI on Panda and/or Blaze? I pushed the latest DSS + HDMI patches to a test branch for easier testing (I'll push Panda DVI patches there also when I get the new version): git://gitorious.org/linux-omap-dss2/linux.git test Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 02:24 -0600, K, Mythri P wrote: Hi Tomi, On Thu, Mar 10, 2011 at 8:36 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: There is this code in dss.c: #ifdef CONFIG_OMAP2_DSS_VENC REG_FLD_MOD(DSS_CONTROL, 1, 4, 4); /* venc dac demen */ REG_FLD_MOD(DSS_CONTROL, 1, 3, 3); /* venc clock 4x enable */ REG_FLD_MOD(DSS_CONTROL, 0, 2, 2); /* venc clock mode = normal */ #endif Regarding this piece of code , although it appears that is should not affect , I think we should move this out of dss_init , if any such change is needed we should do that on VENC enable dont you think ? Either we should enable them on venc_enable, or remove the ifdef. If there are side effects (which we don't know currently) we should use do them on venc_enable. If there aren't any side effects, we should just write the register always. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Tomi, On Wed, Mar 16, 2011 at 12:21 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: On Sun, 2011-03-13 at 11:20 -0500, Stephan Raue wrote: Am 13.03.2011 15:32, schrieb Stephan Raue: snip i have tried this omap2plus defconfig now too, with some little changes needed to boot my system (config: http://paste.pocoo.org/show/352917/). Now i get this error (see also: http://paste.pocoo.org/show/352915/) [ 3.255065] omapdss HDMI: fallback to VGA [ 3.271636] omapdss HDMI error: Failed to set PHY_PWR_STATUS [ 3.277587] omapdss HDMI error: failed to power on device [ 3.283325] omapdss error: failed to power on [ 3.287902] omapfb omapfb: Failed to enable display 'hdmi' [ 3.293853] Console: switching to colour dummy device 80x30 [ 3.304595] omapfb omapfb: failed to setup omapfb [ 3.309539] omapfb: probe of omapfb failed with error -5 using omap2plus defconfig with my little changes i need to boot my system i get the error above, also if i remove CONFIG_ARCH_OMAP2. but if i remove CONFIG_ARCH_OMAP3 too i get the error i reported originally (the kernel begins to boot, but crashes) (diff between omap2plus defconfig without CONFIG_ARCH_OMAP2 and omap2plus defconfig without CONFIG_ARCH_OMAP2, CONFIG_ARCH_OMAP3: http://paste.pocoo.org/show/352960/) I'm currently traveling for this week so I have quite limited ability to test this. Mythri still haven't been able to reproduce any of these errors, right? That's right i have not been able to reproduce the error. I have tried with 4 Panda Boards with atleast 4 - 5 Montiors connected ( Also without connecting any monitor). Anybody else there to test HDMI on Panda and/or Blaze? I pushed the latest DSS + HDMI patches to a test branch for easier testing (I'll push Panda DVI patches there also when I get the new version): git://gitorious.org/linux-omap-dss2/linux.git test Stephan, It would be great if you could try out with this tree with omap2plus_defconfig. Note : Please disable VENC , there is a known issue of kernel crash with VENC enabled. Thanks and regards, Mythri. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 16.03.2011 11:53, schrieb K, Mythri P: Hi Tomi, On Wed, Mar 16, 2011 at 12:21 PM, Tomi Valkeinentomi.valkei...@ti.com wrote: On Sun, 2011-03-13 at 11:20 -0500, Stephan Raue wrote: Am 13.03.2011 15:32, schrieb Stephan Raue: snip i have tried this omap2plus defconfig now too, with some little changes needed to boot my system (config: http://paste.pocoo.org/show/352917/). Now i get this error (see also: http://paste.pocoo.org/show/352915/) [3.255065] omapdss HDMI: fallback to VGA [3.271636] omapdss HDMI error: Failed to set PHY_PWR_STATUS [3.277587] omapdss HDMI error: failed to power on device [3.283325] omapdss error: failed to power on [3.287902] omapfb omapfb: Failed to enable display 'hdmi' [3.293853] Console: switching to colour dummy device 80x30 [3.304595] omapfb omapfb: failed to setup omapfb [3.309539] omapfb: probe of omapfb failed with error -5 using omap2plus defconfig with my little changes i need to boot my system i get the error above, also if i remove CONFIG_ARCH_OMAP2. but if i remove CONFIG_ARCH_OMAP3 too i get the error i reported originally (the kernel begins to boot, but crashes) (diff between omap2plus defconfig without CONFIG_ARCH_OMAP2 and omap2plus defconfig without CONFIG_ARCH_OMAP2, CONFIG_ARCH_OMAP3: http://paste.pocoo.org/show/352960/) I'm currently traveling for this week so I have quite limited ability to test this. Mythri still haven't been able to reproduce any of these errors, right? That's right i have not been able to reproduce the error. I have tried with 4 Panda Boards with atleast 4 - 5 Montiors connected ( Also without connecting any monitor). Anybody else there to test HDMI on Panda and/or Blaze? I pushed the latest DSS + HDMI patches to a test branch for easier testing (I'll push Panda DVI patches there also when I get the new version): git://gitorious.org/linux-omap-dss2/linux.git test Stephan, It would be great if you could try out with this tree with omap2plus_defconfig. Note : Please disable VENC , there is a known issue of kernel crash with VENC enabled. Thanks and regards, Mythri. Hi, i tried this test tree with omap2plus_defconfig. it seems the kernel crashes and poweroff the board on loading this hdmi stuff, but dont print any crashlog. is there a way any backtraces will be printed? output from serial console: http://paste.pocoo.org/show/354850/ kernel config (omap2plus_defconfig, added squashfs support, added support to include initramfs in kernel, build omapfb stuff statically into the kernel): http://paste.pocoo.org/show/354853/ i am using a own toolchain to crosscompile with gcc-4.5.2, binutils-2.21... Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Hiremath, Vaibhav
Sent: Friday, March 11, 2011 6:53 PM
To: Valkeinen, Tomi; K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi
Sent: Friday, March 11, 2011 12:55 PM
To: K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 00:16 -0600, K, Mythri P wrote:
Hi Stephan,
On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue
mailingli...@openelec.tv
wrote:
thanks, this helps to boot the kernel. but now i get:
snip
see also: http://paste.pocoo.org/show/351648/
I see that you kernel is not booting because of dss clk
[3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4
[3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc
Tomi is this related to the clock issue you were mentioning , which
gets solved by adding a delay ?
Well, I have a hack patch in my tree which adds a delay of 10us. That
fixed the problem for me, but the 10us is just a random guess. It could
be that it needs to be longer wait. But this could be something else
also.
Tomi
[Hiremath, Vaibhav] Tomi, just thought of updating you,
The linux-omap/dss2 OMAP3EVM seems to be broken, I am trying to debug this
at the moment and will update about my findings.
Since linux-omap/master is booting up fine, it looks like one of new DSS
patch leading to this.
[Hiremath, Vaibhav] I think I found the where and why the kernel is crashing
but not sure about root-cause -
The root-cause turned out to be -
void dss_clk_enable(enum dss_clock clks)
{
...
if (check_ctx cpu_is_omap34xx() dss_need_ctx_restore())
restore_all_ctx();
...
}
In this case, restore never happens, if I understand correctly, I am expecting,
the context must be restored when all clock (especially interface clock) is
disabled.
In order to do this, dss_need_ctx_restore must be implemented here, which I
think should be ORed with other conditions.
if (cpu_is_omap34xx() (check_ctx || dss_need_ctx_restore()))
(This results in kernel crash at my end)
Personally I don't know any platform is implementing this function OR how one
should make use of it. I remember last time we had similar discussion and the
comment came was, restore only required in case of off mode. I feel, this is
not applicable here, since irrespective of retention/inactive/off mode if
driver is disabling clock for the peripheral we must restore the context.
Thanks,
Vaibhav
Thanks,
Vaibhav
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Mon, 2011-03-14 at 03:35 -0500, Hiremath, Vaibhav wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Hiremath, Vaibhav
Sent: Friday, March 11, 2011 6:53 PM
To: Valkeinen, Tomi; K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi
Sent: Friday, March 11, 2011 12:55 PM
To: K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 00:16 -0600, K, Mythri P wrote:
Hi Stephan,
On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue
mailingli...@openelec.tv
wrote:
thanks, this helps to boot the kernel. but now i get:
snip
see also: http://paste.pocoo.org/show/351648/
I see that you kernel is not booting because of dss clk
[3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4
[3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc
Tomi is this related to the clock issue you were mentioning , which
gets solved by adding a delay ?
Well, I have a hack patch in my tree which adds a delay of 10us. That
fixed the problem for me, but the 10us is just a random guess. It could
be that it needs to be longer wait. But this could be something else
also.
Tomi
[Hiremath, Vaibhav] Tomi, just thought of updating you,
The linux-omap/dss2 OMAP3EVM seems to be broken, I am trying to debug this
at the moment and will update about my findings.
Since linux-omap/master is booting up fine, it looks like one of new DSS
patch leading to this.
[Hiremath, Vaibhav] I think I found the where and why the kernel is crashing
but not sure about root-cause -
The root-cause turned out to be -
void dss_clk_enable(enum dss_clock clks)
{
...
if (check_ctx cpu_is_omap34xx() dss_need_ctx_restore())
restore_all_ctx();
...
}
In this case, restore never happens, if I understand correctly, I am
expecting, the context must be restored when all clock (especially interface
clock) is disabled.
In order to do this, dss_need_ctx_restore must be implemented here, which I
think should be ORed with other conditions.
if (cpu_is_omap34xx() (check_ctx || dss_need_ctx_restore()))
(This results in kernel crash at my end)
Personally I don't know any platform is implementing this function OR how one
should make use of it. I remember last time we had similar discussion and the
comment came was, restore only required in case of off mode. I feel, this is
not applicable here, since irrespective of retention/inactive/off mode if
driver is disabling clock for the peripheral we must restore the context.
I don't know about OMAP4, but on OMAP3 the register contents are only
lost when DSS goes to OFF mode. If you just turn off the clocks and OFF
mode is not enabled in the PM, context restore is not needed. I am not
sure of the current status of OFF mode in the mainline kernel.
However, for some reason DSS works fine on my Overo board. I would
imagine that it would break also if OFF is enabled for all omap
boards...
As for get_last_off_on_transaction_id(), it seems to be called
get_context_loss_count() in the mainline kernel and returns u32, not
int. I haven't tested it, but get_last_off_on_transaction_id pointer in
the dss platform data should be set to get_context_loss_count in the
board file (or in arch/arm/plat-omap/display.c if using the dss2 tree).
Tomi
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message-
From: Valkeinen, Tomi
Sent: Monday, March 14, 2011 2:55 PM
To: Hiremath, Vaibhav
Cc: K, Mythri P; Stephan Raue; linux-omap@vger.kernel.org
Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Mon, 2011-03-14 at 03:35 -0500, Hiremath, Vaibhav wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Hiremath, Vaibhav
Sent: Friday, March 11, 2011 6:53 PM
To: Valkeinen, Tomi; K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi
Sent: Friday, March 11, 2011 12:55 PM
To: K, Mythri P
Cc: Stephan Raue; linux-omap@vger.kernel.org
Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 00:16 -0600, K, Mythri P wrote:
Hi Stephan,
On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue
mailingli...@openelec.tv
wrote:
thanks, this helps to boot the kernel. but now i get:
snip
see also: http://paste.pocoo.org/show/351648/
I see that you kernel is not booting because of dss clk
[3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4
[3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc
Tomi is this related to the clock issue you were mentioning ,
which
gets solved by adding a delay ?
Well, I have a hack patch in my tree which adds a delay of 10us.
That
fixed the problem for me, but the 10us is just a random guess. It
could
be that it needs to be longer wait. But this could be something else
also.
Tomi
[Hiremath, Vaibhav] Tomi, just thought of updating you,
The linux-omap/dss2 OMAP3EVM seems to be broken, I am trying to debug
this
at the moment and will update about my findings.
Since linux-omap/master is booting up fine, it looks like one of new
DSS
patch leading to this.
[Hiremath, Vaibhav] I think I found the where and why the kernel is
crashing but not sure about root-cause -
The root-cause turned out to be -
void dss_clk_enable(enum dss_clock clks)
{
...
if (check_ctx cpu_is_omap34xx() dss_need_ctx_restore())
restore_all_ctx();
...
}
In this case, restore never happens, if I understand correctly, I am
expecting, the context must be restored when all clock (especially
interface clock) is disabled.
In order to do this, dss_need_ctx_restore must be implemented here,
which I think should be ORed with other conditions.
if (cpu_is_omap34xx() (check_ctx || dss_need_ctx_restore()))
(This results in kernel crash at my end)
Personally I don't know any platform is implementing this function OR
how one should make use of it. I remember last time we had similar
discussion and the comment came was, restore only required in case of off
mode. I feel, this is not applicable here, since irrespective of
retention/inactive/off mode if driver is disabling clock for the
peripheral we must restore the context.
I don't know about OMAP4, but on OMAP3 the register contents are only
lost when DSS goes to OFF mode. If you just turn off the clocks and OFF
mode is not enabled in the PM, context restore is not needed. I am not
sure of the current status of OFF mode in the mainline kernel.
However, for some reason DSS works fine on my Overo board. I would
imagine that it would break also if OFF is enabled for all omap
boards...
As for get_last_off_on_transaction_id(), it seems to be called
get_context_loss_count() in the mainline kernel and returns u32, not
int. I haven't tested it, but get_last_off_on_transaction_id pointer in
the dss platform data should be set to get_context_loss_count in the
board file (or in arch/arm/plat-omap/display.c if using the dss2 tree).
[Hiremath, Vaibhav] Let me try this out.
Thanks,
Vaibhav
Tomi
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Tomi, On Thu, Mar 10, 2011 at 2:44 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: I think this version is good. It works for me, at least =). Any Panda or Blaze owners reading this want to give this a try? Tested on my pandaboard, with these patches applied on top of your dss2 tree: I get a working display on my DVI or my HDMI screen. = I tested by running the Ubuntu UI. I have a couple of these traces from times to times (seems linked to screen saver enabling/disabling the screen): omapdss DISPC error: timeout waiting for EVSYNC The best screen resolution is properly selected on both of my screens, but the frame-buffer is sized to 640x480. So the display works but the usable surface when going though /dev/fb0 is quite reduced. Is there a way to get the FB sized according to the screen resolution (in the init sequence, it appears that the FBs are allocated before the init of the HDMI)? Fyi, I have also tested with the patches for DVI support and can get both outputs working simultaneously (my tree is here: http://dev.omapzoom.org/?p=sebjan/kernel.git;a=shortlog;h=refs/tags/topic-display-iv1-2.6.38-rc7). -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Mon, 2011-03-14 at 05:37 -0500, Jan, Sebastien wrote: Hi Tomi, On Thu, Mar 10, 2011 at 2:44 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: I think this version is good. It works for me, at least =). Any Panda or Blaze owners reading this want to give this a try? Tested on my pandaboard, with these patches applied on top of your dss2 tree: I get a working display on my DVI or my HDMI screen. = I tested by running the Ubuntu UI. I have a couple of these traces from times to times (seems linked to screen saver enabling/disabling the screen): omapdss DISPC error: timeout waiting for EVSYNC Yes, I get those every time I enable or disable the HDMI output. That shouldn't cause any problems, but it's something that needs to be fixed at some point. The best screen resolution is properly selected on both of my screens, but the frame-buffer is sized to 640x480. So the display works but the usable surface when going though /dev/fb0 is quite reduced. Is there a way to get the FB sized according to the screen resolution (in the init sequence, it appears that the FBs are allocated before the init of the HDMI)? Currently the resolution has to be configured by the user manually. I haven't tried, but I think giving the resolution with boot parameters should also work. Mythri, have you tried that? I don't think it is possible for the omapdss, panel or omapfb drivers to configure the resolution automatically, except at boot time. After we have booted up, there may be users for the framebuffer and changing it secretly would cause problems. I think the best way here is that the HDMI/omapdss driver gives hotplug event, which is conveyed through omapfb to an userspace application. This application can then query the available resolutions via some mechanism, and select one of those. Fyi, I have also tested with the patches for DVI support and can get both outputs working simultaneously (my tree is here: http://dev.omapzoom.org/?p=sebjan/kernel.git;a=shortlog;h=refs/tags/topic-display-iv1-2.6.38-rc7). Thanks. I'll also set up a test branch in DSS2 tree shortly, to which I'll add DVI and HDMI patches for easier testing. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Tomi,Sebastien, On Tue, Mar 15, 2011 at 9:36 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote: On Mon, 2011-03-14 at 05:37 -0500, Jan, Sebastien wrote: Hi Tomi, On Thu, Mar 10, 2011 at 2:44 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: I think this version is good. It works for me, at least =). Any Panda or Blaze owners reading this want to give this a try? Tested on my pandaboard, with these patches applied on top of your dss2 tree: I get a working display on my DVI or my HDMI screen. = I tested by running the Ubuntu UI. I have a couple of these traces from times to times (seems linked to screen saver enabling/disabling the screen): omapdss DISPC error: timeout waiting for EVSYNC Yes, I get those every time I enable or disable the HDMI output. That shouldn't cause any problems, but it's something that needs to be fixed at some point. The best screen resolution is properly selected on both of my screens, but the frame-buffer is sized to 640x480. So the display works but the usable surface when going though /dev/fb0 is quite reduced. Is there a way to get the FB sized according to the screen resolution (in the init sequence, it appears that the FBs are allocated before the init of the HDMI)? Currently the resolution has to be configured by the user manually. I haven't tried, but I think giving the resolution with boot parameters should also work. Mythri, have you tried that? You could configure the timings later on with the sysfs ( set_timings ) or HDMI driver would pick the best timing (as suggested by standard) , but yes framebuffer would have picked the timing on probe so it will not update. I don't think it is possible for the omapdss, panel or omapfb drivers to configure the resolution automatically, except at boot time. After we have booted up, there may be users for the framebuffer and changing it secretly would cause problems. I think the best way here is that the HDMI/omapdss driver gives hotplug event, which is conveyed through omapfb to an userspace application. This application can then query the available resolutions via some mechanism, and select one of those. Fyi, I have also tested with the patches for DVI support and can get both outputs working simultaneously (my tree is here: http://dev.omapzoom.org/?p=sebjan/kernel.git;a=shortlog;h=refs/tags/topic-display-iv1-2.6.38-rc7). Thanks. I'll also set up a test branch in DSS2 tree shortly, to which I'll add DVI and HDMI patches for easier testing. Tomi Thanks and regards, Mythri. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 12.03.2011 07:51, schrieb K, Mythri P: Hi, On Sat, Mar 12, 2011 at 12:12 AM, Stephan Rauemailingli...@openelec.tv wrote: Am 11.03.2011 19:27, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 10:18 -0600, Stephan Raue wrote: Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Ok. I need to dig out my panda and try to get it running. Blaze board seems to work fine, at least for me. Does the crash happen every time? Tomi omap2plus_defconfig yes, with all configs i tried. will try a make omap2plus_defconfig too and let you know. I have tried booting on Panda board and it works fine , I am using OMAP2PLUS defconfig. I have disabled VENC though( without that i see that kernel hangs , ie because reading VENC register in hwmod probe is resulting in a crash. i have tried this omap2plus defconfig now too, with some little changes needed to boot my system (config: http://paste.pocoo.org/show/352917/). Now i get this error (see also: http://paste.pocoo.org/show/352915/) [3.255065] omapdss HDMI: fallback to VGA [3.271636] omapdss HDMI error: Failed to set PHY_PWR_STATUS [3.277587] omapdss HDMI error: failed to power on device [3.283325] omapdss error: failed to power on [3.287902] omapfb omapfb: Failed to enable display 'hdmi' [3.293853] Console: switching to colour dummy device 80x30 [3.304595] omapfb omapfb: failed to setup omapfb [3.309539] omapfb: probe of omapfb failed with error -5 thanks Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 13.03.2011 15:32, schrieb Stephan Raue: Am 12.03.2011 07:51, schrieb K, Mythri P: Hi, On Sat, Mar 12, 2011 at 12:12 AM, Stephan Rauemailingli...@openelec.tv wrote: Am 11.03.2011 19:27, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 10:18 -0600, Stephan Raue wrote: Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Ok. I need to dig out my panda and try to get it running. Blaze board seems to work fine, at least for me. Does the crash happen every time? Tomi omap2plus_defconfig yes, with all configs i tried. will try a make omap2plus_defconfig too and let you know. I have tried booting on Panda board and it works fine , I am using OMAP2PLUS defconfig. I have disabled VENC though( without that i see that kernel hangs , ie because reading VENC register in hwmod probe is resulting in a crash. i have tried this omap2plus defconfig now too, with some little changes needed to boot my system (config: http://paste.pocoo.org/show/352917/). Now i get this error (see also: http://paste.pocoo.org/show/352915/) [3.255065] omapdss HDMI: fallback to VGA [3.271636] omapdss HDMI error: Failed to set PHY_PWR_STATUS [3.277587] omapdss HDMI error: failed to power on device [3.283325] omapdss error: failed to power on [3.287902] omapfb omapfb: Failed to enable display 'hdmi' [3.293853] Console: switching to colour dummy device 80x30 [3.304595] omapfb omapfb: failed to setup omapfb [3.309539] omapfb: probe of omapfb failed with error -5 using omap2plus defconfig with my little changes i need to boot my system i get the error above, also if i remove CONFIG_ARCH_OMAP2. but if i remove CONFIG_ARCH_OMAP3 too i get the error i reported originally (the kernel begins to boot, but crashes) (diff between omap2plus defconfig without CONFIG_ARCH_OMAP2 and omap2plus defconfig without CONFIG_ARCH_OMAP2, CONFIG_ARCH_OMAP3: http://paste.pocoo.org/show/352960/) thanks Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Valkeinen, Tomi Sent: Friday, March 11, 2011 12:55 PM To: K, Mythri P Cc: Stephan Raue; linux-omap@vger.kernel.org Subject: Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4 On Fri, 2011-03-11 at 00:16 -0600, K, Mythri P wrote: Hi Stephan, On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue mailingli...@openelec.tv wrote: thanks, this helps to boot the kernel. but now i get: snip see also: http://paste.pocoo.org/show/351648/ I see that you kernel is not booting because of dss clk [3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4 [3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc Tomi is this related to the clock issue you were mentioning , which gets solved by adding a delay ? Well, I have a hack patch in my tree which adds a delay of 10us. That fixed the problem for me, but the 10us is just a random guess. It could be that it needs to be longer wait. But this could be something else also. Tomi [Hiremath, Vaibhav] Tomi, just thought of updating you, The linux-omap/dss2 OMAP3EVM seems to be broken, I am trying to debug this at the moment and will update about my findings. Since linux-omap/master is booting up fine, it looks like one of new DSS patch leading to this. Thanks, Vaibhav -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 10:18 -0600, Stephan Raue wrote: Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Ok. I need to dig out my panda and try to get it running. Blaze board seems to work fine, at least for me. Does the crash happen every time? Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Am 11.03.2011 19:27, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 10:18 -0600, Stephan Raue wrote: Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Ok. I need to dig out my panda and try to get it running. Blaze board seems to work fine, at least for me. Does the crash happen every time? Tomi omap2plus_defconfig yes, with all configs i tried. will try a make omap2plus_defconfig too and let you know. thanks much Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi, On Sat, Mar 12, 2011 at 12:12 AM, Stephan Raue mailingli...@openelec.tv wrote: Am 11.03.2011 19:27, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 10:18 -0600, Stephan Raue wrote: Am 11.03.2011 14:22, schrieb Tomi Valkeinen: On Fri, 2011-03-11 at 02:43 -0600, Stephan Raue wrote: Am 11.03.2011 08:12, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi please enable swap support or try: http://ftp.arm.linux.org.uk/git/?p=linux-2.6-arm.git;a=commit;h=97594b0f35c0708cb9551c070b9693a52ec24ebf which is fixed in 2.6.38-rc8 Ok. So you didn't have just my master branch and the HDMI patch set? I see that the config you gave is for rc8, and mine is rc7, so I guess you also merged rc8 into your tree? Tomi yes, you are right, i have tested this with different kernel configs and both rc7 and rc8 with the same results. Ok. I need to dig out my panda and try to get it running. Blaze board seems to work fine, at least for me. Does the crash happen every time? Tomi omap2plus_defconfig yes, with all configs i tried. will try a make omap2plus_defconfig too and let you know. I have tried booting on Panda board and it works fine , I am using OMAP2PLUS defconfig. I have disabled VENC though( without that i see that kernel hangs , ie because reading VENC register in hwmod probe is resulting in a crash. thanks much Stephan Vaibhav, You see a crash even without this patch set right ? so should we take that in a different thread? Thanks and regards, Mythri. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Thu, 2011-03-10 at 04:44 -0600, K, Mythri P wrote: Adding HDMI support on OMAP4. HDMI is a driver that is similar to the VENC or the DSI driver to support HDMI/DVI sink device. The current design adheres to the DSS2 architecture. It is split into the HDMI DSS driver and HDMI panel driver. I think this version is good. It works for me, at least =). Any Panda or Blaze owners reading this want to give this a try? There are a couple of cosmetic fixes you could still do, I'll email about those separately. But they are just about comments/descriptions, you can fix them and email me a tarball for the patches, no need to spam the mailing list. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Stephan Am 10.03.2011 14:44, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 04:44 -0600, K, Mythri P wrote: Adding HDMI support on OMAP4. HDMI is a driver that is similar to the VENC or the DSI driver to support HDMI/DVI sink device. The current design adheres to the DSS2 architecture. It is split into the HDMI DSS driver and HDMI panel driver. I think this version is good. It works for me, at least =). Any Panda or Blaze owners reading this want to give this a try? There are a couple of cosmetic fixes you could still do, I'll email about those separately. But they are just about comments/descriptions, you can fix them and email me a tarball for the patches, no need to spam the mailing list. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Mythri, On Thu, 2011-03-10 at 04:44 -0600, K, Mythri P wrote: Adding HDMI support on OMAP4. HDMI is a driver that is similar to the VENC or the DSI driver to support HDMI/DVI sink device. The current design adheres to the DSS2 architecture. I was testing this on Blaze, with VENC enabled in Kconfig and a small hack in venc.c which skips registering the venc device on omap4. I haven't seen these earlier, so it may just be I've been lucky, or enabling VENC affected this. I've seen this twice when loading the modules: [ 23.007690] omapdss HDMI: no valid timing found , falling back to VGA [ 23.040161] omapdss HDMI error: PLL GO bit not set [ 23.045196] omapdss HDMI error: failed to power on device [ 23.050964] omapdss error: failed to power on [ 23.055572] omapfb omapfb: Failed to enable display 'hdmi' [ 23.066162] omapfb omapfb: failed to setup omapfb [ 23.071166] omapfb: probe of omapfb failed with error -5 And I've seen this once when unloading modules: [ 126.473419] omapdss DISPC error: SYNC_LOST_DIGIT, disabling TV [ 126.569244] omapdss DISPC error: timeout waiting for EVSYNC [ 126.670776] omapdss DISPC error: timeout waiting for EVSYNC [ 126.773376] omapdss HDMI: no valid timing found , falling back to VGA [ 126.881896] omapdss DISPC error: timeout waiting for EVSYNC [ 126.983367] omapdss DISPC error: timeout waiting for EVSYNC rmmod: can't unload 'omapdss': Resource temporarily unavailable This looks a bit bad, as it sounds to me that when an error happened, some code path returned too early and the omapdss driver could not unload. There is this code in dss.c: #ifdef CONFIG_OMAP2_DSS_VENC REG_FLD_MOD(DSS_CONTROL, 1, 4, 4); /* venc dac demen */ REG_FLD_MOD(DSS_CONTROL, 1, 3, 3); /* venc clock 4x enable */ REG_FLD_MOD(DSS_CONTROL, 0, 2, 2); /* venc clock mode = normal */ #endif They don't sound like they would affect HDMI, but that was the only difference I found (between VENC enabled and disabled) with a quick search. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Tomi, Am 10.03.2011 15:51, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Ah, I guess you hit one yet unsolved problem on on omap4: VENC register access fails. Can you try switching this off: CONFIG_OMAP2_DSS_VENC. I need to make some quick hack to get VENC disabled on OMAP4 until we find the solution for this. Tomi thanks, this helps to boot the kernel. but now i get: [3.281127] Power Management for TI OMAP4. [3.291870] mmc0: host does not support reading read-only switch. assuming write-enable. [3.312957] clock: disabling unused clocks to save power [3.318695] mmc0: new high speed SDHC card at address 0001 [3.325622] mmcblk0: mmc0:0001 0 7.46 GiB [3.333618] mmcblk0: p1 p2 [3.335540] Unhandled fault: imprecise external abort (0x1406) at 0xffed6a6a [3.335571] Internal error: : 1406 [#1] PREEMPT SMP [3.335571] last sysfs file: [3.335571] Modules linked in: [3.335571] CPU: 0Not tainted (2.6.38-rc8 #1) [3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4 [3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc [3.335632] pc : [c066b4f8]lr : [c066c65c]psr: 2093 [3.335632] sp : ef845e20 ip : c0e6ffd0 fp : c09fbb90 [3.335632] r10: c0f774ac r9 : 0088 r8 : c0673644 [3.335662] r7 : 0004000e r6 : a093 r5 : r4 : [3.335662] r3 : f08c4000 r2 : f08c4000 r1 : 0006964a r0 : 0003 [3.335662] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel [3.335693] Control: 10c5387d Table: 8000404a DAC: 0015 [3.335693] Process swapper (pid: 1, stack limit = 0xef8442f8) [3.335693] Stack: (0xef845e20 to 0xef846000) [3.335693] 5e20: 1887 c0f78588 c0f78588 0044 0001 eed70b40 c06735d8 [3.335723] 5e40: c0f785f4 f0a0 c0f785b4 6013 0080 ef814000 c09fd630 [3.335723] 5e60: ef814698 ef814264 eeeae6e0 0003 eeeae400 c067a528 c082f738 [3.335723] 5e80: eeeae6e0 c09fd628 ef814694 eee26fc0 ef845ed8 c0537e70 0001 bf60 [3.335754] 5ea0: f0a0 02800280 01e0 0080 0280 [3.335754] 5ec0: 00ff01e0 c0538780 ef848000 c0830e38 ef804ac4 0003 ef8ad4c0 [3.335784] 5ee0: c09fd664 c09fd630 c09fd664 c0a0f540 c0a0f540 c09e776c [3.335784] 5f00: c06bc470 c06bc45c c06bb670 c09fd630 c09fd664 c0a0f540 [3.335784] 5f20: c06bb794 c0a0f540 ef845f38 c06bb72c c06ba8c4 ef804a5c ef8ae054 [3.335815] 5f40: c0a0f540 c0a0f540 eee24680 c0a19328 c06baf78 c092c550 0480 [3.335815] 5f60: ef845f50 c0a0f540 c002d640 c09e7680 c001edd8 c09e776c c06bb9dc [3.335815] 5f80: c002d624 c002d640 c09e7680 c001edd8 c09e776c c001edfc [3.335845] 5fa0: ef844000 c041e644 c0933524 0198 c0a01b8c c09e7680 c09e7770 c002d624 [3.335845] 5fc0: c002d640 c09e7680 c09e7770 0002 c09e776c c0008b2c 0004 [3.335876] 5fe0: c00089d4 c0423f1c 0013 c0423f1c faffd73f 00100e0a [3.335876] [c066b4f8] (dss_clk_disable_no_ctx+0x0/0xa4) from [c0f78588] (num_managers+0x0/0x4) [3.335906] Code: e8bd8070 c0f77254 c0954a8a 000218de (e92d4038) [3.335906] ---[ end trace b7597bb719140d9a ]--- [3.335906] note: swapper[1] exited with preempt_count 2 [3.335937] Kernel panic - not syncing: Attempted to kill init! [3.588439] CPU1: stopping [3.591308] [c0428bec] (unwind_backtrace+0x0/0xe4) from [c041e2d8] (do_IPI+0xe4/0x15c) [3.600036] [c041e2d8] (do_IPI+0xe4/0x15c) from [c08314cc] (__irq_svc+0x4c/0xcc) [3.608184] Exception stack(0xef861b60 to 0xef861ba8) [3.613494] 1b60: c04582a0 ef861ba8 ef861b98 ef86 0282 0002 ef861c00 [3.622100] 1b80: 0001 ef86 0001 000a 005b820e ef861ba8 c04582a0 c04582a4 [3.630706] 1ba0: 6113 [3.634399] [c08314cc] (__irq_svc+0x4c/0xcc) from [c04582a4] (__do_softirq+0x6c/0x250) [3.643096] [c04582a4] (__do_softirq+0x6c/0x250) from [c0458988] (irq_exit+0x58/0xb0) [3.651733] [c0458988] (irq_exit+0x58/0xb0) from [c041e29c] (do_IPI+0xa8/0x15c) [3.659790] [c041e29c] (do_IPI+0xa8/0x15c) from [c08314cc] (__irq_svc+0x4c/0xcc) [3.667938] Exception stack(0xef861c00 to 0xef861c48) [3.673248] 1c00: 0001 0001 ef84a800 0025 0001 c09fe67c c0a32340 [3.681854] 1c20: c6b2f9f3 0001 0001 0036 6113 ef861c48
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
Hi Stephan, On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue mailingli...@openelec.tv wrote: Hi Tomi, Am 10.03.2011 15:51, schrieb Tomi Valkeinen: On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Ah, I guess you hit one yet unsolved problem on on omap4: VENC register access fails. Can you try switching this off: CONFIG_OMAP2_DSS_VENC. I need to make some quick hack to get VENC disabled on OMAP4 until we find the solution for this. Tomi thanks, this helps to boot the kernel. but now i get: snip see also: http://paste.pocoo.org/show/351648/ I see that you kernel is not booting because of dss clk [3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4 [3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc Tomi is this related to the clock issue you were mentioning , which gets solved by adding a delay ? Thanks and regards, Mythri. if i remove this patchserie again it boots, see here: http://paste.pocoo.org/show/351650/ thanks Stephan -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Thu, 2011-03-10 at 08:45 -0600, Stephan Raue wrote: Hi, if i try this patch series the boot stops after (seeing via serial console): Starting kernel ... Uncompressing Linux... done, booting the kernel. without this patch series i can see the boot to th OS. I am using this patches on top of http://gitorious.org/linux-omap-dss2/linux/commits/master Do i anything wrong or do i use a wrong git repo (the patches apply cleanly)? Her my kernel config: http://fpaste.org/9Esw/ Hmm, I cannot even compile the kernel with that config: CC arch/arm/mach-omap2/io.o In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_flush_mmu': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:104:3: error: implicit declaration of function 'release_pages' In file included from arch/arm/mm/init.c:27:0: /home/tomba/work/linux/arch/arm/include/asm/tlb.h: In function 'tlb_remove_page': /home/tomba/work/linux/arch/arm/include/asm/tlb.h:168:3: error: implicit declaration of function 'page_cache_release' make[1]: *** [arch/arm/mm/init.o] Error 1 make: *** [arch/arm/mm] Error 2 make: *** Waiting for unfinished jobs Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 00/10] OMAP4 : DSS2 : HDMI support on OMAP4
On Fri, 2011-03-11 at 00:16 -0600, K, Mythri P wrote: Hi Stephan, On Fri, Mar 11, 2011 at 5:37 AM, Stephan Raue mailingli...@openelec.tv wrote: thanks, this helps to boot the kernel. but now i get: snip see also: http://paste.pocoo.org/show/351648/ I see that you kernel is not booting because of dss clk [3.335601] PC is at dss_clk_disable_no_ctx+0x0/0xa4 [3.335632] LR is at omap_dispc_register_isr+0xa4/0xcc Tomi is this related to the clock issue you were mentioning , which gets solved by adding a delay ? Well, I have a hack patch in my tree which adds a delay of 10us. That fixed the problem for me, but the 10us is just a random guess. It could be that it needs to be longer wait. But this could be something else also. Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
