[Natty] [ti-omap4] [Pull-request]: TI OMAP4 2.6.38 updates
Bryan Wu
bryan.wu at canonical.com
Thu Mar 24 04:26:49 UTC 2011
On Thu, Mar 24, 2011 at 10:48 AM, Ricardo Salveti de Araujo <
ricardo.salveti at canonical.com> wrote:
> On Wed, 2011-03-23 at 20:26 +0800, Bryan Wu wrote:
> > Tim,
> >
> > I've got latest updates from Sebastien Jan, Andy Green and Ricardo,
> > Please find the branch here:
> > git://kernel.ubuntu.com/roc/ubuntu-natty.git ti-omap4
> >
> > It's based on latest 2.8.38 Linaro release and it is also contains:
> > - DSS2 HDMI/DVI driver integration, HDMI output 1920x1080p works fine
> > - Audio driver updates and fixing
> > - Enable PowerVR SGX support in kernel, Ricardo will provide user space
> > SGX related PPA later
> > - WLAN driver updates
> >
> > We test it on Panda boards, so far
> > - boot ok on HDMI output on 1280x1024 DVI screen: ok
> > - audio play / record using aplay/arecord: ok
> > - syslink and tiler unit tests: ok
> > - WLAN through UI (NetworkManager): ok
> > - USB OTG in device mode: failing, we are working on this to fix it
> soon.
> > It is ready for our ti-omap4 Natty image.
>
> Just tested and this kernel is working fine with SGX, tested with DVI
> and HDMI.
>
> Once this kernel hit the archive I'll publish the new packages at the TI
> PPA.
>
> Two issues I saw while using it is a backtrace while booting and the
> invalid alsa+pulse configuration:
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING:
> at /home/ubuntu/kernel/kernel-tilt/arch/arm/mach-omap2/omap_hwmod.c:1664
> omap_hwmod_setup_one+0x4c/0xe0()
> [ 0.000000] omap_hwmod: timer1: hwmod not yet registered
>
That's because we missing a timer1 hwmod data structure
in arch/arm/mach-omap2/omap_hwmod_44xx_data.c
But in arch/arm/mach-omap2/timer-gp.c:266, it try to setup a timer1
omap_hwmod.
We can ignore the omap_hwmod_setup_one in timer-gp.c, but I'm not sure about
that.
In arch/arm/mach-omap2/omap_hwmod_44xx_data.c:573:
--
/*
* Modules omap_hwmod structures
*
* The following IPs are excluded for the moment because:
* - They do not need an explicit SW control using omap_hwmod API.
* - They still need to be validated with the driver
* properly adapted to omap_hwmod / omap_device
*
....
* timer1
--
It looks like we don't have timer1 hwmod for timer-gp.c.
Sebastien, could you help to take a look at this? or we can post this to
upstream.
> [ 0.000000] Modules linked in:
> [ 0.000000] [<c005a440>] (unwind_backtrace+0x0/0xe0) from
> [<c0092cc0>] (warn_slowpath_common+0x4c/0x64)
> [ 0.000000] [<c0092cc0>] (warn_slowpath_common+0x4c/0x64) from
> [<c0092d58>] (warn_slowpath_fmt+0x2c/0x3c)
> [ 0.000000] [<c0092d58>] (warn_slowpath_fmt+0x2c/0x3c) from
> [<c00115b0>] (omap_hwmod_setup_one+0x4c/0xe0)
> [ 0.000000] [<c00115b0>] (omap_hwmod_setup_one+0x4c/0xe0) from
> [<c001098c>] (omap2_gp_clockevent_init+0x38/0x1ac)
> [ 0.000000] [<c001098c>] (omap2_gp_clockevent_init+0x38/0x1ac) from
> [<c0010b48>] (omap2_gp_timer_init+0x48/0x5c)
> [ 0.000000] [<c0010b48>] (omap2_gp_timer_init+0x48/0x5c) from
> [<c000c208>] (time_init+0x20/0x30)
> [ 0.000000] [<c000c208>] (time_init+0x20/0x30) from [<c0008aa4>]
> (start_kernel+0x1ec/0x364)
> [ 0.000000] [<c0008aa4>] (start_kernel+0x1ec/0x364) from [<8000803c>]
> (0x8000803c)
> [ 0.000000] ---[ end trace da227214a82491b7 ]---
>
> [ 286.581970] asoc: no valid backend routes for PCM: SDP4430 Media
> [ 286.590057] asoc: no valid backend routes for PCM: SDP4430 Media
> [ 286.597656] asoc: no valid backend routes for PCM: SDP4430 Media
> [ 286.605102] asoc: no valid backend routes for PCM: SDP4430 Media
>
>
Should we setup some config files in user space?
Tim, I've just rebased our ti-omap4 to master 2.6.38-7.38 release. Please
pull from here:
git://kernel.ubuntu.com/roc/ubuntu-natty.git ti-omap4
Thanks,
--
Bryan Wu <bryan.wu at canonical.com>
Kernel Developer +86.138-1617-6545 Mobile
Ubuntu Kernel Team
Canonical Ltd. www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20110324/425d6572/attachment.html>
More information about the kernel-team
mailing list