All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] ARM: support for Moschip MCS814x SoCs
Date: Tue, 17 Jul 2012 15:28:26 +0200	[thread overview]
Message-ID: <20120717152826.2bf75948@skate> (raw)
In-Reply-To: <201207171312.06987.arnd@arndb.de>

Hello,

Thanks a lot for those details.

Le Tue, 17 Jul 2012 13:12:06 +0000,
Arnd Bergmann <arnd@arndb.de> a ?crit :

> > My understanding until now was that __raw_readl/__raw_writel should
> > be used for accesses with native endianness, but apparently, it's
> > more subtle than this. Would you mind expanding a bit on this?
> 
> The __raw_* versions are basically only valid if you access a memory
> buffer, such as a video framebuffer. They do the conversion of an
> __iomem pointer into something that can be accessed by the compiler.
> 
> The non-raw versions have fixed endianess, guarantee that the access
> is done atomically (could be byte-wise otherwise) and that all the
> necessary barriers are used to synchronize against DMA and
> out-of-order execution.
> 
> We don't actually have accessors that are CPU-endian and guarantee
> that you can access an MMIO register properly.
> 
> On powerpc, the convention is that readl/writel should only be used
> to access PCI, but that is for the enhanced error handling, not for
> endianess.

And then, on PowerPC, which accessors do you use to access
SoC-peripherals that are not on the PCI bus?

For example, drivers/tty/serial/mpsc.c uses writel/readl, so a
conversion to/from little-endian is done when writing/reading
registers. Are those memory-mapped devices little-endian even though
they are used on big-endian PowerPCs?

I apologize for the silly questions, but I'm trying to make some sense
out of these numerous I/O and memory accessors.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mike Turquette <mturquette@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Florian Fainelli <florian@openwrt.org>,
	olof@lixom.net, devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/8] ARM: support for Moschip MCS814x SoCs
Date: Tue, 17 Jul 2012 15:28:26 +0200	[thread overview]
Message-ID: <20120717152826.2bf75948@skate> (raw)
In-Reply-To: <201207171312.06987.arnd@arndb.de>

Hello,

Thanks a lot for those details.

Le Tue, 17 Jul 2012 13:12:06 +0000,
Arnd Bergmann <arnd@arndb.de> a écrit :

> > My understanding until now was that __raw_readl/__raw_writel should
> > be used for accesses with native endianness, but apparently, it's
> > more subtle than this. Would you mind expanding a bit on this?
> 
> The __raw_* versions are basically only valid if you access a memory
> buffer, such as a video framebuffer. They do the conversion of an
> __iomem pointer into something that can be accessed by the compiler.
> 
> The non-raw versions have fixed endianess, guarantee that the access
> is done atomically (could be byte-wise otherwise) and that all the
> necessary barriers are used to synchronize against DMA and
> out-of-order execution.
> 
> We don't actually have accessors that are CPU-endian and guarantee
> that you can access an MMIO register properly.
> 
> On powerpc, the convention is that readl/writel should only be used
> to access PCI, but that is for the enhanced error handling, not for
> endianess.

And then, on PowerPC, which accessors do you use to access
SoC-peripherals that are not on the PCI bus?

For example, drivers/tty/serial/mpsc.c uses writel/readl, so a
conversion to/from little-endian is done when writing/reading
registers. Are those memory-mapped devices little-endian even though
they are used on big-endian PowerPCs?

