linux-arm-kernel.lists.infradead.org archive mirror
 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 12:16:40 +0200	[thread overview]
Message-ID: <20120717121640.589780ce@skate> (raw)
In-Reply-To: <201207161554.04812.arnd@arndb.de>

Le Mon, 16 Jul 2012 15:54:04 +0000,
Arnd Bergmann <arnd@arndb.de> a ?crit :

> > +void mcs814x_restart(char mode, const char *cmd)
> > +{
> > +	__raw_writel(~(1 << 31), mcs814x_sysdbg_base);
> > +}
> 
> You should generally avoid using __raw_readl etc. and instead use
> readl/write or readl_relaxed/writel_relaxed.

I thought that readl/writel and readl_relaxed/writel_relaxed were used
for PCI-style access, for which these macros/functions do automatically
a conversion from the CPU-endianness to the PCI-endianness
(little-endian). Here of course, this the SoC is used little-endian, it
will just work because readl/writel will not do any endianness
conversion, but if we were on a big-endian machine?

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?

Best regards,

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

  parent reply	other threads:[~2012-07-17 10:16 UTC|newest]

Thread overview: 40+ 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 ` [PATCH 1/8] " Florian Fainelli
2012-07-16 12:29   ` Thomas Petazzoni
2012-07-16 12:43     ` Florian Fainelli
2012-07-16 15:55       ` Arnd Bergmann
2012-07-16 17:57       ` Nicolas Pitre
2012-07-23 19:11     ` Florian Fainelli
2012-07-27 22:42       ` Linus Walleij
2012-07-16 15:54   ` Arnd Bergmann
2012-07-16 20:47     ` Turquette, Mike
2012-07-17  9:41       ` Florian Fainelli
2012-07-17 10:47       ` Florian Fainelli
2012-07-16 22:12     ` Linus Walleij
2012-07-17  9:35       ` Florian Fainelli
2012-07-17  9:34     ` Florian Fainelli
2012-07-17 13:07       ` Arnd Bergmann
2012-07-17 13:32         ` Florian Fainelli
2012-07-17 13:45           ` Arnd Bergmann
2012-07-17 10:16     ` Thomas Petazzoni [this message]
2012-07-17 13:12       ` Arnd Bergmann
2012-07-17 13:28         ` Thomas Petazzoni
2012-07-17 13:51           ` Arnd Bergmann
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-17 13:19   ` Arnd Bergmann
2012-07-17 13:34     ` Florian Fainelli
2012-07-17 13:53       ` Arnd Bergmann
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-17 13:24   ` Arnd Bergmann
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-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 ` [PATCH 6/8] ARM: MCS814x: provide a sample defconfig file 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 ` [PATCH 8/8] ARM: MSC814x: add MAINTAINERS entry Florian Fainelli
2012-07-15 19:59 ` [PATCH 0/8] ARM: support for Moschip MCS814x SoCs Arnd Bergmann
2012-07-16  8:16   ` Florian Fainelli
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=20120717121640.589780ce@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 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).