From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shinya Kuribayashi <skuribay@pobox.com>
Date: Sun, 13 Feb 2011 23:41:29 +0900
Subject: [U-Boot] in/out_le32, etc.
In-Reply-To: <201102120323.59395.Aaron.Williams@caviumnetworks.com>
References: <201102120323.59395.Aaron.Williams@caviumnetworks.com>
Message-ID: <4D57ED99.4040003@pobox.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 02/12/2011 08:23 PM, Aaron Williams wrote:
> There's in_xxx/out_xxx, __raw_readx/__raw_writex and readx/writex.  What 
> exactly is the difference between all of these?  It looks like the in/out was 
> added recently and is not present in the mips io.h file.

In the MIPS code, 'mips_io_port_base' makes in_xxx/out_xxx distinct
from readx/writex.  And raw operations are never swapped in software.
Check <asm/io.h> for more details.

> For example, on our platform the PCI BAR address space is mapped to different 
> 64-bit address spaces depending on the bus number. It would be very helpful if 
> different macros were used for different I/O devices. For example, one set of 
> macros for accessing PCI BAR address space.