All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] mxs: generalize code for print_cpuinfo()
Date: Sun, 17 Jun 2012 19:56:16 +0200	[thread overview]
Message-ID: <4FDE1A40.40008@denx.de> (raw)
In-Reply-To: <201206171802.49354.marex@denx.de>

On 17/06/2012 18:02, Marek Vasut wrote:

>> I like that there will be support for i.MX23, too. But I dislike that
>> everything takes the name "MX28". As you suggest in your subject, maybe
>> it is time to rename directories, and use "mxs" (as in kernel) instead
>> of mx28.
> 
> We can do that eventually, later ... it depends on the ordering of Otavio's 
> patches, I'm fine either way.

Fine with me - anyway, it is something must be done.

> 
>>> +
>>> +static u8 get_cpu_rev(void)
>>> +{
>>> +	struct mx28_digctl_regs *digctl_regs =
>>> +		(struct mx28_digctl_regs *)MXS_DIGCTL_BASE;
>>> +
>>> +	return readl(&digctl_regs->hw_digctl_chipid) & 0x0000F;
>>> +}
>>
>> Everywhere (i.MX, omap, ...) get_cpu_rev returns u32. The function is
>> currently exported, too.
> 
> Correct, but isn't the return value mangled somehow (like having major rev. << 
> 16 and minor rev. << 0 )? Or that's only IMX?

Checking in current implementations for get_cpu_rev() (i.MX / OMAP24 /
OMAP3 / AM33, and even board/apollon/sys_info.c: I do not know why the
cpu detection is inseide this file), none of them requires strictly 32
bit. However, we should be coherent in all code - for this reason I
dislike if one of the i.MX is implemented differently as for other SOCs.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

  reply	other threads:[~2012-06-17 17:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 12:58 [U-Boot] [PATCH 0/3] i.MX refactoring patchset Otavio Salvador
2012-06-17 12:58 ` [U-Boot] [PATCH 1/3] imx: Use a clear identification of an unidentified CPU type Otavio Salvador
2012-06-17 13:05   ` Fabio Estevam
2012-06-17 13:09     ` Otavio Salvador
2012-06-17 13:13       ` Fabio Estevam
2012-06-17 13:21         ` Otavio Salvador
2012-06-17 13:30         ` Marek Vasut
2012-06-17 15:43   ` Stefano Babic
2012-06-17 15:48     ` Otavio Salvador
2012-06-17 16:03       ` Marek Vasut
2012-06-17 17:50         ` Otavio Salvador
2012-06-17 18:04           ` Stefano Babic
2012-06-17 18:40             ` Marek Vasut
2012-06-17 18:04           ` Marek Vasut
2012-06-17 12:58 ` [U-Boot] [PATCH 2/3] mxs: generalize code for print_cpuinfo() Otavio Salvador
2012-06-17 13:10   ` Fabio Estevam
2012-06-17 13:25   ` Fabio Estevam
2012-06-17 13:35     ` Marek Vasut
2012-06-17 14:14       ` Fabio Estevam
2012-06-17 14:35     ` Otavio Salvador
2012-06-17 15:10       ` Marek Vasut
2012-06-17 15:17         ` Otavio Salvador
2012-06-17 13:28   ` Marek Vasut
2012-06-17 15:49   ` Stefano Babic
2012-06-17 16:02     ` Marek Vasut
2012-06-17 17:56       ` Stefano Babic [this message]
2012-06-17 18:03         ` Otavio Salvador
2012-06-17 18:41           ` Marek Vasut
2012-06-17 18:04         ` Marek Vasut
2012-06-17 17:49     ` Otavio Salvador
2012-06-17 12:58 ` [U-Boot] [PATCH 3/3] mx28evk: extend default environment Otavio Salvador
2012-06-17 21:54 ` [U-Boot] [PATCH 0/3] i.MX refactoring patchset Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FDE1A40.40008@denx.de \
    --to=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.