update 2010-10-08 This information is fairly out of date.


I'm just writing this post so we have some kind of centralized knowledge of those who have the Efika MX board. A wiki would be nice, so everyone could edit and add their stuff, but meanwhile i believe this is enough.

Poweroff/reboot issues
kernel 2.6.28
-reboot works fine
-power off works fine, but after powering it off, you need to unplug and plug the power cord in case you want to power it on again.
kernel 2.6.31
-reboot does a poweroff, which has the same problem as 2.6.28(the power cord removal thing)
-poweroff does a reboot!!!

Sound
-Works, you need to load the snd-soc-imx-3stack-sgtl5000 module.

Wi-Fi
-The Efika MX v3 board has a RT3070USB wireless card. The 2.6.31 kernel includes the RT2870USB driver, which seems to detect the RT3070USB card in the Efika, yet it doesn't work(it doesn't associate to any AP). You need to download the firmware for it @ Ralink web page and put the rt2870.bin inside that tarball in /lib/firmware.

LEDs in u-boot
You can play with the led on the power button under u-boot with the following commands:
'led 0 on' = blue
'led 1 on' = green
'led 2 on' = red
For turning it off, just use 'led {0,1,2} off' or 'led off'

Feel free to correct me or if you think i'm missing something, i'll add it.

Not sure what causes this, the actual poweroff code is identical in both kernels.
It's built-in by default on the 2.6.31 kernel because it doesn't seem to register itself on the 2.6.31 kernel properly. We actually fixed this in the Ubuntu kernel but we're not sure why the regression occurred. Maybe a change in ALSA SoC again..
You may have better luck with the RT3070STA driver from the same website. I can associate the in-kernel driver with an AP here; it is just wildly unreliable and doesn't associate with some AES access points (even with the same encryption methods!), and no WEP ones.

We're still working on this but the driver in 2.6.32 and 2.6-next require way too many changes to backport.


For Bluetooth; systems are shipping without Bluetooth right now. We have spare modules if you're desperate for it for a project. They cost us about $18 a unit and it would have pushed the price of the systems up. You can buy a tiny USB Bluetooth dongle for $2.50 from a lot of places like DealExtreme with free shipping.. may as well get a powered hub from there and some dirt cheap SD cards if you're buying things to make your Efika MX even more useful :)

_________________
Matt Sealey

Expanding on your led control for those of us playing at home, here's a quick reference table for all possible color combinations:

000 - Off
001 - Blue
010 - Green
011 - Light Blue
100 - Red
101 - Purple
110 - Yellow
111 - White

I did notice that led off does not work to turn off all LEDs, and I am having to turn them all off individually.

Have you opened up your MX case to determine which PMIC is in this design? I'm wondering if there's any PWM control over the LED output?

Not verified this yet, but it looks like the PMIC is more than likely the MC13892. Not sure why there's no public register list for this IC; I've yet to come across anything on the Freescale website. There is full driver support in the BSP.

It is the MC13892 "Atlas" PMIC version 2.0A.

Note; Freescale aren't ready to ship docs as there are parts which they cannot release. This all has to go through legal (as you know :) - the MC13783 for example has a documentation for "GPL drivers" and then a private set of docs for board designers and people with NDAs.

Note that there is VERY VERY little reason to touch the PMIC at all within Linux. It's all done and correct for you. If porting another operating system, from U-Boot or Aura, most of it is already set up for you too. We hope to completely encapsulate PMIC operation (i.e. you don't even need to know there is a PMIC) in Aura.
:)

As for the LEDs they're controlled by 3 GPIO lines and not by the PMIC. I am not sure why they are not connected to the funlights controller in the PMIC (probably because at the time the funlights controller had no Linux driver) but, they are not.

You can find the correct GPIO pins to use in the Linux source code, look for WLAN_LED_PIN or some such define and it'll give you the IOMUX pin number.

_________________
Matt Sealey

Quick LED hack is here, it doesn't work but it does compile. Since Christmas is popping up, I might not work on it so much as I could/should the next couple of days but if you get bored, any obvious bugs/mistakes or comments would be awesome.

_________________
Matt Sealey

LED hack works if you gpio_free the pins before registering the platform driver :)

_________________
Matt Sealey