mx31moboard for 2.6.33-rc1
Get series with b4
b4 am 1261407604.2144.16.camel@climbing-albyVersions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] mx31moboard for 2.6.33-rc1
Il giorno lun, 21/12/2009 alle 12.17 +0100, Sascha Hauer ha scritto:
Quoted 11 lines · Valentin Longchamp
Quoted 9 lines
I have tested mx31moboard with the first -rc. Here are two patches correcting the current problems. They should go to a next -rc.
1) The patches for usbh support were based on the bad branch, where the
platform_deviceshad been renamed. Now this prevents the mx3 config to build. The first patch reverts to the correct names.2) The MC13783 voltage regulators with
boot_onoralways_onenabled hang the kernel at boot. Remove these options from mx31moboard configuration. Sascha, is this a correct behavior or is it a bug ?
Quoted 6 lines
AFAIK the
boot_onindicate the regulator framework that this regulator is already enabled when the kernel starts. I don't see why this makes the kernel hang. Can you do a bit more debugging please?Sascha
The patch that I proposed:
[PATCH 2/4] mfd: mc13783: When probing, unlock the mc13783 before subsystems initialisation. solve the problem I think.
If you enable the debug output on drivers/mfd/mc13783-core and you see that the kernel hang on the mc13783 waiting queue, than my patch is for you.
With boot_on = 1 the regulator core ensure also that the regulator is enabled during probe, so it call the corresponding enable function. That function utilise the mc13783-API that are still locked.
mc13783-regulator now is probed when mc13783-core register it's regulator subsystem.
For now that patch (acked by Uwe Kleine-K?nig) is not applied to the mfd tree.
Alberto!