Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [v6, 3/5] dt: move guts devicetree doc out of powerpc directory
Date: Thu, 17 Mar 2016 12:06:40 -0500	[thread overview]
Message-ID: <20160317170640.GB21009@rob-hp-laptop> (raw)
In-Reply-To: <1457518131-11339-4-git-send-email-yangbo.lu@nxp.com>

On Wed, Mar 09, 2016 at 06:08:49PM +0800, Yangbo Lu wrote:
> Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
> since it's used by not only PowerPC but also ARM. And add a specification
> for 'little-endian' property.
> 
> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
> ---
> Changes for v2:
> 	- None
> Changes for v3:
> 	- None
> Changes for v4:
> 	- Added this patch
> Changes for v5:
> 	- Modified the description for little-endian property
> Changes for v6:
> 	- None
> ---
>  Documentation/devicetree/bindings/{powerpc => soc}/fsl/guts.txt | 3 +++
>  1 file changed, 3 insertions(+)
>  rename Documentation/devicetree/bindings/{powerpc => soc}/fsl/guts.txt (91%)
> 
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/guts.txt b/Documentation/devicetree/bindings/soc/fsl/guts.txt
> similarity index 91%
> rename from Documentation/devicetree/bindings/powerpc/fsl/guts.txt
> rename to Documentation/devicetree/bindings/soc/fsl/guts.txt
> index b71b203..07adca9 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/guts.txt
> +++ b/Documentation/devicetree/bindings/soc/fsl/guts.txt
> @@ -25,6 +25,9 @@ Recommended properties:
>   - fsl,liodn-bits : Indicates the number of defined bits in the LIODN
>     registers, for those SOCs that have a PAMU device.
>  
> + - little-endian : Indicates that the global utilities block is little
> +   endian. The default is big endian.

The default is "the native endianness of the system". So absence on an 
ARM system would be LE. This property is valid for any simple-bus 
device, so it isn't really required to document per device. You can, but 
your description had better match the documented behaviour.

Rob

  reply	other threads:[~2016-03-17 17:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 10:08 [v6, 0/5] Fix eSDHC host version register bug Yangbo Lu
2016-03-09 10:08 ` [v6, 1/5] ARM64: dts: ls2080a: add device configuration node Yangbo Lu
2016-03-09 10:08 ` [v6, 2/5] soc: fsl: add GUTS driver for QorIQ platforms Yangbo Lu
2016-03-18 22:54   ` Scott Wood
2016-03-25  6:44     ` Yangbo Lu
2016-03-09 10:08 ` [v6, 3/5] dt: move guts devicetree doc out of powerpc directory Yangbo Lu
2016-03-17 17:06   ` Rob Herring [this message]
2016-03-17 17:11     ` Arnd Bergmann
2016-03-17 17:57       ` Rob Herring
2016-03-17 21:33         ` Leo Li
2016-03-18 18:16     ` Scott Wood
2016-03-25  6:38       ` Yangbo Lu
2016-03-09 10:08 ` [v6, 4/5] powerpc/fsl: move mpc85xx.h to include/linux/fsl Yangbo Lu
2016-03-12 15:52   ` Wolfram Sang
2016-03-09 10:08 ` [v6, 5/5] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0 Yangbo Lu
2016-03-13 22:26   ` Arnd Bergmann
2016-03-14  7:29     ` Yangbo Lu
2016-03-14 17:45       ` Scott Wood
2016-03-17 17:01         ` Rob Herring
2016-03-17 17:06           ` Arnd Bergmann
2016-03-18 18:28             ` Scott Wood
2016-03-25  6:43               ` Yangbo Lu

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=20160317170640.GB21009@rob-hp-laptop \
    --to=robh@kernel.org \
    --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