From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [PATCH] ARM: OMAP5: DSS hwmod data Date: Tue, 18 Mar 2014 10:37:22 +0200 Message-ID: <532805C2.9060803@ti.com> References: <1394619996-3525-1-git-send-email-tomi.valkeinen@ti.com> <532037E0.1080309@ti.com> <53258DDA.50005@compulab.co.il> <532692A7.7000509@ti.com> <5326F71C.1060602@compulab.co.il> <5326F893.3080607@ti.com> <53270510.1030301@compulab.co.il> <5327D9BE.80503@ti.com> <532801A7.6060702@compulab.co.il> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bCAv2krdDclJcsOKP4fNGeJaPE1B6vSn7" Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:49690 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754233AbaCRIhv (ORCPT ); Tue, 18 Mar 2014 04:37:51 -0400 In-Reply-To: <532801A7.6060702@compulab.co.il> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Dmitry Lifshitz Cc: Tony Lindgren , Paul Walmsley , =?ISO-8859-1?Q?Beno=EEt_Cousson?= , Archit Taneja , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org --bCAv2krdDclJcsOKP4fNGeJaPE1B6vSn7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 18/03/14 10:19, Dmitry Lifshitz wrote: > Hi Tomi, >=20 > Thank you a lot for your assistance. >=20 > Here are my relevant DT nodes: >=20 > / { > aliases { > display0 =3D &hdmi0; > }; >=20 > hdmi0: connector@0 { > compatible =3D "hdmi-connector"; > label =3D "hdmi"; >=20 > type =3D "b"; >=20 > hdmi_connector_in: endpoint { > remote-endpoint =3D <&hdmi_out>; > }; > }; > }; >=20 > &dss { > status =3D "ok"; > }; >=20 > &hdmi { > status =3D "ok"; > vdda-supply =3D <&ldo4_reg>; >=20 > pinctrl-names =3D "default"; > pinctrl-0 =3D <&dss_hdmi_pins>; >=20 > hdmi_out: endpoint { > remote-endpoint =3D <&hdmi_connector_in>; > }; > }; The above looks fine. > I have the following kernel crash (caused by missing .detect callback):= Yes, it seems the hdmi driver is missing detect, as there's no support in there for the detection at the moment. You can add the function to omap5.c, and return true always. How does the HPD work on your board? On uevm, the ESD/Level shifter chip handles HPD, which is the only supported way at the moment. > While using FBDEV I have the following issue: >=20 > root@cm-debian:~# modprobe omapfb > [ 27.524419] ------------[ cut here ]------------ > [ 27.529256] WARNING: CPU: 1 PID: 2087 at > /home/lifshitz/workroot/OMAP5-eewiki/omap5-kernel/mm/page_alloc.c:2492 > __alloc_pages_nodemask+0x268/0x83c() > [ 27.543164] Modules linked in: omapfb(+) cfbcopyarea cfbimgblt > cfbfillrect bnep rfcomm bluetooth 6lowpan_iphc phy_omap_usb2 > connector_hdmi omapdss omap4_keypad matrix_keymap omap_ocp2scp > rtc_palmas spi_omap2_mcspi > [ 27.563113] CPU: 1 PID: 2087 Comm: modprobe Tainted: G W =20 > 3.14.0-rc4-cm-t54-test-suit+ #108 > [ 27.572677] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > [ 27.580786] [] (show_stack) from [] > (dump_stack+0x70/0x88) > [ 27.588341] [] (dump_stack) from [] > (warn_slowpath_common+0x70/0x88) > [ 27.596815] [] (warn_slowpath_common) from [] > (warn_slowpath_null+0x1c/0x24) > [ 27.606004] [] (warn_slowpath_null) from [] > (__alloc_pages_nodemask+0x268/0x83c) > [ 27.615562] [] (__alloc_pages_nodemask) from [] > (__dma_alloc_buffer.isra.16+0x2c/0xdc) > [ 27.625661] [] (__dma_alloc_buffer.isra.16) from > [] (__alloc_remap_buffer.isra.19+0x18/0xcc) > [ 27.636300] [] (__alloc_remap_buffer.isra.19) from > [] (__dma_alloc+0x110/0x138) > [ 27.645757] [] (__dma_alloc) from [] > (arm_dma_alloc+0xb0/0xd8) > [ 27.653686] [] (arm_dma_alloc) from [] > (omapfb_alloc_fbmem.isra.24+0xc8/0x158 [omapfb]) > [ 27.663911] [] (omapfb_alloc_fbmem.isra.24 [omapfb]) from > [] (omapfb_alloc_fbmem_display.isra.25+0xec/0xfc [omapfb]) > [ 27.676759] [] (omapfb_alloc_fbmem_display.isra.25 > [omapfb]) from [] (omapfb_allocate_all_fbs+0xf4/0x174 [omapfb= ]) > [ 27.689419] [] (omapfb_allocate_all_fbs [omapfb]) from > [] (omapfb_create_framebuffers+0x1fc/0x524 [omapfb]) > [ 27.701432] [] (omapfb_create_framebuffers [omapfb]) from > [] (omapfb_probe+0x28c/0x41c [omapfb]) > [ 27.712446] [] (omapfb_probe [omapfb]) from [] > (platform_drv_probe+0x18/0x48) > [ 27.721728] [] (platform_drv_probe) from [] > (really_probe+0x80/0x208) > [ 27.730284] [] (really_probe) from [] > (driver_probe_device+0x30/0x48) > [ 27.738834] [] (driver_probe_device) from [] > (__driver_attach+0x8c/0x90) > [ 27.747661] [] (__driver_attach) from [] > (bus_for_each_dev+0x54/0x88) > [ 27.756220] [] (bus_for_each_dev) from [] > (bus_add_driver+0xe4/0x1d8) > [ 27.764778] [] (bus_add_driver) from [] > (driver_register+0x78/0xf4) > [ 27.773148] [] (driver_register) from [] > (do_one_initcall+0x44/0x174) > [ 27.781703] [] (do_one_initcall) from [] > (do_init_module+0x48/0x17c) > [ 27.790172] [] (do_init_module) from [] > (SyS_init_module+0x64/0x6c) > [ 27.798546] [] (SyS_init_module) from [] > (ret_fast_syscall+0x0/0x30) > [ 27.807015] ---[ end trace 842d286115ab739d ]--- > [ 27.811849] omapfb omapfb: failed to allocate framebuffer > [ 27.817490] omapfb omapfb: failed to allocate fbmem > [ 27.822746] omapfb omapfb: failed to setup omapfb > [ 27.827710] omapfb: probe of omapfb failed with error -12 Hmm, do you have CMA enabled? Maybe something like: CONFIG_DMA_CMA=3Dy CONFIG_CMA_SIZE_MBYTES=3D32 CONFIG_CMA_SIZE_SEL_MBYTES=3Dy And if you have omap5-uevm, you could first try that one to see if you get the branch working. Tomi --bCAv2krdDclJcsOKP4fNGeJaPE1B6vSn7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTKAXCAAoJEPo9qoy8lh71RjIQAJ27gxBiYMYVAlcLbHKYebNJ ULABu3zTo6mDpHv0GLzrNazOF1Q0+X46towTEZ8ZMT2++2Zum7cUiZA8JMi8Y/ae nQfpA2k3yISARYiF9Rv2pCPIGVpVxAmvrDPpcoCM2+Y0u1CNPzNpQXwv8iwL5u3c 9TEtsN1n52n4dAYKLzCxYbV+u9m1pC/K+CpsjiSi1C5nQe114UrmP1ip9aGtlb/D plP216snkfT8JEMwWMKa99iBrpZ5+0omeajJ0WrmUDF9kIwdNdOn55z5D7q+V0nw JcawshsK/0I9n5zSepPbX/vmrQQZdP4FM938iqlv5iMwaa6mpFOH06ejvLSTzap2 OsUAL5D281+hKm7RMhfrdxdqhUdLDNwOz8NUYmpF8VklZVks5uJh+DG+D0Tj23dl RDGxUnKlZpop8NHwU9xiTH+0Gp7+DA917bsJlLmRI3T8XD4505Ee2qEg4NTD0maH JFgcI5SFL+dNIYaajC38JF7zPBGpoT7tdacYDH4+juHdWco2Thb1AvBM9FtmM1bI kUXxS5nRJ8sbHQhgoNgsOPPQRRfenncTqc6zpAsgdDyWLxjxw+7zj0aixHrKJ8Ki OtEiuNVmbOvSy2ygncMzOf/2cf5OD7hLHYtygKeiazjw0jplYCvLxincgqBWUrYS M0RzGxbkbbtrPbpoy77x =h9l1 -----END PGP SIGNATURE----- --bCAv2krdDclJcsOKP4fNGeJaPE1B6vSn7-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: tomi.valkeinen@ti.com (Tomi Valkeinen) Date: Tue, 18 Mar 2014 10:37:22 +0200 Subject: [PATCH] ARM: OMAP5: DSS hwmod data In-Reply-To: <532801A7.6060702@compulab.co.il> References: <1394619996-3525-1-git-send-email-tomi.valkeinen@ti.com> <532037E0.1080309@ti.com> <53258DDA.50005@compulab.co.il> <532692A7.7000509@ti.com> <5326F71C.1060602@compulab.co.il> <5326F893.3080607@ti.com> <53270510.1030301@compulab.co.il> <5327D9BE.80503@ti.com> <532801A7.6060702@compulab.co.il> Message-ID: <532805C2.9060803@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 18/03/14 10:19, Dmitry Lifshitz wrote: > Hi Tomi, > > Thank you a lot for your assistance. > > Here are my relevant DT nodes: > > / { > aliases { > display0 = &hdmi0; > }; > > hdmi0: connector at 0 { > compatible = "hdmi-connector"; > label = "hdmi"; > > type = "b"; > > hdmi_connector_in: endpoint { > remote-endpoint = <&hdmi_out>; > }; > }; > }; > > &dss { > status = "ok"; > }; > > &hdmi { > status = "ok"; > vdda-supply = <&ldo4_reg>; > > pinctrl-names = "default"; > pinctrl-0 = <&dss_hdmi_pins>; > > hdmi_out: endpoint { > remote-endpoint = <&hdmi_connector_in>; > }; > }; The above looks fine. > I have the following kernel crash (caused by missing .detect callback): Yes, it seems the hdmi driver is missing detect, as there's no support in there for the detection at the moment. You can add the function to omap5.c, and return true always. How does the HPD work on your board? On uevm, the ESD/Level shifter chip handles HPD, which is the only supported way at the moment. > While using FBDEV I have the following issue: > > root at cm-debian:~# modprobe omapfb > [ 27.524419] ------------[ cut here ]------------ > [ 27.529256] WARNING: CPU: 1 PID: 2087 at > /home/lifshitz/workroot/OMAP5-eewiki/omap5-kernel/mm/page_alloc.c:2492 > __alloc_pages_nodemask+0x268/0x83c() > [ 27.543164] Modules linked in: omapfb(+) cfbcopyarea cfbimgblt > cfbfillrect bnep rfcomm bluetooth 6lowpan_iphc phy_omap_usb2 > connector_hdmi omapdss omap4_keypad matrix_keymap omap_ocp2scp > rtc_palmas spi_omap2_mcspi > [ 27.563113] CPU: 1 PID: 2087 Comm: modprobe Tainted: G W > 3.14.0-rc4-cm-t54-test-suit+ #108 > [ 27.572677] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > [ 27.580786] [] (show_stack) from [] > (dump_stack+0x70/0x88) > [ 27.588341] [] (dump_stack) from [] > (warn_slowpath_common+0x70/0x88) > [ 27.596815] [] (warn_slowpath_common) from [] > (warn_slowpath_null+0x1c/0x24) > [ 27.606004] [] (warn_slowpath_null) from [] > (__alloc_pages_nodemask+0x268/0x83c) > [ 27.615562] [] (__alloc_pages_nodemask) from [] > (__dma_alloc_buffer.isra.16+0x2c/0xdc) > [ 27.625661] [] (__dma_alloc_buffer.isra.16) from > [] (__alloc_remap_buffer.isra.19+0x18/0xcc) > [ 27.636300] [] (__alloc_remap_buffer.isra.19) from > [] (__dma_alloc+0x110/0x138) > [ 27.645757] [] (__dma_alloc) from [] > (arm_dma_alloc+0xb0/0xd8) > [ 27.653686] [] (arm_dma_alloc) from [] > (omapfb_alloc_fbmem.isra.24+0xc8/0x158 [omapfb]) > [ 27.663911] [] (omapfb_alloc_fbmem.isra.24 [omapfb]) from > [] (omapfb_alloc_fbmem_display.isra.25+0xec/0xfc [omapfb]) > [ 27.676759] [] (omapfb_alloc_fbmem_display.isra.25 > [omapfb]) from [] (omapfb_allocate_all_fbs+0xf4/0x174 [omapfb]) > [ 27.689419] [] (omapfb_allocate_all_fbs [omapfb]) from > [] (omapfb_create_framebuffers+0x1fc/0x524 [omapfb]) > [ 27.701432] [] (omapfb_create_framebuffers [omapfb]) from > [] (omapfb_probe+0x28c/0x41c [omapfb]) > [ 27.712446] [] (omapfb_probe [omapfb]) from [] > (platform_drv_probe+0x18/0x48) > [ 27.721728] [] (platform_drv_probe) from [] > (really_probe+0x80/0x208) > [ 27.730284] [] (really_probe) from [] > (driver_probe_device+0x30/0x48) > [ 27.738834] [] (driver_probe_device) from [] > (__driver_attach+0x8c/0x90) > [ 27.747661] [] (__driver_attach) from [] > (bus_for_each_dev+0x54/0x88) > [ 27.756220] [] (bus_for_each_dev) from [] > (bus_add_driver+0xe4/0x1d8) > [ 27.764778] [] (bus_add_driver) from [] > (driver_register+0x78/0xf4) > [ 27.773148] [] (driver_register) from [] > (do_one_initcall+0x44/0x174) > [ 27.781703] [] (do_one_initcall) from [] > (do_init_module+0x48/0x17c) > [ 27.790172] [] (do_init_module) from [] > (SyS_init_module+0x64/0x6c) > [ 27.798546] [] (SyS_init_module) from [] > (ret_fast_syscall+0x0/0x30) > [ 27.807015] ---[ end trace 842d286115ab739d ]--- > [ 27.811849] omapfb omapfb: failed to allocate framebuffer > [ 27.817490] omapfb omapfb: failed to allocate fbmem > [ 27.822746] omapfb omapfb: failed to setup omapfb > [ 27.827710] omapfb: probe of omapfb failed with error -12 Hmm, do you have CMA enabled? Maybe something like: CONFIG_DMA_CMA=y CONFIG_CMA_SIZE_MBYTES=32 CONFIG_CMA_SIZE_SEL_MBYTES=y And if you have omap5-uevm, you could first try that one to see if you get the branch working. Tomi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: