Audio Driver (with bounty!)


hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
It should boot into the first run wizard where it asks you to set up a username/password and some other things.
As part of that it disables the root login.
If you've not completed the first-run-wizard, there is only a user:root password:root account.
Hm. There was no wizzard. Just boot log on the screen and console and now a login: on both.
And the message
Code:
[FAILED] Failed to start Pyra First Run Wizard.
See 'systemctl status pyra-first-run.service' for details.
         Starting Light Display Manager...
Doing as suggested:
Code:
root@pyra:~# systemctl status pyra-first-run.service
● pyra-first-run.service - Pyra First Run Wizard
   Loaded: loaded (/lib/systemd/system/pyra-first-run.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-02-14 11:12:21 CET; 6min ago
     Docs: https://www.pyra-handheld.com/wiki/index.php?title=Main_Page
  Process: 1974 ExecStart=/usr/bin/xinit /usr/share/pyra/scripts/pyra-first-run.sh (code=exited, status=1/FAILURE)
 Main PID: 1974 (code=exited, status=1/FAILURE)

Feb 14 11:12:18 pyra xinit[1974]: Please consult the The X.Org Foundation support
Feb 14 11:12:18 pyra xinit[1974]:          at http://wiki.x.org
Feb 14 11:12:18 pyra xinit[1974]:  for help.
Feb 14 11:12:18 pyra xinit[1974]: (EE)
Feb 14 11:12:21 pyra xinit[1974]: /usr/bin/xinit: giving up
Feb 14 11:12:21 pyra xinit[1974]: /usr/bin/xinit: unable to connect to X server: Connection refused
Feb 14 11:12:21 pyra xinit[1974]: /usr/bin/xinit: server error
Feb 14 11:12:21 pyra systemd[1]: pyra-first-run.service: Main process exited, code=exited, status=1/FAILURE
Feb 14 11:12:21 pyra systemd[1]: pyra-first-run.service: Failed with result 'exit-code'.
Feb 14 11:12:21 pyra systemd[1]: Failed to start Pyra First Run Wizard.
root@pyra:~# uname -a
Linux pyra 5.12.1-letux-lpae #1 SMP PREEMPT Mon May 3 15:22:55 CEST 2021 armv7l GNU/Linux
root@pyra:~#
But root:root works so that I could now run pvrsrvctl.
Code:
root@pyra:~# dmesg|fgrep pvr
[    4.537746] pvrsrvkm 56000000.gpu: Enabling quirks 00000000
[    4.618765] [drm] Initialized pvr 1.17.4948957 20110701 for 56000000.gpu on minor 1
root@pyra:~# /opt/omap5-sgx-ddk-um-linux/bin/pvrsrvctl --no-module --start
PVR:(Error): PVRSRVBridgeCall: Failed to access device.  Function ID:3223086861 (strerror returns no value.). [0, ]
PVR:(Error): OpenServices: PVRSRVBridgeCall failed. [0, ]
PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [0, ]
PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [0, ]
/opt/omap5-sgx-ddk-um-linux/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=PVRSRV_ERROR_INIT_FAILURE)
root@pyra:~#
So at least I can reproduce the error message on your image. Interesting will be if the Letux image shows the same or not.
It smells like a memory access/alignment issue in the kernel driver. There were a lot of changes recently to make everything in Linux more 64-bit friendly and someone may have changed a macro or function which the original pvrsgx driver code assumes to be always 32 bit.
Also, getting makesd to produce a letux image isn't really cooperating anymore, can't seem to be able to generate a bootable image.
I had been using "sudo DEV=/dev/sdh ./makesd pyra+lc15-4gb" to generate it, which worked fine before. (haven't checked if it's the sd card, or if maybe the uboot files end up at the wrong block on the card)
What are the recommended options to get it to generate a pyra image with a more up to date kernel ?
Well, currently there is a server update running in the background so the download.goldelico.com may have been not available temporarily.
But it seems not to be the problem. Maybe you could run a "makesd -u" for self-update of the tool.

An SD card baked with your command partially boots a letux-5.4.114 kernel (lastest stable kernel) but is stuck locating the SD card (which should not be the case).
I remember there was recently some change because upstream did add mmc aliases to the device tree and that may have mixed up our fragile combination of u-boot, boot.scr, bootargs.scr, dts and kernel.

Getting the latest kernel (and latest Debian) can be done through "sudo DEV=/dev/sdh ./makesd -v latest pyra+lc15-4gb".
This also fails to boot - seems that some problem in the letux u-boot setup has crept in.

So my work program seems to be:
1. fix u-boot issue for fresh makesd-generated SD cards
2. look deeper into the SGX situation
 

aTc

Very Active Member
Joined
Apr 25, 2009
Messages
250
Does the first-run/xorg also fail when selecting the 5.6 kernel from the boot menu ?
I have no idea why that would fail. Unless i somehow ended up uploading a different image than the one i was testing with (although it having the 5.12.1 kernel should mean that it is).
 

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
Does the first-run/xorg also fail when selecting the 5.6 kernel from the boot menu ?
I have no idea why that would fail. Unless i somehow ended up uploading a different image than the one i was testing with (although it having the 5.12.1 kernel should mean that it is).
Good news:
1. starting your image

I flashed the card again (with a fresh download) and this time it did boot and run through the wizard. I checked that it is running your kernel build
Code:
[    0.000000] Linux version 5.12.1-letux-lpae (pyra@debian-buster) (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP PREEMPT Mon May 3 15:22:55 CEST 2021

Playing a little around shows your reported ACL issues:

Code:
[   36.967875] systemd-journald[1721]: Failed to set ACL on /var/log/journal/fd5bc67602a4469281f71532c2b2a65f/user-1000.journal, ignoring: Operation not supported

Can you name which CONFIGs are missing?

2. makesd and letux image
while I was able to reproduce the letux / makesd issue initially (i.e. yesterday) I wasn't any more today. So it was likely a temporary download server glitch (server was rebooted this morning). Well, the makesd tool is not very good in detecting download errors (because it does not exactly know what it should be able to download and what is optional).

So please check if "sudo DEV=/dev/sdh ./makesd -v latest pyra+lc15-4gb" works now. It bakes a Bullseye image without GUI.

3. trying to run PVRSGX on letux-5.12.1 with Bullseye
"apt-get install letux-pvrsgx-1.17" downloads and compiles the pvrsrv user-space for the Pyra.

Note: I had to do " rm -rf /var/lib/apt/lists; apt-get update" first because there seems to be an old version in the package cache of this image which is broken (does not apply OMAP5 patch).

Now I also get the same error:
Code:
root@letux:~# pvrsrvctl --no-module --start
[ 3656.324531] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable.
PVR:(Error): PVRSRVBridgeCall: Failed to access device.  Function ID:3223086861 (strerror returns no value.). [0, ]
PVR:(Error): OpenServices: PVRSRVBridgeCall failed. [0, ]
PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [0, ]
PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [0, ]
pvrsrvctl: SrvInit failed (already initialized?) (err=PVRSRV_ERROR_INIT_FAILURE)
root@letux:~#
So it is something in the kernel driver and not user-space.

Debugging is not very difficult but just time consuming. We can go back to older kernel binaries (that is why I needed to upgrade the Letux server to add a new disk for this archive) until we find the last version where it still did work. And then watch for significant changes or do a git bisect.

Thanks for reporting this issue!
 
Last edited:

Phlyra

FLOSSing
Joined
Jul 25, 2019
Messages
1,517
This might be a naïve question from a NOOB but would the SOF Project be useful for Pyra audio?
 

TrashyMG

Sarcasm Dispenser
Staff member
Joined
Jan 18, 2010
Messages
11,294
This might be a naïve question from a NOOB but would the SOF Project be useful for Pyra audio?
It seems to only support a handful of Intel embedded sound devices, so likely not?
 

Phlyra

FLOSSing
Joined
Jul 25, 2019
Messages
1,517
It seems to only support a handful of Intel embedded sound devices, so likely not?
That’s what I wondered initially but then when I RTFM on GitHub, in the Introduction section it says “Sound Open Firmware has a modular and generic codebase and can be ported to different DSP architectures or host platforms”?

There is a “Vendor Specific Architecture Information” subsection that mentions “Intel DSP Architecture” but is prefaced with:
“This is architecture specific to a single vendor that falls outside the scope of the high level generic SOF architecture.”

I only came across it after reading Phoronix’s article about the SOF2.0 release.
 
Last edited:

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
What's the current status of the audio driver?

Last info I heard was this little snippet of news from ED:
AESS almost working!
In regards of software, Nikolaus (@hns) has continued to work on porting the AESS subsystem from an older kernel to the current one.
This was A LOT more work than anyone anticipicated - but according to an email I received from him, it seems very likely he'll get it to work!
What's the AESS subsystem? Well, it's the hardware accelerated audio system of TI's audio chip we're using together with the OMAP.
At the moment, it's completely unused - which means, that all resampling, rerouting, etc. needs to be handled by the OMAP5, which means it slows down the system, heats it up a bit and doesn't allow to fully use the capabilities of the chip.
Without AESS, the audio chip always expects 96kHz audio - and the OMAP5 has to resample it whenever you play audio.
The TWL6040 Audio Companion IC is also on the OMAP5432 devboard if I'm not mistaken
 

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
Yes it is.. And on the PandaBoard ES. The main hardware differences are that the 5EVM only has a stereo headset output, the PandaES has one more accesible handsfree speaker output and the Pyra has two of them...
I have initially done some development for AESS on the OMAP5 EVM and then switched mainly to the PandaES because there I had a v3.15 based kernel tree that was said to work. Well, I was finally able to compile and run this 10 years old kernel tree. But I wasn't able to play any tone (except in legacy mode). Which is the same with the letux6.1-rc4 with the new AESS code. There is one more thing: the letux-aess kernel panics if I want to read back the AESS firmware from memory. I have got a hint from one of the original developers where to look at, but haven't done yet.
If you want to experiment a little, install the letux-6.1-rc4 kernel and rootfs files (Letux/root) with Debian 9.13 on the board(s) and run /root/build-aess-fw. Then reboot to get the firmware loaded.
 
Last edited:

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
Earlier this week I set out to build the original TI SDK for the omap5 line of cards. I went with the GLSDK 6.03.00.01 release. That's the last one which lists official support for OMAP5. All the SKDs can be found here: https://software-dl.ti.com/dsps/dsps_public_sw/glsdk/index.html

The TI GLSDK is basically a bunch of scripts for setting up what you need to use Yocto and download their co-processor support code (XDC tools, IPC, BIOS, etc.). It sets up all the Yocto layers you need and checks out the proper git commits for the release. At least when it works...

My first approach was to try and run this ancient Yocto on my modern Ubuntu 22.04 server. Well, that wasted a day :x

Next approach is to build it in a Ubuntu 12.04 docker container. Ubuntu 12.04 is the officially supported distro. This approach proved much better and bitbake is super close to completing the last 10-30 tasks, out of around ~4000, now! Then I'll flash an SD card, boot it up, and hopefully see the accelerated audio system in action. I thought it best to have a working, known good system for reference before trying to fix a non/semi-working driver :)

I'll post all my fixes to build the SDK online eventually, and maybe share the docker build image and a tarball with all needed packages. Most of my changes are for finding new mirrors for the packages it downloads during the build process. For now, here's the two docker "recipes" you need to install and setup the SDK:

* https://github.com/Risca/yocto-ubuntu-12.04
* https://github.com/Risca/ti-glsdk_omap5-uevm_6_03_00_01-docker
 
Last edited:

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
Hi, that is nice.

I did the same with the old PandaES driver recommended by Peter (omap-audio maintainer): https://github.com/omap-audio/linux-audio/tree/next-bnw/ti-audio-next_3.15
Here is my version with some fixes and an addition for a shell script that downloads and builds the matching firmware binary on the PandaES:
https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/omap-audio-3.15

Using this as a reference driver for the PandaES I was able to debug the amixer setup and firmware of the new driver. Then unfortunately, I had to interrupt and reduce most kernel work in Nov/Dec (same for the volume daemon). Just could do some maintenance, but no bug fixing.

The maturity state of the new driver (as of letux-6.1.y) is:
* loads well and does not crash on boot
* new matching firmware can be build from source
* shows a list of amixers identical to the old 3.15 driver
* aplay is working on the legacy interface (as without AESS drivers installed) and plays music on the headsets (arecord not tested)
* bugs:
- trying to play sound through the new interfaces times out
- it is not possible to read back the /sys/kernel/debug/pmem (crashes something in L3)
- https://github.com/omap-audio/audio-test fails

So I hope to find soon more time to finish climbing the Mt. AESSerest, having the summit already in view.. The last 3% are usually the most challenging...
 

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
Some tiny news:

After doing some more experiments, I think the firmware inside the AESS DSP may even be running... The effect of crashing the L3 with pmem can be traced to a read access to an undocumented register inside a register block (Table 8 in the document mentioned below) which controls the firmware inside the DSP. Reading this register may have an unknown side-effect in the DSP firmware...

Next, I remembered that there was a special document from TI about the AESS subsystem. Finally I found it again as SWPU245H (https://www.ti.com/pdfs/wtbu/OMAP4430_4460_4470_PUBLIC_TRM_Addendum_ABE_HAL_vH.pdf).

And after reading it again, I now better understand how the pieces fit together:

TI provides/provided a user-space library "ABE_HAL" that can access and configure the AESS by using direct access to the memory. I.e. without any kernel sound driver (not even ALSA). It just needs some user space program to provide a waveform data stream and write it to some buffers. And configure which connections the DSP should use to play on headset, bluetooth, handsfree or several whatever is connected to the OMAP and the twl6040.
The source code of the library is also available: https://git.goldelico.com/?p=letux-...ee56cb;hb=refs/heads/letux/aess-audio-test-v3 but not used by the audio-test tools.
This way of providing a driver for the AESS subsystem is likely good for debugging and bringing up the sound system. And maybe for a special handheld device not related to any specific operating system architecture.

The real Linux kernel driver code was derived from this library to do almost the same but more directly by using DAI and DAPM as the interfaces are called in Linux ALSA language. And this driver runs completely in kernel and allows to use standard amixer, aplay etc. to control everything.

My hope is that understanding this will help to get AESS debugged and fixed. For example I could boot without the Linux AESS driver and try to load firmware and access it through the ABE_HAL library.
 

matzesu

Forum Addict!
Staff member
Joined
Oct 24, 2008
Messages
12,679
Age
38
Location
Germany,, Saarland, at home
Just a not serious meant suggestion : why make the Audio whit difficult Electronic Devices and Software? Can’t whe have a few tiny Demons who play tiny instruments inside the Pyra? Like on Diskworld ?

Awesome Progress (this was serious meant )
 

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
Exciting! I wish I had more spare time to help out here!
 

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
Just a not serious meant suggestion : why make the Audio whit difficult Electronic Devices and Software? Can’t whe have a few tiny Demons who play tiny instruments inside the Pyra? Like on Diskworld ?

Awesome Progress (this was serious meant )
Well, there are already some tiny musicians inside :) They are called Electrons and Bits...

Joke put aside, there is again a minor progress. I did compare the v3.15 based setup with my latest build, both on the PandaBoard ES (which has the same audio architecture as the OMAP5) and found another difference. In /sys/debug/kernel/omap-aess/ports there is a list of the ports known to AESS. And there, "pdmdl1" and "pdmul1" were missing on the new kernel build.

Originally I thought there is a bug in the firmware build since I had turned the firmware build upside down. But research did reveal that some 10 years old patch originally from TI was missing. It defines which PDM interfaces the processor can handle. Upstream code defines one interface but AESS needs a seconds one. And it is only initialized by code introduced by this patch.

After forward-porting the mentioned patch to the latest kernel, the ports list is now complete.
Unfortunately, there is no other functional improvement yet...

Likely, we have more such quite simple road blocks ahead. But resolving one does not make it work. Like a stack of thin, opaque sheets with a small transparent dot on each sheet. Light only passes through when they all line up....

So let's try to analyse the next road block (which we do not even see yet in the fog).
 

Git1

Very Active Member
Joined
Dec 23, 2020
Messages
110
Well, there are already some tiny musicians inside :) They are called Electrons and Bits...

Joke put aside, there is again a minor progress. I did compare the v3.15 based setup with my latest build, both on the PandaBoard ES (which has the same audio architecture as the OMAP5) and found another difference. In /sys/debug/kernel/omap-aess/ports there is a list of the ports known to AESS. And there, "pdmdl1" and "pdmul1" were missing on the new kernel build.

Originally I thought there is a bug in the firmware build since I had turned the firmware build upside down. But research did reveal that some 10 years old patch originally from TI was missing. It defines which PDM interfaces the processor can handle. Upstream code defines one interface but AESS needs a seconds one. And it is only initialized by code introduced by this patch.

After forward-porting the mentioned patch to the latest kernel, the ports list is now complete.
Unfortunately, there is no other functional improvement yet...

Likely, we have more such quite simple road blocks ahead. But resolving one does not make it work. Like a stack of thin, opaque sheets with a small transparent dot on each sheet. Light only passes through when they all line up....

So let's try to analyse the next road block (which we do not even see yet in the fog).

Wow, that's a very amiable approach. Your effort is very much appreciated. I don't have a Pyra yet, but one day I will. When I get it I won't forget your efforts to make it better. Thank you so much!
 

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
Yes it is.. And on the PandaBoard ES. The main hardware differences are that the 5EVM only has a stereo headset output, the PandaES has one more accesible handsfree speaker output and the Pyra has two of them...
I have initially done some development for AESS on the OMAP5 EVM and then switched mainly to the PandaES because there I had a v3.15 based kernel tree that was said to work. Well, I was finally able to compile and run this 10 years old kernel tree. But I wasn't able to play any tone (except in legacy mode). Which is the same with the letux6.1-rc4 with the new AESS code. There is one more thing: the letux-aess kernel panics if I want to read back the AESS firmware from memory. I have got a hint from one of the original developers where to look at, but haven't done yet.
If you want to experiment a little, install the letux-6.1-rc4 kernel and rootfs files (Letux/root) with Debian 9.13 on the board(s) and run /root/build-aess-fw. Then reboot to get the firmware loaded.
I finally got a free evening to try the GLSDK 6.03.00.01 "reference build" I did earlier this month, and I think I got the AESS working on Linux-3.8. I was playing back 44.1 kHz wav file with 98% idle (top), and I got these printouts in the kernel log:
Code:
[ 8571.756805] omap-dma-engine 4a056000.dma-controller: allocating channel for 101
[ 8749.511840] omap-dma-engine 4a056000.dma-controller: freeing channel for 101

I had to setup the audio path with amixer, as described here and copied below for future reference:
Code:
  amixer cset -c 1 name='Headset Left Playback' 1
  amixer cset -c 1 name='Headset Right Playback' 1
  amixer cset -c 1 name='Headset Playback Volume' 12
  amixer cset -c 1 name='DL1 PDM Switch' 1
  amixer cset -c 1 name='Sidetone Mixer Playback' 1
  amixer cset -c 1 name='SDT DL Volume' 120
  amixer cset -c 1 name='DL1 Mixer Multimedia' 1
  amixer cset -c 1 name='DL1 Media Playback Volume' 110
  amixer sset -c 1 'Analog Left',0 'Aux/FM Left'
  amixer sset -c 1 'Analog Right',0 'Aux/FM Right'
  amixer sset -c 1 'Aux FM',0 7
  amixer sset -c 1 'AUDUL Media',0 149
  amixer sset -c 1 'Capture',0 4
  amixer sset -c 1 MUX_UL00,0 AMic0
  amixer sset -c 1 MUX_UL01,0 AMic1
  amixer sset -c 1 'AMIC UL',0 120

Let me know if anyone want more info or maybe SD card image
 

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
Full debug kernel log:
Code:
Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.8.13-gcc16f99 (yoctouser@441a9713f538) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP PREEMPT Wed Jan 4 15:53:51 UTC 2023
[    0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine: OMAP5 Panda board, model: TI OMAP5 uEVM board
[    0.000000] cma: CMA: reserved 8 MiB at 95000000
[    0.000000] cma: CMA: reserved 168 MiB at 95800000
[    0.000000] cma: CMA: reserved 16 MiB at ae800000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] OMAP5432 ES2.0
[    0.000000] PERCPU: Embedded 9 pages/cpu @c1f48000 s13568 r8192 d15104 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 515872
[    0.000000] Kernel command line: console=ttyO2,115200n8 vram=16M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] __ex_table already sorted, skipping sort
[    0.000000] Memory: 2031MB = 2031MB total
[    0.000000] Memory: 1849828k/1849828k available, 230940k reserved, 1301504K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc08ad444   (8854 kB)
[    0.000000]       .init : 0xc08ae000 - 0xc090b500   ( 374 kB)
[    0.000000]       .data : 0xc090c000 - 0xc09db3f0   ( 829 kB)
[    0.000000]        .bss : 0xc09db3f0 - 0xc0f3bdf8   (5507 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[    0.000000] OMAP clocksource: 32k_counter at 32768 Hz
[    0.000000] Architected local timer running at 6.14MHz (virt).
[    0.000000] Switching to timer-based delay loop
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[    0.000000] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.000000] ... MAX_LOCK_DEPTH:          48
[    0.000000] ... MAX_LOCKDEP_KEYS:        8191
[    0.000000] ... CLASSHASH_SIZE:          4096
[    0.000000] ... MAX_LOCKDEP_ENTRIES:     16384
[    0.000000] ... MAX_LOCKDEP_CHAINS:      32768
[    0.000000] ... CHAINHASH_SIZE:          16384
[    0.000000]  memory used by lock dependency info: 3695 kB
[    0.000000]  per task-struct memory footprint: 1152 bytes
[    0.000610] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.30 BogoMIPS (lpj=48000)
[    0.000610] pid_max: default: 32768 minimum: 301
[    0.000915] Security Framework initialized
[    0.001007] Mount-cache hash table entries: 512
[    0.015563] CPU: Testing write buffer coherency: ok
[    0.016235] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.016448] Setting up static identity map for 0x8060e370 - 0x8060e3e0
[    0.095764] CPU1: Booted secondary processor
[    0.095794] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.096099] Brought up 2 CPUs
[    0.096099] SMP: Total of 2 processors activated (24.61 BogoMIPS).
[    0.097778] devtmpfs: initialized
[    0.114288] omap_hwmod: aess: _wait_target_disable failed
[    0.138214] omap_hwmod: dss_dispc: cannot be enabled for reset (3)
[    0.140380] omap_hwmod: dss_dsi1_a: cannot be enabled for reset (3)
[    0.142547] omap_hwmod: dss_dsi1_b: cannot be enabled for reset (3)
[    0.144683] omap_hwmod: dss_dsi1_c: cannot be enabled for reset (3)
[    0.146850] omap_hwmod: dss_hdmi: cannot be enabled for reset (3)
[    0.148986] omap_hwmod: dss_rfbi: cannot be enabled for reset (3)
[    0.197906] pinctrl core: initialized pinctrl subsystem
[    0.200622] regulator-dummy: no parameters
[    0.204498] NET: Registered protocol family 16
[    0.225006] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.225494] omap-gpmc omap-gpmc: GPMC revision 6.0
[    0.225585] omap-gpmc omap-gpmc: failed to reserve memory
[    0.225616] omap-gpmc: probe of omap-gpmc failed with error -16
[    0.240936] OMAP GPIO hardware version 0.1
[    0.277984] No ATAGs?
[    0.278015] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.278015] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.280731] OMAP DMA hardware revision 0.0
[    0.284240] pinctrl-single 4a002840.pinmux: 219 pins at pa fc002840 size 438
[    0.284851] pinctrl-single 4ae0c840.pinmux: 28 pins at pa fce0c840 size 56
[    0.324218] bio: create slab <bio-0> at 0
[    0.326202] edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot
[    0.326232] edma-dma-engine: probe of edma-dma-engine.0 failed with error -5
[    0.363403] omap-dma-engine 4a056000.dma-controller: OMAP DMA engine driver
[    0.364807] vmmcsd_fixed: 3000 mV
[    0.365447] vmmcwl_fixed: 1800 mV
[    0.366027] hsusb2_reset: 3300 mV
[    0.366516] hsusb3_reset: 3300 mV
[    0.374847] SCSI subsystem initialized
[    0.376434] usbcore: registered new interface driver usbfs
[    0.376678] usbcore: registered new interface driver hub
[    0.376953] usbcore: registered new device driver usb
[    0.379486] omap_i2c 48070000.i2c: did not get pins for i2c error: -19
[    0.380249] omap_i2c 48070000.i2c: bus 0 rev0.12 at 400 kHz
[    0.384033] palmas 0-0048: Muxing GPIO 2, PWM 0, LED 0
[    0.384552] palmas 0-0048: Product ID c035
[    0.384765] palmas 0-0048: Product Design Rev 3
[    0.384948] palmas 0-0048: Product SW Rev a1
[    0.387542] smps123: 600 <--> 1500 mV at 1060 mV
[    0.389251] smps45: 600 <--> 1310 mV at 1030 mV
[    0.391418] smps6: 1200 mV
[    0.394378] smps7: 1800 mV
[    0.396118] smps8: 600 <--> 1310 mV at 1040 mV
[    0.398101] smps9: 2100 mV
[    0.399871] smps10: 5000 mV
[    0.400665] ldo1: 1500 <--> 1800 mV
[    0.402954] ldo2: 2800 mV
[    0.404663] ldo3: 1500 mV
[    0.405822] ldo4: 1500 <--> 1800 mV
[    0.407562] ldo5: 1800 mV
[    0.409271] ldo6: 1200 mV
[    0.410919] ldo7: 2000 mV
[    0.412658] ldo8: 3000 mV
[    0.414001] ldo9: 1800 <--> 3000 mV at 3000 mV
[    0.415740] ldoln: 1800 mV
[    0.417846] ldousb: 3250 mV
[    0.422607] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[    0.423095] omap_i2c 48072000.i2c: bus 1 rev0.12 at 100 kHz
[    0.423187] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
[    0.423675] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz
[    0.423767] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19
[    0.424224] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 100 kHz
[    0.424468] omap_i2c 4807c000.i2c: did not get pins for i2c error: -19
[    0.424926] omap_i2c 4807c000.i2c: bus 4 rev0.12 at 100 kHz
[    0.425964] Linux video capture interface: v2.00
[    0.427825] omap-iommu omap-iommu.0: mmu_dsp registered
[    0.427917] omap-iommu omap-iommu.1: mmu_ipu registered
[    0.428863] Advanced Linux Sound Architecture Driver Initialized.
[    0.430664] Bluetooth: Core ver 2.16
[    0.430877] NET: Registered protocol family 31
[    0.430877] Bluetooth: HCI device and connection manager initialized
[    0.430938] Bluetooth: HCI socket layer initialized
[    0.430969] Bluetooth: L2CAP socket layer initialized
[    0.430999] Bluetooth: SCO socket layer initialized
[    0.431121] Switching to clocksource arch_sys_counter
[    0.503051] NET: Registered protocol family 2
[    0.504089] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.504394] TCP bind hash table entries: 8192 (order: 6, 294912 bytes)
[    0.507019] TCP: Hash tables configured (established 8192 bind 8192)
[    0.507141] TCP: reno registered
[    0.507171] UDP hash table entries: 512 (order: 3, 40960 bytes)
[    0.507507] UDP-Lite hash table entries: 512 (order: 3, 40960 bytes)
[    0.508239] NET: Registered protocol family 1
[    0.509002] RPC: Registered named UNIX socket transport module.
[    0.509033] RPC: Registered udp transport module.
[    0.509033] RPC: Registered tcp transport module.
[    0.509033] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.533966] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.535491] platform omap-rproc.0: platform_device for rproc dsp created
[    0.535827] platform omap-rproc.1: platform_device for rproc ipu created
[    0.661193] bounce pool size: 64 pages
[    0.661560] VFS: Disk quotas dquot_6.5.2
[    0.661712] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.663391] NFS: Registering the id_resolver key type
[    0.663635] Key type id_resolver registered
[    0.663635] Key type id_legacy registered
[    0.663696] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.664123] msgmni has been set to 1454
[    0.665954] io scheduler noop registered
[    0.665985] io scheduler deadline registered
[    0.666046] io scheduler cfq registered (default)
[    0.669738] gpiochip_find_base: found new base at 488
[    0.670196] gpiochip_add: registered GPIOs 488 to 511 on device: tca6424a
[    0.672119] OMAP DSS rev 6.1
[    0.677276] of_get_named_gpio_flags exited with status 488
[    0.677307] of_get_named_gpio_flags exited with status 489
[    0.677337] of_get_named_gpio_flags exited with status 193
[    0.677368] of_get_named_gpio_flags exited with status 194
[    0.677368] of_get_named_gpio_flags exited with status 195
[    0.685607] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.689056] pinctrl core: add 1 pinmux maps
[    0.689086] pinctrl-single 4a002840.pinmux: found group selector 12 for pinmux_uart1_pins
[    0.689178] pinctrl-single 4a002840.pinmux: request pin 48 (4a0028a0) for 4806a000.serial
[    0.689178] pinctrl-single 4a002840.pinmux: request pin 49 (4a0028a2) for 4806a000.serial
[    0.689208] pinctrl-single 4a002840.pinmux: request pin 50 (4a0028a4) for 4806a000.serial
[    0.689208] pinctrl-single 4a002840.pinmux: request pin 51 (4a0028a6) for 4806a000.serial
[    0.689208] pinctrl-single 4a002840.pinmux: enabling pinmux_uart1_pins function12
[    0.689453] 4806a000.serial: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
[    0.690277] omap_uart 4806c000.serial: did not get pins for uart1 error: -19
[    0.690429] 4806c000.serial: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1
[    0.691040] pinctrl core: add 1 pinmux maps
[    0.691040] pinctrl-single 4a002840.pinmux: found group selector 13 for pinmux_uart3_pins
[    0.691070] pinctrl-single 4a002840.pinmux: request pin 205 (4a0029da) for 48020000.serial
[    0.691070] pinctrl-single 4a002840.pinmux: request pin 206 (4a0029dc) for 48020000.serial
[    0.691101] pinctrl-single 4a002840.pinmux: enabling pinmux_uart3_pins function13
[    0.691223] 48020000.serial: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2
[    1.622467] console [ttyO2] enabled
[    1.626739] omap_uart 4806e000.serial: did not get pins for uart3 error: -19
[    1.634277] 4806e000.serial: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
[    1.642822] pinctrl core: add 1 pinmux maps
[    1.642822] pinctrl-single 4a002840.pinmux: found group selector 14 for pinmux_uart5_pins
[    1.642852] pinctrl-single 4a002840.pinmux: request pin 184 (4a0029b0) for 48066000.serial
[    1.642852] pinctrl-single 4a002840.pinmux: request pin 185 (4a0029b2) for 48066000.serial
[    1.642883] pinctrl-single 4a002840.pinmux: request pin 186 (4a0029b4) for 48066000.serial
[    1.642883] pinctrl-single 4a002840.pinmux: request pin 187 (4a0029b6) for 48066000.serial
[    1.642883] pinctrl-single 4a002840.pinmux: request pin 192 (4a0029c0) for 48066000.serial
[    1.642883] pinctrl-single 4a002840.pinmux: enabling pinmux_uart5_pins function14
[    1.643066] 48066000.serial: ttyO4 at MMIO 0x48066000 (irq = 137) is a OMAP UART4
[    1.651550] omap_uart 48068000.serial: did not get pins for uart5 error: -19
[    1.659088] 48068000.serial: ttyO5 at MMIO 0x48068000 (irq = 138) is a OMAP UART5
[    1.668640] [drm] Initialized drm 1.1.0 20060810
[    1.688354] brd: module loaded
[    1.700347] loop: module loaded
[    1.703948] (stk) :sysfs entries created
[    1.708160] (stk) : debugfs entries created
[    1.712982] gccore gccore.0: opp_get_opp_count: device OPP not found (-19)
[    1.740692] of_get_named_gpio_flags exited with status 141
[    1.746368] palmas-pwm palmas_pwm.35: there are no PWMs muxed
[    1.752502] palmas-pwm: probe of palmas_pwm.35 failed with error -22
[    1.762481] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.769927] OneNAND driver initializing
[    1.774444] omap2_mcspi 48098000.spi: pins are not configured from the driver
[    1.782684] pinctrl core: add 1 pinmux maps
[    1.782714] pinctrl-single 4a002840.pinmux: found group selector 15 for pinmux_mcspi2_pins
[    1.782745] pinctrl-single 4a002840.pinmux: request pin 94 (4a0028fc) for 4809a000.spi
[    1.782745] pinctrl-single 4a002840.pinmux: request pin 95 (4a0028fe) for 4809a000.spi
[    1.782745] pinctrl-single 4a002840.pinmux: request pin 96 (4a002900) for 4809a000.spi
[    1.782775] pinctrl-single 4a002840.pinmux: request pin 97 (4a002902) for 4809a000.spi
[    1.782775] pinctrl-single 4a002840.pinmux: enabling pinmux_mcspi2_pins function15
[    1.783447] pinctrl core: add 1 pinmux maps
[    1.783447] pinctrl-single 4a002840.pinmux: found group selector 16 for pinmux_mcspi3_pins
[    1.783477] pinctrl-single 4a002840.pinmux: request pin 60 (4a0028b8) for 480b8000.spi
[    1.783477] pinctrl-single 4a002840.pinmux: request pin 61 (4a0028ba) for 480b8000.spi
[    1.783508] pinctrl-single 4a002840.pinmux: request pin 62 (4a0028bc) for 480b8000.spi
[    1.783508] pinctrl-single 4a002840.pinmux: request pin 63 (4a0028be) for 480b8000.spi
[    1.783508] pinctrl-single 4a002840.pinmux: enabling pinmux_mcspi3_pins function16
[    1.783996] pinctrl core: add 1 pinmux maps
[    1.784027] pinctrl-single 4a002840.pinmux: found group selector 17 for pinmux_mcspi4_pins
[    1.784057] pinctrl-single 4a002840.pinmux: request pin 178 (4a0029a4) for 480ba000.spi
[    1.784057] pinctrl-single 4a002840.pinmux: pin 4a0029a4 already requested by 4a002840.pinmux; cannot claim for 480ba000.spi
[    1.795837] pinctrl-single 4a002840.pinmux: pin-178 (480ba000.spi) status -22
[    1.803344] pinctrl-single 4a002840.pinmux: could not request pin 178 on device pinctrl-single
[    1.812377] pinctrl-single 4a002840.pinmux: ignoring disable for pinmux_mcspi4_pins function17
[    1.812408] omap2_mcspi 480ba000.spi: pins are not configured from the driver
[    1.824279] usbcore: registered new interface driver asix
[    1.830169] usbcore: registered new interface driver cdc_ether
[    1.836486] usbcore: registered new interface driver smsc95xx
[    1.842712] usbcore: registered new interface driver net1080
[    1.848846] usbcore: registered new interface driver cdc_subset
[    1.855285] usbcore: registered new interface driver zaurus
[    1.861358] usbcore: registered new interface driver cdc_ncm
[    1.868164] usbcore: registered new interface driver cdc_wdm
[    1.874114] Initializing USB Mass Storage driver...
[    1.879455] usbcore: registered new interface driver usb-storage
[    1.885742] USB Mass Storage support registered.
[    1.890808] usbcore: registered new interface driver usbtest
[    1.897674] mousedev: PS/2 mouse device common for all mice
[    1.910278] palmas-rtc palmas_rtc.30: rtc core: registered palmas_rtc.30 as rtc0
[    1.919860] i2c /dev entries driver
[    1.927276] Driver for 1-wire Dallas network protocol.
[    1.934906] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.944427] palmas-wdt palmas_wdt.29: Failed to register misc device
[    1.951110] palmas-wdt: probe of palmas_wdt.29 failed with error -16
[    1.958251] hdev edb69000
[    1.959259] HCI device registered (hdev edb69000)
[    1.959503] hci0 edb69000
[    1.961120] of_get_named_gpio_flags: can't parse gpios property
[    1.961151] of_get_named_gpio_flags: can't parse gpios property
[    1.961486] omap-dma-engine 4a056000.dma-controller: allocating channel for 62
[    1.961517] omap-dma-engine 4a056000.dma-controller: allocating channel for 61
[    1.959533] (stc):  chnl_id list empty :4
[    1.979156] (stk) : st_kim_start<4>[    1.983428] omap_hsmmc 4809c000.mmc: pins are not configured from the driver
[    2.033203] of_get_named_gpio_flags: can't parse gpios property
[    2.033203] of_get_named_gpio_flags: can't parse gpios property
[    2.033325] omap-dma-engine 4a056000.dma-controller: allocating channel for 48
[    2.041015] omap-dma-engine 4a056000.dma-controller: allocating channel for 47
[    2.051818] omap_hsmmc 480b4000.mmc: pins are not configured from the driver
[    2.098571] mmc0: host does not support reading read-only switch. assuming write-enable.
[    2.103302] of_get_named_gpio_flags: can't parse gpios property
[    2.103302] of_get_named_gpio_flags: can't parse gpios property
[    2.103424] omap-dma-engine 4a056000.dma-controller: allocating channel for 78
[    2.103424] omap-dma-engine 4a056000.dma-controller: allocating channel for 77
[    2.103607] omap_hsmmc 480ad000.mmc: pins are not configured from the driver
[    2.131622] mmc0: new high speed SDHC card at address 59b4
[    2.138427] mmcblk0: mmc0:59b4 USD   7.51 GiB
[    2.145629]  mmcblk0: p1 p2
[    2.217620] mmc1: BKOPS_EN bit is not set
[    2.221282] leds-gpio leds.20: pins are not configured from the driver
[    2.221313] of_get_named_gpio_flags exited with status 153
[    2.221313] of_get_named_gpio_flags exited with status 153
[    2.222747] ledtrig-cpu: registered to indicate activity on CPUs
[    2.223632] usbcore: registered new interface driver usbhid
[    2.223632] usbhid: USB HID core driver
[    2.224304] platform 4a0021e0.bandgap: Driver ti-soc-thermal requests probe deferral
[    2.253662]  remoteproc0: dsp is available
[    2.254791] mmc1: new high speed MMC card at address 0001
[    2.263641]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    2.273071]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    2.273132] mmcblk1: mmc1:0001 SEM04G 3.68 GiB
[    2.273437] mmcblk1boot0: mmc1:0001 SEM04G partition 1 2.00 MiB
[    2.273712] mmcblk1boot1: mmc1:0001 SEM04G partition 2 2.00 MiB
[    2.301788]  mmcblk1: unknown partition table
[    2.302093]  remoteproc1: ipu is available
[    2.302093]  remoteproc1: Note: remoteproc is still under development and considered experimental.
[    2.302093]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    2.333374]  mmcblk1boot1: unknown partition table
[    2.340362]  mmcblk1boot0: unknown partition table
[    2.353759] omap-hdmi-audio-card sound_hdmi.19:  omap-hdmi-hifi <-> omap-hdmi-audio mapping ok
[    2.367645] oprofile: no performance counters
[    2.373260] oprofile: using timer interrupt.
[    2.378082] TCP: cubic registered
[    2.381530] Initializing XFRM netlink socket
[    2.386108] NET: Registered protocol family 17
[    2.390808] NET: Registered protocol family 15
[    2.395629] Bluetooth: RFCOMM TTY layer initialized
[    2.400787] Bluetooth: RFCOMM socket layer initialized
[    2.406188] Bluetooth: RFCOMM ver 1.11
[    2.410125] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.415710] Bluetooth: BNEP socket layer initialized
[    2.420898] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.427124] Bluetooth: HIDP socket layer initialized
[    2.432525] Key type dns_resolver registered
[    2.437011] NET: Registered protocol family 40
[    2.087585] (stk) :ldisc_install = 1
[    2.441955] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    2.450256] mux: Failed to setup hwmod io irq -22
[    2.458343] Power Management for TI OMAP4PLUS devices.
[    2.463867] ThumbEE CPU extension supported.
[    2.469879] ldo8: disabling
[    2.473663] ldo3: disabling
[    2.479095] dmm 4e000000.dmm: initialized all PAT entries
[    2.488555] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    2.495544] [drm] No driver support for vblank timestamp query.
[    2.505767] omapdrm omapdrm.0: No connectors reported connected with modes
[    2.513000] [drm] Cannot find any crtc or sizes - going 1024x768
[    2.524658] [drm] Enabling DMM ywrap scrolling
[    2.534515] Console: switching to colour frame buffer device 128x48
[    2.544464] omapdrm omapdrm.0: fb0: omapdrm frame buffer device
[    2.550659] omapdrm omapdrm.0: registered panic notifier
[    2.556243] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0
[    2.567779] palmas-rtc palmas_rtc.30: setting system clock to 2023-01-05 21:13:31 UTC (1672953211)
[    2.577423] ALSA device list:
[    2.580535]   #0: OMAP5HDMI
[    2.663543] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.672058] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.680511] devtmpfs: mounted
[    2.683807] Freeing init memory: 372K
[    3.087677] (stk) :ldisc installation timeout
[    3.092132] (stk) :ldisc_install = 0udevd[1017]: starting version 182
[    4.018218] aess 401f1000.aess: Failed to load firmware 0
[    4.095397] (stk) : timed out waiting for ldisc to be un-installed
[    4.208801] (stk) :ldisc_install = 1<6>[    4.336761] palmas-usb palmas_usb.36: Initialized Palmas USB module
[    4.583190] ahci ahci.0.auto: can't get clock
[    4.610748] ahci: SSS flag set, parallel bus scan disabled
[    4.693145] ahci ahci.0.auto: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[    4.732025]  remoteproc1: failed to load ducati-m3-core0.xem3
[    4.740112] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.742401]  remoteproc0: failed to load tesla-dsp.xe64T
[    4.759338] ahci ahci.0.auto: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part ccc apst
[    4.771057] omap-abe-twl6040 sound.18: McASP node is not provided
[    4.784515] aess 401f1000.aess: ABE firmware size 54048 bytes
[    4.790527] aess 401f1000.aess: ABE mem P 8192 C 7852 D 16384 S 21600 bytes
[    4.810699] ehci-omap: OMAP-EHCI Host Controller driver
[    4.853332] scsi0 : ahci_platform
[    4.876464] ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a1401ff] port 0x100 irq 86
[    4.899414] aess 401f1000.aess: ABE Firmware version 9590
[    5.012329] aess 401f1000.aess: ABE Config size 6160 bytes
[    5.018249] ehci-omap 4a064c00.ehci: EHCI Host Controller
[    5.101623] aess 401f1000.aess: ASoC: got 5 new coefficients
[    5.101654] aess 401f1000.aess: ASoC: adding enum kcontrol DL1 Equalizer size 5
[    5.101654] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Equalizer
[    5.101745] aess 401f1000.aess: ASoC: got 5 new coefficients
[    5.101776] aess 401f1000.aess: ASoC: adding enum kcontrol DL2 Left Equalizer size 5
[    5.101776] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Left Equalizer
[    5.101806] aess 401f1000.aess: ASoC: got 5 new coefficients
[    5.101806] aess 401f1000.aess: ASoC: adding enum kcontrol DL2 Right Equalizer size 5
[    5.101806] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Right Equalizer
[    5.101837] aess 401f1000.aess: ASoC: got 4 new coefficients
[    5.101837] aess 401f1000.aess: ASoC: adding enum kcontrol SDT Equalizer size 4
[    5.101837] aess 401f1000.aess: ASoC: no handler specified for kcontrol SDT Equalizer
[    5.101867] aess 401f1000.aess: ASoC: got 3 new coefficients
[    5.101867] aess 401f1000.aess: ASoC: adding enum kcontrol DMic Equalizer size 3
[    5.101867] aess 401f1000.aess: ASoC: no handler specified for kcontrol DMic Equalizer
[    5.101898] aess 401f1000.aess: ASoC: got 3 new coefficients
[    5.101898] aess 401f1000.aess: ASoC: adding enum kcontrol Amic Equalizer size 3
[    5.101898] aess 401f1000.aess: ASoC: no handler specified for kcontrol Amic Equalizer
[    5.101928] aess 401f1000.aess: ASoC: Got 0x92c bytes of type 1 version 0 vendor 0 at pass 1
[    5.101928] aess 401f1000.aess: ASoC: adding 26 kcontrols
[    5.101928] aess 401f1000.aess: ASoC: adding mixer kcontrol DL1 Media Playback Volume with access 0x13
[    5.101959] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Media Playback Volume
[    5.101959] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.101959] aess 401f1000.aess: ASoC: adding mixer kcontrol DL1 Tones Playback Volume with access 0x13
[    5.101989] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Tones Playback Volume
[    5.101989] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.101989] aess 401f1000.aess: ASoC: adding mixer kcontrol DL1 Voice Playback Volume with access 0x13
[    5.101989] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Voice Playback Volume
[    5.102020] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102020] aess 401f1000.aess: ASoC: adding mixer kcontrol DL1 Capture Playback Volume with access 0x13
[    5.102020] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Capture Playback Volume
[    5.102050] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102050] aess 401f1000.aess: ASoC: adding mixer kcontrol DL2 Media Playback Volume with access 0x13
[    5.102081] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Media Playback Volume
[    5.102081] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102081] aess 401f1000.aess: ASoC: adding mixer kcontrol DL2 Tones Playback Volume with access 0x13
[    5.102081] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Tones Playback Volume
[    5.102111] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102111] aess 401f1000.aess: ASoC: adding mixer kcontrol DL2 Voice Playback Volume with access 0x13
[    5.102111] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Voice Playback Volume
[    5.102142] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102142] aess 401f1000.aess: ASoC: adding mixer kcontrol DL2 Capture Playback Volume with access 0x13
[    5.102142] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Capture Playback Volume
[    5.102172] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102172] aess 401f1000.aess: ASoC: adding mixer kcontrol VXREC Media Volume with access 0x13
[    5.102172] aess 401f1000.aess: ASoC: no handler specified for kcontrol VXREC Media Volume
[    5.102203] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102203] aess 401f1000.aess: ASoC: adding mixer kcontrol VXREC Tones Volume with access 0x13
[    5.102203] aess 401f1000.aess: ASoC: no handler specified for kcontrol VXREC Tones Volume
[    5.102203] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102233] aess 401f1000.aess: ASoC: adding mixer kcontrol VXREC Voice DL Volume with access 0x13
[    5.102233] aess 401f1000.aess: ASoC: no handler specified for kcontrol VXREC Voice DL Volume
[    5.102233] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102264] aess 401f1000.aess: ASoC: adding mixer kcontrol VXREC Voice UL Volume with access 0x13
[    5.102264] aess 401f1000.aess: ASoC: no handler specified for kcontrol VXREC Voice UL Volume
[    5.102264] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102294] aess 401f1000.aess: ASoC: adding mixer kcontrol AUDUL Media Volume with access 0x13
[    5.102294] aess 401f1000.aess: ASoC: no handler specified for kcontrol AUDUL Media Volume
[    5.102294] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102325] aess 401f1000.aess: ASoC: adding mixer kcontrol AUDUL Tones Volume with access 0x13
[    5.102325] aess 401f1000.aess: ASoC: no handler specified for kcontrol AUDUL Tones Volume
[    5.102325] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102355] aess 401f1000.aess: ASoC: adding mixer kcontrol AUDUL Voice UL Volume with access 0x13
[    5.102355] aess 401f1000.aess: ASoC: no handler specified for kcontrol AUDUL Voice UL Volume
[    5.102355] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102355] aess 401f1000.aess: ASoC: adding mixer kcontrol AUDUL Voice DL Volume with access 0x13
[    5.102386] aess 401f1000.aess: ASoC: no handler specified for kcontrol AUDUL Voice DL Volume
[    5.102386] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102416] aess 401f1000.aess: ASoC: adding mixer kcontrol SDT UL Volume with access 0x13
[    5.102416] aess 401f1000.aess: ASoC: no handler specified for kcontrol SDT UL Volume
[    5.102416] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102447] aess 401f1000.aess: ASoC: adding mixer kcontrol SDT DL Volume with access 0x13
[    5.102447] aess 401f1000.aess: ASoC: no handler specified for kcontrol SDT DL Volume
[    5.102447] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102478] aess 401f1000.aess: ASoC: adding mixer kcontrol DMIC1 UL Volume with access 0x13
[    5.102478] aess 401f1000.aess: ASoC: no handler specified for kcontrol DMIC1 UL Volume
[    5.102478] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102508] aess 401f1000.aess: ASoC: adding mixer kcontrol DMIC2 UL Volume with access 0x13
[    5.102508] aess 401f1000.aess: ASoC: no handler specified for kcontrol DMIC2 UL Volume
[    5.102508] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102539] aess 401f1000.aess: ASoC: adding mixer kcontrol DMIC3 UL Volume with access 0x13
[    5.102539] aess 401f1000.aess: ASoC: no handler specified for kcontrol DMIC3 UL Volume
[    5.102539] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102569] aess 401f1000.aess: ASoC: adding mixer kcontrol AMIC UL Volume with access 0x13
[    5.102569] aess 401f1000.aess: ASoC: no handler specified for kcontrol AMIC UL Volume
[    5.102600] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102600] aess 401f1000.aess: ASoC: adding mixer kcontrol BT UL Volume with access 0x13
[    5.102600] aess 401f1000.aess: ASoC: no handler specified for kcontrol BT UL Volume
[    5.102600] aess 401f1000.aess:  created TLV type 1 size 8 bytes
[    5.102630] aess 401f1000.aess: ASoC: adding mixer kcontrol DL1 Mono Mixer with access 0x0
[    5.102630] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL1 Mono Mixer
[    5.102661] aess 401f1000.aess: ASoC: adding mixer kcontrol DL2 Mono Mixer with access 0x0
[    5.102661] aess 401f1000.aess: ASoC: no handler specified for kcontrol DL2 Mono Mixer
[    5.102661] aess 401f1000.aess: ASoC: adding mixer kcontrol AUDUL Mono Mixer with access 0x0
[    5.102691] aess 401f1000.aess: ASoC: no handler specified for kcontrol AUDUL Mono Mixer
[    5.102691] aess 401f1000.aess: ASoC: adding 46 DAPM widgets
[    5.102691] aess 401f1000.aess: ASoC: creating DAPM widget TONES_DL id 23
[    5.102722] aess 401f1000.aess: ASoC: creating DAPM widget VX_DL id 23
[    5.102722] aess 401f1000.aess: ASoC: creating DAPM widget VX_UL id 24
[    5.102752] aess 401f1000.aess: ASoC: creating DAPM widget MM_UL1 id 24
[    5.102752] aess 401f1000.aess: ASoC: creating DAPM widget MM_UL2 id 24
[    5.102783] aess 401f1000.aess: ASoC: creating DAPM widget MM_DL id 23
[    5.102783] aess 401f1000.aess: ASoC: creating DAPM widget MODEM_DL id 23
[    5.102813] aess 401f1000.aess: ASoC: creating DAPM widget MODEM_UL id 24
[    5.102813] aess 401f1000.aess: ASoC: creating DAPM widget PDM_UL1 id 23
[    5.102844] aess 401f1000.aess: ASoC: creating DAPM widget PDM_DL1 id 24
[    5.102844] aess 401f1000.aess: ASoC: creating DAPM widget PDM_DL2 id 24
[    5.102844] aess 401f1000.aess: ASoC: creating DAPM widget BT_VX_UL id 23
[    5.102874] aess 401f1000.aess: ASoC: creating DAPM widget BT_VX_DL id 24
[    5.102874] aess 401f1000.aess: ASoC: creating DAPM widget MM_EXT_UL id 23
[    5.102905] aess 401f1000.aess: ASoC: creating DAPM widget MM_EXT_DL id 24
[    5.102905] aess 401f1000.aess: ASoC: creating DAPM widget DMIC0 id 23
[    5.102935] aess 401f1000.aess: ASoC: creating DAPM widget DMIC1 id 23
[    5.102935] aess 401f1000.aess: ASoC: creating DAPM widget DMIC2 id 23
[    5.102935] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL00 id 2
[    5.102966] aess 401f1000.aess: ASoC: widget MUX_UL00 has 1 controls of type 828206
[    5.102966] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.102966] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.102996] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL00
[    5.102996] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL01 id 2
[    5.102996] aess 401f1000.aess: ASoC: widget MUX_UL01 has 1 controls of type 828206
[    5.103027] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.103027] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.103057] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL01
[    5.103057] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL02 id 2
[    5.103057] aess 401f1000.aess: ASoC: widget MUX_UL02 has 1 controls of type 828206
[    5.103088] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.103088] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.103088] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL02
[    5.103118] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL03 id 2
[    5.103118] aess 401f1000.aess: ASoC: widget MUX_UL03 has 1 controls of type 828206
[    5.103118] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.103149] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.119201] ehci-omap 4a064c00.ehci: new USB bus registered, assigned bus number 1
[    5.136535] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL03
[    5.136566] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL04 id 2
[    5.136596] aess 401f1000.aess: ASoC: widget MUX_UL04 has 1 controls of type 828206
[    5.136596] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136627] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136627] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL04
[    5.136627] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL05 id 2
[    5.136657] aess 401f1000.aess: ASoC: widget MUX_UL05 has 1 controls of type 828206
[    5.136657] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136688] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136688] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL05
[    5.136688] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL10 id 2
[    5.136718] aess 401f1000.aess: ASoC: widget MUX_UL10 has 1 controls of type 828206
[    5.136718] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136749] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136749] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL10
[    5.136779] aess 401f1000.aess: ASoC: creating DAPM widget MUX_UL11 id 2
[    5.136779] aess 401f1000.aess: ASoC: widget MUX_UL11 has 1 controls of type 828206
[    5.136810] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136810] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136840] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_UL11
[    5.136840] aess 401f1000.aess: ASoC: creating DAPM widget MUX_VX0 id 2
[    5.136840] aess 401f1000.aess: ASoC: widget MUX_VX0 has 1 controls of type 828206
[    5.136871] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136871] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136871] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_VX0
[    5.136901] aess 401f1000.aess: ASoC: creating DAPM widget MUX_VX1 id 2
[    5.136901] aess 401f1000.aess: ASoC: widget MUX_VX1 has 1 controls of type 828206
[    5.136901] aess 401f1000.aess:  adding DAPM widget enum control Route
[    5.136932] aess 401f1000.aess: ASoC: no handler specified for kcontrol Route
[    5.136932] aess 401f1000.aess: ASoC: no handler specified for ext widget MUX_VX1
[    5.136962] aess 401f1000.aess: ASoC: creating DAPM widget DL1 Mixer id 5
[    5.136962] aess 401f1000.aess: ASoC: widget DL1 Mixer has 4 controls of type 808001
[    5.136962] aess 401f1000.aess:  adding DAPM widget mixer control Tones at 0
[    5.136993] aess 401f1000.aess: ASoC: no handler specified for kcontrol Tones
[    5.136993] aess 401f1000.aess:  adding DAPM widget mixer control Voice at 1
[    5.136993] aess 401f1000.aess: ASoC: no handler specified for kcontrol Voice
[    5.137023] aess 401f1000.aess:  adding DAPM widget mixer control Capture at 2
[    5.137023] aess 401f1000.aess: ASoC: no handler specified for kcontrol Capture
[    5.137023] aess 401f1000.aess:  adding DAPM widget mixer control Multimedia at 3
[    5.137054] aess 401f1000.aess: ASoC: no handler specified for kcontrol Multimedia
[    5.137054] aess 401f1000.aess: ASoC: no handler specified for ext widget DL1 Mixer
[    5.137054] aess 401f1000.aess: ASoC: creating DAPM widget DL2 Mixer id 5
[    5.137084] aess 401f1000.aess: ASoC: widget DL2 Mixer has 4 controls of type 808001
[    5.137084] aess 401f1000.aess:  adding DAPM widget mixer control Tones at 0
[    5.137084] aess 401f1000.aess: ASoC: no handler specified for kcontrol Tones
[    5.137084] aess 401f1000.aess:  adding DAPM widget mixer control Voice at 1
[    5.137115] aess 401f1000.aess: ASoC: no handler specified for kcontrol Voice
[    5.137115] aess 401f1000.aess:  adding DAPM widget mixer control Capture at 2
[    5.137115] aess 401f1000.aess: ASoC: no handler specified for kcontrol Capture
[    5.137115] aess 401f1000.aess:  adding DAPM widget mixer control Multimedia at 3
[    5.137145] aess 401f1000.aess: ASoC: no handler specified for kcontrol Multimedia
[    5.137145] aess 401f1000.aess: ASoC: no handler specified for ext widget DL2 Mixer
[    5.137145] aess 401f1000.aess: ASoC: creating DAPM widget DL1 Media Volume id 7
[    5.137176] aess 401f1000.aess: ASoC: creating DAPM widget Voice Capture Mixer id 5
[    5.137207] aess 401f1000.aess: ASoC: widget Voice Capture Mixer has 3 controls of type 808001
[    5.137207] aess 401f1000.aess:  adding DAPM widget mixer control Tones Playback at 0
[    5.137207] aess 401f1000.aess: ASoC: no handler specified for kcontrol Tones Playback
[    5.137237] aess 401f1000.aess:  adding DAPM widget mixer control Media Playback at 1
[    5.137237] aess 401f1000.aess: ASoC: no handler specified for kcontrol Media Playback
[    5.137237] aess 401f1000.aess:  adding DAPM widget mixer control Capture at 2
[    5.137237] aess 401f1000.aess: ASoC: no handler specified for kcontrol Capture
[    5.137268] aess 401f1000.aess: ASoC: no handler specified for ext widget Voice Capture Mixer
[    5.137268] aess 401f1000.aess: ASoC: creating DAPM widget Capture Mixer id 5
[    5.137298] aess 401f1000.aess: ASoC: widget Capture Mixer has 4 controls of type 808001
[    5.137298] aess 401f1000.aess:  adding DAPM widget mixer control Tones at 0
[    5.137298] aess 401f1000.aess: ASoC: no handler specified for kcontrol Tones
[    5.137298] aess 401f1000.aess:  adding DAPM widget mixer control Voice Playback at 1
[    5.137329] aess 401f1000.aess: ASoC: no handler specified for kcontrol Voice Playback
[    5.137329] aess 401f1000.aess:  adding DAPM widget mixer control Voice Capture at 2
[    5.137329] aess 401f1000.aess: ASoC: no handler specified for kcontrol Voice Capture
[    5.137359] aess 401f1000.aess:  adding DAPM widget mixer control Media Playback at 3
[    5.137359] aess 401f1000.aess: ASoC: no handler specified for kcontrol Media Playback
[    5.137359] aess 401f1000.aess: ASoC: no handler specified for ext widget Capture Mixer
[    5.137390] aess 401f1000.aess: ASoC: creating DAPM widget Sidetone Mixer id 5
[    5.137390] aess 401f1000.aess: ASoC: widget Sidetone Mixer has 2 controls of type 808001
[    5.137390] aess 401f1000.aess:  adding DAPM widget mixer control Capture at 0
[    5.137390] aess 401f1000.aess: ASoC: no handler specified for kcontrol Capture
[    5.137420] aess 401f1000.aess:  adding DAPM widget mixer control Playback at 1
[    5.137420] aess 401f1000.aess: ASoC: no handler specified for kcontrol Playback
[    5.137420] aess 401f1000.aess: ASoC: no handler specified for ext widget Sidetone Mixer
[    5.137451] aess 401f1000.aess: ASoC: creating DAPM widget DL1 PDM id 5
[    5.137451] aess 401f1000.aess: ASoC: widget DL1 PDM has 1 controls of type 848001
[    5.137481] aess 401f1000.aess:  adding DAPM widget mixer control Switch at 0
[    5.137481] aess 401f1000.aess: ASoC: no handler specified for kcontrol Switch
[    5.137481] aess 401f1000.aess: ASoC: no handler specified for ext widget DL1 PDM
[    5.137512] aess 401f1000.aess: ASoC: creating DAPM widget DL1 BT_VX id 5
[    5.137512] aess 401f1000.aess: ASoC: widget DL1 BT_VX has 1 controls of type 848001
[    5.137512] aess 401f1000.aess:  adding DAPM widget mixer control Switch at 0
[    5.137512] aess 401f1000.aess: ASoC: no handler specified for kcontrol Switch
[    5.137542] aess 401f1000.aess: ASoC: no handler specified for ext widget DL1 BT_VX
[    5.137542] aess 401f1000.aess: ASoC: creating DAPM widget DL1 MM_EXT id 5
[    5.137542] aess 401f1000.aess: ASoC: widget DL1 MM_EXT has 1 controls of type 848001
[    5.137573] aess 401f1000.aess:  adding DAPM widget mixer control Switch at 0
[    5.137573] aess 401f1000.aess: ASoC: no handler specified for kcontrol Switch
[    5.137573] aess 401f1000.aess: ASoC: no handler specified for ext widget DL1 MM_EXT
[    5.137603] aess 401f1000.aess: ASoC: creating DAPM widget Sidetone Capture VMixer id 5
[    5.137603] aess 401f1000.aess: ASoC: creating DAPM widget Voice Capture VMixer id 5
[    5.138610] aess 401f1000.aess: ASoC: creating DAPM widget DL1 Capture VMixer id 5
[    5.138641] aess 401f1000.aess: ASoC: creating DAPM widget DL2 Capture VMixer id 5
[    5.138671] aess 401f1000.aess: ASoC: creating DAPM widget VX UL VMixer id 5
[    5.138671] aess 401f1000.aess: ASoC: creating DAPM widget VX DL VMixer id 5
[    5.138702] aess 401f1000.aess: ASoC: creating DAPM widget MM VMixer id 5
[    5.138702] aess 401f1000.aess: ASoC: creating DAPM widget BE_OUT id 1
[    5.138732] aess 401f1000.aess: ASoC: creating DAPM widget BE_IN id 0
[    5.138732] aess 401f1000.aess: ASoC: Got 0x4ce4 bytes of type 2 version 0 vendor 0 at pass 2
[    5.138763] aess 401f1000.aess: ASoC: Got 0x4094 bytes of type 3 version 0 vendor 0 at pass 3
[    5.138763] aess 401f1000.aess: ASoC: adding 205 DAPM routes
[    5.212585] (stk) :ldisc installation timeout
[    5.216949] (stk) :ldisc_install = 0<3>[    5.244445] aess 401f1000.aess: opp_get_opp_count: device OPP not found (-19)
[    5.288269] ehci-omap 4a064c00.ehci: irq 109, io mem 0x4a064c00
[    5.359313] aess 401f1000.aess: opp: no OPP data
[    5.376647] ata1: SATA link down (SStatus 0 SControl 300)
[    5.408782] ehci-omap 4a064c00.ehci: USB 2.0 started, EHCI 1.00
[    5.417266] aess 401f1000.aess: No OPP definition
[    5.422515] aess 401f1000.aess: DMEM bank at 0xf04c0000
[    5.422515] aess 401f1000.aess: CMEM bank at 0xf04a8000
[    5.422515] aess 401f1000.aess: SMEM bank at 0xf04b0000
[    5.422515] aess 401f1000.aess: PMEM bank at 0xf04ac000
[    5.422546] aess 401f1000.aess: AESS bank at 0xf04a6000
[    5.422546] aess 401f1000.aess: Map 79 items of size 0xc at offset 0x0
[    5.422546] aess 401f1000.aess: Labels 18 at offset 0x3b8
[    5.422576] aess 401f1000.aess: Functions 26 at offset 0x404
[    5.422576] aess 401f1000.aess: Tasks 42 of size 0x4 at offset 0x470
[    5.422576] aess 401f1000.aess: Ports 17 of size 0xe4 at offset 0x51c
[    5.422576] aess 401f1000.aess: Ping pong port at offset 0x1444
[    5.422607] aess 401f1000.aess: DL1 mono mixer at offset 0x1528
[    5.422607] aess 401f1000.aess: DL2 mono mixer at offset 0x1530
[    5.422607] aess 401f1000.aess: AUDUL mixer at offset 0x1538
[    5.422607] aess 401f1000.aess: ASRC at offset 0x1540
[    5.431701] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.438781] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.472290] usb usb1: Product: EHCI Host Controller
[    5.479705] usb usb1: Manufacturer: Linux 3.8.13-gcc16f99 ehci_hcd
[    5.493347] usb usb1: SerialNumber: 4a064c00.ehci
[    5.515411] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> MultiMedia1 mapping ok
[    5.524108] hub 1-0:1.0: USB hub found
[    5.529693] hub 1-0:1.0: 3 ports detected
[    5.537689] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> MultiMedia2 mapping ok
[    5.559204] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> Voice mapping ok
[    5.579406] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> Tones mapping ok
[    5.593841] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> MODEM mapping ok
[    5.611846] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> MultiMedia1 LP mapping ok
[    5.778442] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    5.784484] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
[    5.793609] xhci-hcd xhci-hcd.1.auto: irq 124, io mem 0x4a030000
[    5.799987] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    5.807098] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.814636] usb usb2: Product: xHCI Host Controller
[    5.819702] usb usb2: Manufacturer: Linux 3.8.13-gcc16f99 xhci-hcd
[    5.826232] usb usb2: SerialNumber: xhci-hcd.1.auto
[    5.831970] xHCI xhci_add_endpoint called for root hub
[    5.831970] xHCI xhci_check_bandwidth called for root hub
[    5.832153] hub 2-0:1.0: USB hub found
[    5.836181] hub 2-0:1.0: 1 port detected
[    5.840606] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    5.846557] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[    5.854675] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[    5.861755] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.869293] usb usb3: Product: xHCI Host Controller
[    5.874389] usb usb3: Manufacturer: Linux 3.8.13-gcc16f99 xhci-hcd
[    5.880859] usb usb3: SerialNumber: xhci-hcd.1.auto
[    5.886352] xHCI xhci_add_endpoint called for root hub
[    5.886352] xHCI xhci_check_bandwidth called for root hub
[    5.886535] hub 3-0:1.0: USB hub found
[    5.890441] hub 3-0:1.0: 1 port detected
[    5.894592] usb 1-2: new high-speed USB device number 2 using ehci-omap
[    6.056671] usb 1-2: New USB device found, idVendor=0424, idProduct=3503
[    6.063659] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    6.072052] hub 1-2:1.0: USB hub found
[    6.076049] hub 1-2:1.0: 3 ports detected
[    6.220397] (stk) : timed out waiting for ldisc to be un-installed
[    6.333648] (stk) :ldisc_install = 1<6>[    6.368835] usb 1-3: new high-speed USB device number 3 using ehci-omap
[    6.525726] usb 1-3: New USB device found, idVendor=0424, idProduct=9730
[    6.532775] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    6.544006] smsc95xx v1.0.4
[    6.629272] smsc95xx 1-3:1.0 eth0: register 'smsc95xx' at usb-4a064c00.ehci-3, smsc95xx USB 2.0 Ethernet, ae:f9:f9:e0:3a:07
[    6.634613] omap_i2c 48072000.i2c: controller timed out
[    6.634704] i2c 1-0033: I2C write to TPS6130x failed
[    7.329864] (stk) :ldisc installation timeout
[    7.334289] (stk) :ldisc_install = 0<3>[    7.634521] omap_i2c 48072000.i2c: controller timed out
[    7.640045] i2c 1-0033: I2C write to TPS6130x failed
[    7.645507] omap-abe-twl6040 sound.18:  twl6040-dl1 <-> mcpdm-abe mapping ok
[    7.654785] omap-abe-twl6040 sound.18:  twl6040-ul <-> mcpdm-abe mapping ok
[    7.663818] omap-abe-twl6040 sound.18:  twl6040-dl2 <-> mcpdm-abe mapping ok
[    7.673004] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> 40122000.mcbsp mapping ok
[    7.683135] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> 40124000.mcbsp mapping ok
[    7.694976] omap-abe-twl6040 sound.18:  twl6040-legacy <-> mcpdm-legacy mapping ok
[    7.706420] omap-abe-twl6040 sound.18:  snd-soc-dummy-dai <-> 40124000.mcbsp mapping ok
[    7.723480] input: PandaBoard5 Headset Jack as /devices/sound.18/sound/card1/input0
[    8.337646] (stk) : timed out waiting for ldisc to be un-installed
[    8.451385] (stk) :ldisc_install = 1(stk) :ldisc installation timeout
[    9.457855] (stk) :ldisc_install = 0(stk) : timed out waiting for ldisc to be un-installed
[   10.566772] (stk) :ldisc_install = 1<6>[   11.540344] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[   11.564178] (stk) :ldisc installation timeout
[   11.568572] (stk) :ldisc_install = 0(stk) : timed out waiting for ldisc to be un-installed
[   12.684020] (stk) :ldisc_install = 1(stk) :ldisc installation timeout
[   13.684417] (stk) :ldisc_install = 0<6>[   14.334197] smsc95xx 1-3:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xD1E1
[   14.681365] (stk) : timed out waiting for ldisc to be un-installed
[   14.689697] Bluetooth: st_register failed -22
[  103.677062] omap-dma-engine 4a056000.dma-controller: allocating channel for 101
[  281.445220] omap-dma-engine 4a056000.dma-controller: freeing channel for 101

I find this line interesting, because shortly after it successfully loads the firmware:
Code:
[    4.018218] aess 401f1000.aess: Failed to load firmware 0
 

hns

Well-Known Member
Joined
Dec 4, 2011
Messages
636
Location
Oberhaching
I finally got a free evening to try the GLSDK 6.03.00.01 "reference build" I did earlier this month, and I think I got the AESS working on Linux-3.8. I was playing back 44.1 kHz wav file with 98% idle.

I had to setup the audio path with amixer, as described here and copied below for future reference:
Code:
  amixer cset -c 1 name='Headset Left Playback' 1
  amixer cset -c 1 name='Headset Right Playback' 1
  amixer cset -c 1 name='Headset Playback Volume' 12
  amixer cset -c 1 name='DL1 PDM Switch' 1
  amixer cset -c 1 name='Sidetone Mixer Playback' 1
  amixer cset -c 1 name='SDT DL Volume' 120
  amixer cset -c 1 name='DL1 Mixer Multimedia' 1
  amixer cset -c 1 name='DL1 Media Playback Volume' 110
  amixer sset -c 1 'Analog Left',0 'Aux/FM Left'
  amixer sset -c 1 'Analog Right',0 'Aux/FM Right'
  amixer sset -c 1 'Aux FM',0 7
  amixer sset -c 1 'AUDUL Media',0 149
  amixer sset -c 1 'Capture',0 4
  amixer sset -c 1 MUX_UL00,0 AMic0
  amixer sset -c 1 MUX_UL01,0 AMic1
  amixer sset -c 1 'AMIC UL',0 120

Let me know if anyone want more info or maybe SD card image

Great!!!

I may find some time over the weekend for my (modern) AESS setup and some part of the issues may be the amixer settings, for example 'AUDUL Media'. At least I may find another starting point for debugging.

Thanks for this puzzle piece.
 

Risca

Very Active Member
Joined
Sep 25, 2011
Messages
109
Great!!!

I may find some time over the weekend for my (modern) AESS setup and some part of the issues may be the amixer settings, for example 'AUDUL Media'. At least I may find another starting point for debugging.

Thanks for this puzzle piece.
Happy to help! :D

Unfortunately, I'm fully booked this weekend, or I would try to help out :)
 
Top