I apologize for the silly questions, but I'm trying to make some sense
out of these numerous I/O and memory accessors.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2012-07-17 13:28 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 14:49 [PATCH 0/8] ARM: support for Moschip MCS814x SoCs Florian Fainelli
2012-07-15 14:49 ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 1/8] " Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-16 12:29   ` Thomas Petazzoni
2012-07-16 12:29     ` Thomas Petazzoni
2012-07-16 12:43     ` Florian Fainelli
2012-07-16 12:43       ` Florian Fainelli
2012-07-16 15:55       ` Arnd Bergmann
2012-07-16 15:55         ` Arnd Bergmann
2012-07-16 17:57       ` Nicolas Pitre
2012-07-16 17:57         ` Nicolas Pitre
2012-07-23 19:11     ` Florian Fainelli
2012-07-23 19:11       ` Florian Fainelli
2012-07-27 22:42       ` Linus Walleij
2012-07-27 22:42         ` Linus Walleij
2012-07-16 15:54   ` Arnd Bergmann
2012-07-16 15:54     ` Arnd Bergmann
2012-07-16 20:47     ` Turquette, Mike
2012-07-16 20:47       ` Turquette, Mike
2012-07-17  9:41       ` Florian Fainelli
2012-07-17  9:41         ` Florian Fainelli
2012-07-17 10:47       ` Florian Fainelli
2012-07-17 10:47         ` Florian Fainelli
2012-07-16 22:12     ` Linus Walleij
2012-07-16 22:12       ` Linus Walleij
2012-07-17  9:35       ` Florian Fainelli
2012-07-17  9:35         ` Florian Fainelli
2012-07-17  9:34     ` Florian Fainelli
2012-07-17  9:34       ` Florian Fainelli
2012-07-17 13:07       ` Arnd Bergmann
2012-07-17 13:07         ` Arnd Bergmann
2012-07-17 13:32         ` Florian Fainelli
2012-07-17 13:32           ` Florian Fainelli
2012-07-17 13:45           ` Arnd Bergmann
2012-07-17 13:45             ` Arnd Bergmann
2012-07-17 10:16     ` Thomas Petazzoni
2012-07-17 10:16       ` Thomas Petazzoni
2012-07-17 13:12       ` Arnd Bergmann
2012-07-17 13:12         ` Arnd Bergmann
2012-07-17 13:28         ` Thomas Petazzoni [this message]
2012-07-17 13:28           ` Thomas Petazzoni
2012-07-17 13:51           ` Arnd Bergmann
2012-07-17 13:51             ` Arnd Bergmann
2012-07-16 22:06   ` Linus Walleij
2012-07-16 22:06     ` Linus Walleij
2012-07-15 14:49 ` [PATCH 2/8] ARM: MCS814x: add Device Tree based MCS8140 board support Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-17 13:19   ` Arnd Bergmann
2012-07-17 13:19     ` Arnd Bergmann
2012-07-17 13:34     ` Florian Fainelli
2012-07-17 13:34       ` Florian Fainelli
2012-07-17 13:53       ` Arnd Bergmann
2012-07-17 13:53         ` Arnd Bergmann
2012-07-17 13:57         ` Florian Fainelli
2012-07-17 13:57           ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 3/8] ARM: MCS814x: add Device Tree bindings documentation Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-17 13:24   ` Arnd Bergmann
2012-07-17 13:24     ` Arnd Bergmann
2012-07-17 13:35     ` Florian Fainelli
2012-07-17 13:35       ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 4/8] ARM: MCS814X: add DTS file for Tigal/Robotech RBT-832 Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-17 13:27   ` Arnd Bergmann
2012-07-17 13:27     ` Arnd Bergmann
2012-07-15 14:49 ` [PATCH 5/8] ARM: MCS814x: add DTS file for Devolo dLAN USB Extender Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 6/8] ARM: MCS814x: provide a sample defconfig file Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 7/8] ARM: MSC814X: add Kconfig and Makefile to arch/arm Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-15 14:49 ` [PATCH 8/8] ARM: MSC814x: add MAINTAINERS entry Florian Fainelli
2012-07-15 14:49   ` Florian Fainelli
2012-07-15 19:59 ` [PATCH 0/8] ARM: support for Moschip MCS814x SoCs Arnd Bergmann
2012-07-15 19:59   ` Arnd Bergmann
2012-07-16  8:16   ` Florian Fainelli
2012-07-16  8:16     ` Florian Fainelli
2012-07-16 18:09   ` Nicolas Pitre
2012-07-16 18:09     ` Nicolas Pitre

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=20120717152826.2bf75948@skate \
    --to=thomas.petazzoni@free-electrons.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 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.