dt-bindings: fix spelling, typos, grammar, duplicated words

      the connection between the motherboard and any tiles. Sometimes the

      compatible is placed directly under this node, sometimes it is placed

      in a subnode named "motherboard-bus". Sometimes the compatible includes

      "arm,vexpress,v2?-p1" sometimes (on software models) is is just

      "arm,vexpress,v2?-p1" sometimes (on software models) it is just

      "simple-bus". If the compatible is placed in the "motherboard-bus" node,

      it is stricter and always has two compatibles.

    type: object

#

# For multiple 'if' schema, group them under an 'allOf'.

#

# If the conditionals become too unweldy, then it may be better to just split

# If the conditionals become too unwieldy, then it may be better to just split

# the binding into separate schema documents.

allOf:

  - if:

		     <&gpio1 15 0>;

In the above example, &gpio1 uses 2 cells to specify a gpio. The first cell is

a local offset to the GPIO line and the second cell represent consumer flags,

such as if the consumer desire the line to be active low (inverted) or open

a local offset to the GPIO line and the second cell represents consumer flags,

such as if the consumer desires the line to be active low (inverted) or open

drain. This is the recommended practice.

The exact meaning of each specifier cell is controller specific, and must be

Optional standard bitfield specifiers for the last cell:

- Bit 0: 0 means active high, 1 means active low

- Bit 1: 0 mean push-pull wiring, see:

- Bit 1: 0 means push-pull wiring, see:

           https://en.wikipedia.org/wiki/Push-pull_output

         1 means single-ended wiring, see:

           https://en.wikipedia.org/wiki/Single-ended_triode

In either case placeholders are discouraged: rather use the "" (blank

string) if the use of the GPIO line is undefined in your design. Ideally,

try to add comments to the dts file describing the naming the convention

try to add comments to the dts file describing the naming convention

you have chosen, and specifying from where the names are derived.

The names are assigned starting from line offset 0, from left to right,

It is also possible to use pin groups for gpio ranges when pin groups are the

easiest and most convenient mapping.

Both both <pinctrl-base> and <count> must set to 0 when using named pin groups

Both <pinctrl-base> and <count> must be set to 0 when using named pin groups

names.

The property gpio-ranges-group-names must contain exactly one string for each

Elements of gpio-ranges-group-names must contain the name of a pin group

defined in the respective pin controller. The number of pins/GPIO lines in the

range is the number of pins in that pin group. The number of pins of that

group is defined int the implementation and not in the device tree.

group is defined in the implementation and not in the device tree.

If numerical and named pin groups are mixed, the string corresponding to a

numerical pin range in gpio-ranges-group-names must be empty.

  As above, The Multimedia HW will go through SMI and M4U while it

  access EMI. SMI is a bridge between m4u and the Multimedia HW. It contain

  smi local arbiter and smi common. It will control whether the Multimedia

  HW should go though the m4u for translation or bypass it and talk

  HW should go through the m4u for translation or bypass it and talk

  directly with EMI. And also SMI help control the power domain and clocks for

  each local arbiter.

  default-state:

    description:

      The initial state of the LED. If the LED is already on or off and the

      default-state property is set the to same value, then no glitch should be

      default-state property is set to the same value, then no glitch should be

      produced where the LED momentarily turns off (or on). The "keep" setting

      will keep the LED at whatever its current state is, without producing a

      glitch.