Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1361817
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] regmap: fix documentation to match code |
| Date | 2016-03-21 14:20 +0100 |
| Message-ID | <rf7Ut-6aS-13@gated-at.bofh.it> (permalink) |
| References | <rdJUe-1ST-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] regmap: fix documentation to match code Arnd Bergmann <arnd@arndb.de> - 2016-03-17 18:30 +0100 Re: [PATCH] regmap: fix documentation to match code Mark Brown <broonie@kernel.org> - 2016-03-17 18:50 +0100 Applied "regmap: fix documentation to match code" to the regmap tree Mark Brown <broonie@kernel.org> - 2016-03-18 12:00 +0100 Re: [PATCH] regmap: fix documentation to match code Rob Herring <robh@kernel.org> - 2016-03-21 14:20 +0100
csiph-web