-
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 branch 'Socionext-Synquacer-NETSEC-driver'
Jassi Brar says: ==================== Socionext Synquacer NETSEC driver Changes since v5 # Removed helper macros # Removed 'inline' qualifier # Changed multiline empty comment to single line # Added 'clock-names' property in DT binding example # Ignore 'clock-names' property in driver until f/ws in the wild are upgraded or we support instance that take in more than one clock. # Rebased the patchset onto net-next Changes since v4 # Fixed ucode indexing as a word, instead of byte # Removed redundant clocks, keep only phy rate reference clock and expect it to be 'phy_ref_clk' Changes since v3 # Discard 'socionext,snq-mdio', and simply use 'mdio' subnode. # Use ioremap on ucode region as well, instead of memremap. Changes since v2 # Use 'mdio' subnode in DT bindings. # Use phy_interface_mode_is_rgmii(), instead of open coding the check. # Use readl/b with eeprom_base pointer. # Unregister mdio bus upon failure in probe. Changes since v1 # Switched from using memremap to ioremap # Implemented ndo_do_ioctl callback # Defined optional 'dma-coherent' DT property ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
- Loading branch information
Showing
5 changed files
with
1,848 additions
and
0 deletions.
There are no files selected for viewing
53 changes: 53 additions & 0 deletions
53
Documentation/devicetree/bindings/net/socionext-netsec.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,53 @@ | ||
* Socionext NetSec Ethernet Controller IP | ||
|
||
Required properties: | ||
- compatible: Should be "socionext,synquacer-netsec" | ||
- reg: Address and length of the control register area, followed by the | ||
address and length of the EEPROM holding the MAC address and | ||
microengine firmware | ||
- interrupts: Should contain ethernet controller interrupt | ||
- clocks: phandle to the PHY reference clock | ||
- clock-names: Should be "phy_ref_clk" | ||
- phy-mode: See ethernet.txt file in the same directory | ||
- phy-handle: See ethernet.txt in the same directory. | ||
|
||
- mdio device tree subnode: When the Netsec has a phy connected to its local | ||
mdio, there must be device tree subnode with the following | ||
required properties: | ||
|
||
- #address-cells: Must be <1>. | ||
- #size-cells: Must be <0>. | ||
|
||
For each phy on the mdio bus, there must be a node with the following | ||
fields: | ||
- compatible: Refer to phy.txt | ||
- reg: phy id used to communicate to phy. | ||
|
||
Optional properties: (See ethernet.txt file in the same directory) | ||
- dma-coherent: Boolean property, must only be present if memory | ||
accesses performed by the device are cache coherent. | ||
- local-mac-address: See ethernet.txt in the same directory. | ||
- mac-address: See ethernet.txt in the same directory. | ||
- max-speed: See ethernet.txt in the same directory. | ||
- max-frame-size: See ethernet.txt in the same directory. | ||
|
||
Example: | ||
eth0: ethernet@522d0000 { | ||
compatible = "socionext,synquacer-netsec"; | ||
reg = <0 0x522d0000 0x0 0x10000>, <0 0x10000000 0x0 0x10000>; | ||
interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>; | ||
clocks = <&clk_netsec>; | ||
clock-names = "phy_ref_clk"; | ||
phy-mode = "rgmii"; | ||
max-speed = <1000>; | ||
max-frame-size = <9000>; | ||
phy-handle = <&phy1>; | ||
|
||
mdio { | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
phy1: ethernet-phy@1 { | ||
compatible = "ethernet-phy-ieee802.3-c22"; | ||
reg = <1>; | ||
}; | ||
}; |
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.