[U-Boot] [PATCH] mx6: Fix the reading of CPU revision

[Fabio Estevam]

Hi Dirk,

On Tue, Mar 26, 2013 at 12:43 PM, Dirk Behme <dirk.behme at de.bosch.com> wrote:
> Hi Fabio,
>
>
> On 26.03.2013 13:54, Fabio Estevam wrote:
>>
>> Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx,
>> which
>> is an invalid mx6 CPU revision.
>
>
> Do you have somewhere a list of valid CPU revisions? From two points of
> view:
>
> a) the i.MX6 hardware spec
>
> b) the VPU library

Sorry, I don't. I am basing the CPU revision numbers from FSL U-boot:
http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/tree/board/freescale/common/fsl_sys_rev.c?h=imx_v2009.08_3.0.0

Adding Jason, in case he could clarify it.

> You remove Troy's code here introduced with
>
> http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=commitdiff;h=20332a066aff98f39419495821e14edd10b2a3f8
>
> Troy's detection you remove here intentionally distinguishes between
> DualLite and Solo. You now re-introduce a common DL_S, again.
>
> Additionally, you completely seem to drop checking for scu->config. I've
> already seen some (broken?) i.MX6Solo where this check was essential.
>
> I can't talk about the "problems when trying to use VPU library in the
> kernel" (btw, which problems?) and the invalid 0x62xxx, but we used Troy's
> version of the detection successfully.

Passing 0x62xxx as cpu_rev on a mx6solo caused the VPU issues described here:
https://community.freescale.com/thread/305396

Which cpu_rev value is returned with your mx6solo? Are you able to use VPU lib?

I will test solo lite when I have chance to add support for it.

Regards,

Fabio Estevam