From: Rob Herring <robh@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Brown <broonie@kernel.org>, Xiubo Li <Li.Xiubo@nxp.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: fix documentation to match code
Date: Mon, 21 Mar 2016 08:14:28 -0500 [thread overview]
Message-ID: <20160321131428.GA28046@rob-hp-laptop> (raw)
In-Reply-To: <1458235427-3856540-1-git-send-email-arnd@arndb.de>
On Thu, Mar 17, 2016 at 06:23:40PM +0100, Arnd Bergmann wrote:
> The regmap binding talks about one thing, which is register
> endianess, and it gets almost every aspect of it wrong.
>
> This replaces the current text of the file with a version
> that makes more sense and that matches what we implement
> now.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: a06c488da0b0 ("regmap: Add explict native endian flag to DT bindings")
> Fixes: 275876e208e2 ("regmap: Add the DT binding documentation for endianness")
[...]
> +Note:
> +Regmap defaults to little-endian register access on MMIO based
> +devices, this is by far the most common setting. On CPU
This seems a bit Linux specific to me, but I guess if we are defining
the binding to be this way it is fine.
Acked-by: Rob Herring <robh@kernel.org>
> +architectures that typically run big-endian operating systems
> +(e.g. PowerPC), registers can be defined as big-endian and must
> +be marked that way in the devicetree.
prev parent reply other threads:[~2016-03-21 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 17:23 [PATCH] regmap: fix documentation to match code Arnd Bergmann
2016-03-17 17:40 ` Mark Brown
2016-03-18 10:58 ` Applied "regmap: fix documentation to match code" to the regmap tree Mark Brown
2016-03-21 13:14 ` Rob Herring [this message]
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=20160321131428.GA28046@rob-hp-laptop \
--to=robh@kernel.org \
--cc=Li.Xiubo@nxp.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
/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