forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branches 'spi/topic/fsl-dspi', 'spi/topic/imx',…
… 'spi/topic/mxs', 'spi/topic/omap-100k' and 'spi/topic/orion' into spi-next
- Loading branch information
Showing
12 changed files
with
501 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
Device-Tree binding for regmap | ||
|
||
The endianness mode of CPU & Device scenarios: | ||
Index Device Endianness properties | ||
--------------------------------------------------- | ||
1 BE 'big-endian' | ||
2 LE 'little-endian' | ||
|
||
For one device driver, which will run in different scenarios above | ||
on different SoCs using the devicetree, we need one way to simplify | ||
this. | ||
|
||
Required properties: | ||
- {big,little}-endian: these are boolean properties, if absent | ||
meaning that the CPU and the Device are in the same endianness mode, | ||
these properties are for register values and all the buffers only. | ||
|
||
Examples: | ||
Scenario 1 : CPU in LE mode & device in LE mode. | ||
dev: dev@40031000 { | ||
compatible = "name"; | ||
reg = <0x40031000 0x1000>; | ||
... | ||
}; | ||
|
||
Scenario 2 : CPU in LE mode & device in BE mode. | ||
dev: dev@40031000 { | ||
compatible = "name"; | ||
reg = <0x40031000 0x1000>; | ||
... | ||
big-endian; | ||
}; | ||
|
||
Scenario 3 : CPU in BE mode & device in BE mode. | ||
dev: dev@40031000 { | ||
compatible = "name"; | ||
reg = <0x40031000 0x1000>; | ||
... | ||
}; | ||
|
||
Scenario 4 : CPU in BE mode & device in LE mode. | ||
dev: dev@40031000 { | ||
compatible = "name"; | ||
reg = <0x40031000 0x1000>; | ||
... | ||
little-endian; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.