OMAP4 eMMC support is missing

Bug #867650 reported by John Rigby
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
u-boot-linaro (Ubuntu)
Fix Released
High
John Rigby
Nominated for Oneiric by Ricardo Salveti

Bug Description

Two upstream patches that allow eMMC to work on blaze are missing in u-boot-linaro

SRU Info:

This bug affects all blaze platforms.

Test case is to boot a blaze board and see if eMMC i detected.

The fix is in upstream git.linaro.org (comment #3). This fix has been tested and shown to fix the problem with no regressions (comments #5, #6, #7).

Revision history for this message
John Rigby (jcrigby) wrote :

From Sebastien Jan:

These 2 patches from the linaro u-boot 2011.08 branch were not imported into
the 2011.09 branch, resulting in missing eMMC support in this branch.

I rebased them on top of 2011.09 branch.
I have built and boot-tested them on omap4 blaze, checking eMMC was visible
from kernel with these patches, and boot-tested on panda 4460.
(side note: cross-compiling using 4.6.1 Linaro u-boot fails with a 'compiler
internal error'. I can log a defect on the toolchain for that if you wish.
Cross-compiling with 4.5* works fine - this is what I tested with)

Revision history for this message
John Rigby (jcrigby) wrote :
summary: - eMMC support is missing
+ OMAP4 eMMC support is missing
Revision history for this message
John Rigby (jcrigby) wrote :
Revision history for this message
John Rigby (jcrigby) wrote :
Revision history for this message
Sebastien JAN (sebjan) wrote :

Boot tested the sdp4430 version (panda does not have an eMMC): https://code.launchpad.net/~linaro-maintainers/+archive/staging-overlay/+files/u-boot-linaro-omap4-sdp4430_2011.09%2B5362%2B35%2B201110042126~oneiric1_armel.deb

Verified that eMMC is visible from within the kernel after the boot.

Revision history for this message
John Rigby (jcrigby) wrote :

Tested with latest linaro kernel and nano rootfs on both panda and beagle-xM

Revision history for this message
John Rigby (jcrigby) wrote :

Note: the previous testing was checking for regressions.

John Rigby (jcrigby)
description: updated
Revision history for this message
John Rigby (jcrigby) wrote :
Revision history for this message
John Rigby (jcrigby) wrote :

uploaded u-boot-linaro_2011.09.6-0ubuntu1 to oneiric-proposed

Revision history for this message
John Rigby (jcrigby) wrote :

I see not "Nominate for series" here so not sure what to do next.

John Rigby (jcrigby)
Changed in u-boot-linaro (Ubuntu):
assignee: nobody → John Rigby (jcrigby)
Changed in u-boot-linaro (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package u-boot-linaro - 2011.09.6-0ubuntu1

---------------
u-boot-linaro (2011.09.6-0ubuntu1) oneiric; urgency=low

  * omap4: reduce default operating point for 4460 devices
    Reduce the operating point for 4460 to OPP100 (MPU at 700MHz)
    (LP: #867670)
      From bug report:
        With both A9 cores loaded 4460 reaches max temperature in about 30s at the
        current operating point of 930MHz. The operating point should be lowered to
        700MHz.
        It appears the panda heats more than I thought (and much more that the blaze),
        and by loading the 2 cores I can quite easily reach max temperature at 920MHz
        (it takes around 30s on my board!).
        At 700MHz, the temperature still increases but much slower. So if the A9 cores
        do not run at 100% all the time we shall be ok.
        So for now, we definitely need this change if we don't want to run with a
        heatsink...
  * mmc: omap: enable high capacity
      Enable high capacity to host capability.
      Fixes eMMC detection on boot from MMC/SD card.
    mmc: omap: config VMMC, MMC1_PBIAS
      Config VMMC voltage to 3V for MMC/SD card slot
      and PBIAS settings needed for OMAP4
    (LP: #867650)
 -- John Rigby <email address hidden> Wed, 05 Oct 2011 17:17:34 -0600

Changed in u-boot-linaro (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.