-
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.
yaml --- r: 314930 b: refs/heads/master c: 8732baa h: refs/heads/master v: v3
- Loading branch information
John W. Linville
committed
Jun 29, 2012
1 parent
4aa8c4b
commit 9f7c918
Showing
1,364 changed files
with
29,113 additions
and
15,249 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 |
---|---|---|
@@ -1,2 +1,2 @@ | ||
--- | ||
refs/heads/master: 42fb0b0278e6b9a44bee8adec051de5f43e10b2b | ||
refs/heads/master: 8732baafc3f19e69df683c3f0f36c13cec746fb9 |
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
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
93 changes: 93 additions & 0 deletions
93
trunk/Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.txt
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,93 @@ | ||
Pinctrl-based I2C Bus Mux | ||
|
||
This binding describes an I2C bus multiplexer that uses pin multiplexing to | ||
route the I2C signals, and represents the pin multiplexing configuration | ||
using the pinctrl device tree bindings. | ||
|
||
+-----+ +-----+ | ||
| dev | | dev | | ||
+------------------------+ +-----+ +-----+ | ||
| SoC | | | | ||
| /----|------+--------+ | ||
| +---+ +------+ | child bus A, on first set of pins | ||
| |I2C|---|Pinmux| | | ||
| +---+ +------+ | child bus B, on second set of pins | ||
| \----|------+--------+--------+ | ||
| | | | | | ||
+------------------------+ +-----+ +-----+ +-----+ | ||
| dev | | dev | | dev | | ||
+-----+ +-----+ +-----+ | ||
|
||
Required properties: | ||
- compatible: i2c-mux-pinctrl | ||
- i2c-parent: The phandle of the I2C bus that this multiplexer's master-side | ||
port is connected to. | ||
|
||
Also required are: | ||
|
||
* Standard pinctrl properties that specify the pin mux state for each child | ||
bus. See ../pinctrl/pinctrl-bindings.txt. | ||
|
||
* Standard I2C mux properties. See mux.txt in this directory. | ||
|
||
* I2C child bus nodes. See mux.txt in this directory. | ||
|
||
For each named state defined in the pinctrl-names property, an I2C child bus | ||
will be created. I2C child bus numbers are assigned based on the index into | ||
the pinctrl-names property. | ||
|
||
The only exception is that no bus will be created for a state named "idle". If | ||
such a state is defined, it must be the last entry in pinctrl-names. For | ||
example: | ||
|
||
pinctrl-names = "ddc", "pta", "idle" -> ddc = bus 0, pta = bus 1 | ||
pinctrl-names = "ddc", "idle", "pta" -> Invalid ("idle" not last) | ||
pinctrl-names = "idle", "ddc", "pta" -> Invalid ("idle" not last) | ||
|
||
Whenever an access is made to a device on a child bus, the relevant pinctrl | ||
state will be programmed into hardware. | ||
|
||
If an idle state is defined, whenever an access is not being made to a device | ||
on a child bus, the idle pinctrl state will be programmed into hardware. | ||
|
||
If an idle state is not defined, the most recently used pinctrl state will be | ||
left programmed into hardware whenever no access is being made of a device on | ||
a child bus. | ||
|
||
Example: | ||
|
||
i2cmux { | ||
compatible = "i2c-mux-pinctrl"; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
i2c-parent = <&i2c1>; | ||
|
||
pinctrl-names = "ddc", "pta", "idle"; | ||
pinctrl-0 = <&state_i2cmux_ddc>; | ||
pinctrl-1 = <&state_i2cmux_pta>; | ||
pinctrl-2 = <&state_i2cmux_idle>; | ||
|
||
i2c@0 { | ||
reg = <0>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
eeprom { | ||
compatible = "eeprom"; | ||
reg = <0x50>; | ||
}; | ||
}; | ||
|
||
i2c@1 { | ||
reg = <1>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
eeprom { | ||
compatible = "eeprom"; | ||
reg = <0x50>; | ||
}; | ||
}; | ||
}; | ||
|
29 changes: 29 additions & 0 deletions
29
trunk/Documentation/devicetree/bindings/net/broadcom-bcm87xx.txt
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,29 @@ | ||
The Broadcom BCM87XX devices are a family of 10G Ethernet PHYs. They | ||
have these bindings in addition to the standard PHY bindings. | ||
|
||
Compatible: Should contain "broadcom,bcm8706" or "broadcom,bcm8727" and | ||
"ethernet-phy-ieee802.3-c45" | ||
|
||
Optional Properties: | ||
|
||
- broadcom,c45-reg-init : one of more sets of 4 cells. The first cell | ||
is the MDIO Manageable Device (MMD) address, the second a register | ||
address within the MMD, the third cell contains a mask to be ANDed | ||
with the existing register value, and the fourth cell is ORed with | ||
he result to yield the new register value. If the third cell has a | ||
value of zero, no read of the existing value is performed. | ||
|
||
Example: | ||
|
||
ethernet-phy@5 { | ||
reg = <5>; | ||
compatible = "broadcom,bcm8706", "ethernet-phy-ieee802.3-c45"; | ||
interrupt-parent = <&gpio>; | ||
interrupts = <12 8>; /* Pin 12, active low */ | ||
/* | ||
* Set PMD Digital Control Register for | ||
* GPIO[1] Tx/Rx | ||
* GPIO[0] R64 Sync Acquired | ||
*/ | ||
broadcom,c45-reg-init = <1 0xc808 0xff8f 0x70>; | ||
}; |
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.