Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9ca18397 authored by Masanari Iida's avatar Masanari Iida Committed by Jiri Kosina
Browse files

doc: devicetree: bindings: Fix typo in bindings 



Correct spelling typo in devicetree/bindings.

Singed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>

Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent a3f86127

Documentation/devicetree/bindings/arm/ste-u300.txt

+1 −1
Original line number Diff line number Diff line
@@ -22,7 +22,7 @@ This contains the board-specific information. 
- compatible: must be "stericsson,s365".

- vana15-supply: the regulator supplying the 1.5V to drive the

  board.

- syscon: a pointer to the syscon node so we can acccess the

- syscon: a pointer to the syscon node so we can access the

  syscon registers to set the board as self-powered.



Example:

Documentation/devicetree/bindings/dma/atmel-dma.txt

+2 −2
Original line number Diff line number Diff line
@@ -18,14 +18,14 @@ dma0: dma@ffffec00 { 


DMA clients connected to the Atmel DMA controller must use the format

described in the dma.txt file, using a three-cell specifier for each channel:

a phandle plus two interger cells.

a phandle plus two integer cells.

The three cells in order are:



1. A phandle pointing to the DMA controller.

2. The memory interface (16 most significant bits), the peripheral interface

(16 less significant bits).

3. Parameters for the at91 DMA configuration register which are device

dependant:

dependent:

  - bit 7-0: peripheral identifier for the hardware handshaking interface. The

  identifier can be different for tx and rx.

  - bit 11-8: FIFO configuration. 0 for half FIFO, 1 for ALAP, 1 for ASAP.

Documentation/devicetree/bindings/dma/fsl-imx-dma.txt

+1 −1
Original line number Diff line number Diff line
@@ -34,7 +34,7 @@ Clients have to specify the DMA requests with phandles in a list. 
Required properties:

- dmas: List of one or more DMA request specifiers. One DMA request specifier

    consists of a phandle to the DMA controller followed by the integer

    specifiying the request line.

    specifying the request line.

- dma-names: List of string identifiers for the DMA requests. For the correct

    names, have a look at the specific client driver.

Documentation/devicetree/bindings/dma/ste-dma40.txt

+2 −2
Original line number Diff line number Diff line
@@ -37,14 +37,14 @@ Each dmas request consists of 4 cells: 
  1. A phandle pointing to the DMA controller

  2. Device Type

  3. The DMA request line number (only when 'use fixed channel' is set)

  4. A 32bit mask specifying; mode, direction and endianess [NB: This list will grow]

  4. A 32bit mask specifying; mode, direction and endianness [NB: This list will grow]

        0x00000001: Mode:

                Logical channel when unset

                Physical channel when set

        0x00000002: Direction:

                Memory to Device when unset

                Device to Memory when set

        0x00000004: Endianess:

        0x00000004: Endianness:

                Little endian when unset

                Big endian when set

        0x00000008: Use fixed channel:

Documentation/devicetree/bindings/mfd/cros-ec.txt

+1 −1
Original line number Diff line number Diff line
@@ -4,7 +4,7 @@ Google's ChromeOS EC is a Cortex-M device which talks to the AP and 
implements various function such as keyboard and battery charging.



The EC can be connect through various means (I2C, SPI, LPC) and the

compatible string used depends on the inteface. Each connection method has

compatible string used depends on the interface. Each connection method has

its own driver which connects to the top level interface-agnostic EC driver.

Other Linux driver (such as cros-ec-keyb for the matrix keyboard) connect to

the top-level driver.