On Fri, Apr 27, 2012 at 03:25:38PM -0700, Kevin Hilman wrote:
> "Mark A. Greer" writes:
>
> > On Thu, Apr 26, 2012 at 04:29:45PM -0700, Kevin Hilman wrote:
> >
> > Hi Kevin.
> >
> >> This is a rebased version of this series which is ready for broader
> >> testing. I'd especially appreciate testing from those of you with
> >> AM35x platforms.
> >>
> >> Currently, our SoC detection is based on SoC family detection
> >> (using die ID) and the presence of specific IP blocks (or feature.)
> >>
> >> This series begins the separation of the SoC family detection and
> >> specific IP detection by completely removing IP detection from the SoC
> >> family detection (cpu_is_*.)
> >>
> >> Applies on top of v3.4-rc4, boot tested on AM3517 EVM.
> >
> > Your series applied and booted without issue until the point that
> > pm_idle is called. At that point it hung because its doing a wfi
> > and not getting an interrupt to wake up back up. That's expected
> > behaviour so your patches are good (IMHO) but I need to finish and
> > submit a new version of my patches to fix that issue.
>
> For the benefit of others wanting to test this:
>
> You have to use 'nohlt' on the cmdline on AM35x in order to avoid WFI
> and the wakeup problems that are still being worked on.
>
> Kevin
> --
> 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
Hello Kevin,
I have a Logic PD AM3517 Zoom Experimenter [SOMAM3517-10-1780RJXR-C (REV A)].
My board booted to the Linux login on MMC rootfs.
The following is from 'dmesg' output:
[start]-
...
[0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/mmcblk0p2
rw nohlt rootfstype=ext3 rootwait omapdss.def_disp=dvi
omapfb.mode=dvi:1280x800@60
...
[0.107727] omap_hwmod: am35x_otg_hs: cannot be enabled (3)
[0.121704] omap_hwmod: uart4: softreset failed (waited 1 usec)
...
[0.136505] [ cut here ]
[0.136566] WARNING: at /sandbox/linux/arch/arm/mach-omap2/pm.c:48
_init_omap_device+0x74/0x94()
[0.136566] _init_omap_device: could not find omap_hwmod for iva
[0.136596] Modules linked in:
[0.136657] [] (unwind_backtrace+0x0/0x11c) from []
(warn_slowpath_common+0x4c/0x64)
[0.136718] [] (warn_slowpath_common+0x4c/0x64) from []
(warn_slowpath_fmt+0x2c/0x3c)
[0.136749] [] (warn_slowpath_fmt+0x2c/0x3c) from []
(_init_omap_device+0x74/0x94)
[0.136779] [] (_init_omap_device+0x74/0x94) from []
(omap2_common_pm_init+0x34/0x5c)
[0.136810] [] (omap2_common_pm_init+0x34/0x5c) from []
(do_one_initcall+0x90/0x164)
[0.136840] [] (do_one_initcall+0x90/0x164) from []
(kernel_init+0x120/0x1dc)
[0.136901] [] (kernel_init+0x120/0x1dc) from []
(kernel_thread_exit+0x0/0x8)
[0.137207] ---[ end trace 1b75b31a2719ed1c ]---
...
[0.184143] dpll3_m2_clk rate change failed: -22
[0.186218] usbhs_omap: alias fck already exists
[0.191223] _omap_mux_init_gpio: Multiple gpio paths (2) for gpio126
...
[0.547546] usbhs_omap usbhs_omap: xclk60mhsp1_ck set parentfailed error:-22
[0.547607] usbhs_omap usbhs_omap: xclk60mhsp2_ck set parentfailed error:-22
...
[0.858215] omapdss_venc supply vdda_dac not found, using dummy regulator
[e.863067] omapdss supply vdds_dsi not found, using dummy regulator
...
[1.864593] davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
[1.871093] davinci_mdio davinci_mdio.0: detected phy mask fffe
[1.881072] davinci_mdio.0: probed
[1.884643] davinci_mdio davinci_mdio.0: phy[0]: device davinci_mdio-0:00,
driver SMSC LAN8710/LAN8720
...
[4.477539] voltdm_scale: No voltage scale API registered for vdd_mpu_iva
[4.484832] voltdm_scale: No voltage scale API registered for vdd_core
...
[4.569549] omapfb omapfb: failed to allocate fbmem
[4.579437] omapfb omapfb: failed to setup omapfb
[4.588745] omapfb: probe of omapfb failed with error -12
[end]---
Mark Greer's patches from earlier this month helped with some of these
IVA related items. I would like to help test some of the AM3517 changes.
I have two SOMAM3517 cards (one with WiFi). Is there a kernel config
that is commonly used by those testing the AM3517? or modified
omap2plus? I think some issues that I am seeing involve wrong
configuration assumptions by me.
--
Derald D. Woods
--
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
