From: schen@mvista.com (Steve Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM1176 register writes are in reverse?
Date: Tue, 06 Oct 2009 07:56:14 -0500 [thread overview]
Message-ID: <1254833774.3153.52.camel@linux-1lbu> (raw)
In-Reply-To: <b9e8fcbd0910060510y3dd9ea36x6c97db47f0dfc886@mail.gmail.com>
On Tue, 2009-10-06 at 17:40 +0530, Nicholas Van Orton wrote:
> Hi,
>
> I noticed that register writes to ARM1176 need to be in the reverse
> order. That is, lets say I need to write 0xABCD to a register. But in
> the actual write using __raw_writel() the value needs to be changed to
> 0xCDAB. Why is this so? The Davinci or OMAP on the other hand for
> example, which is an ARM 926 does not need any such manipulation. Why
> is the ARM1176 an exception?
>
Are you working with TI Puma5? I suspect that reverse order is probably
due to specific hardware endianness implementation rather than generic
difference between ARM1176 and ARM926.
Regards,
Steve
next prev parent reply other threads:[~2009-10-06 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 12:10 ARM1176 register writes are in reverse? Nicholas Van Orton
2009-10-06 12:56 ` Steve Chen [this message]
2009-10-06 13:12 ` Ben Dooks
2009-10-06 13:28 ` Nicholas Van Orton
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=1254833774.3153.52.camel@linux-1lbu \
--to=schen@mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).