Re: Regressions for older OMAP3503 silicon

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 5, 2011 at 11:09 AM, Paul Walmsley <paul@xxxxxxxxx> wrote:

> Looking at the 2.6.39 kernel sources, those messages are coming from
> mach-omap2/pm34xx.c:omap3_enable_io_chain().  That means that something is
> seriously wrong since that code should only be executing on ES3.1 chips
> and higher.
>
> Could you put something similar to a
>
> pr_err("** omap_rev is %08x\n", omap_rev());
>
> in your pm34xx.c right above the #if 0 that you added and let us know what
> it says?

I think that what is seriously wrong is the way that the revision test is done:

	if (omap_rev() >= OMAP3430_REV_ES3_1) {

For 3505 ES2.1 omap_rev() returns 35030234 and it is being compared to 34300434.

This sort of revision check really should be looking at cpu type and
revision.  I suspect there are a number of other similar tests in the
kernel that have this issue.

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux