You've already forked linux-apfs
mirror of
https://github.com/linux-apfs/linux-apfs.git
synced 2026-05-01 15:00:59 -07:00
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
Pull networking updates from David Miller:
1) Significantly shrink the core networking routing structures. Result
of http://vger.kernel.org/~davem/seoul2017_netdev_keynote.pdf
2) Add netdevsim driver for testing various offloads, from Jakub
Kicinski.
3) Support cross-chip FDB operations in DSA, from Vivien Didelot.
4) Add a 2nd listener hash table for TCP, similar to what was done for
UDP. From Martin KaFai Lau.
5) Add eBPF based queue selection to tun, from Jason Wang.
6) Lockless qdisc support, from John Fastabend.
7) SCTP stream interleave support, from Xin Long.
8) Smoother TCP receive autotuning, from Eric Dumazet.
9) Lots of erspan tunneling enhancements, from William Tu.
10) Add true function call support to BPF, from Alexei Starovoitov.
11) Add explicit support for GRO HW offloading, from Michael Chan.
12) Support extack generation in more netlink subsystems. From Alexander
Aring, Quentin Monnet, and Jakub Kicinski.
13) Add 1000BaseX, flow control, and EEE support to mvneta driver. From
Russell King.
14) Add flow table abstraction to netfilter, from Pablo Neira Ayuso.
15) Many improvements and simplifications to the NFP driver bpf JIT,
from Jakub Kicinski.
16) Support for ipv6 non-equal cost multipath routing, from Ido
Schimmel.
17) Add resource abstration to devlink, from Arkadi Sharshevsky.
18) Packet scheduler classifier shared filter block support, from Jiri
Pirko.
19) Avoid locking in act_csum, from Davide Caratti.
20) devinet_ioctl() simplifications from Al viro.
21) More TCP bpf improvements from Lawrence Brakmo.
22) Add support for onlink ipv6 route flag, similar to ipv4, from David
Ahern.
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next: (1925 commits)
tls: Add support for encryption using async offload accelerator
ip6mr: fix stale iterator
net/sched: kconfig: Remove blank help texts
openvswitch: meter: Use 64-bit arithmetic instead of 32-bit
tcp_nv: fix potential integer overflow in tcpnv_acked
r8169: fix RTL8168EP take too long to complete driver initialization.
qmi_wwan: Add support for Quectel EP06
rtnetlink: enable IFLA_IF_NETNSID for RTM_NEWLINK
ipmr: Fix ptrdiff_t print formatting
ibmvnic: Wait for device response when changing MAC
qlcnic: fix deadlock bug
tcp: release sk_frag.page in tcp_disconnect
ipv4: Get the address of interface correctly.
net_sched: gen_estimator: fix lockdep splat
net: macb: Handle HRESP error
net/mlx5e: IPoIB, Fix copy-paste bug in flow steering refactoring
ipv6: addrconf: break critical section in addrconf_verify_rtnl()
ipv6: change route cache aging logic
i40e/i40evf: Update DESC_NEEDED value to reflect larger value
bnxt_en: cleanup DIM work on device shutdown
...
This commit is contained in:
Linus Torvalds
@@ -0,0 +1,33 @@
|
||||
What: /kvd/
|
||||
Date: 08-Jan-2018
|
||||
KernelVersion: v4.16
|
||||
Contact: mlxsw@mellanox.com
|
||||
Description: The main database in the Spectrum device is a centralized
|
||||
KVD database used for many of the tables used to configure
|
||||
the chip including L2 FDB, L3 LPM, ECMP and more. The KVD
|
||||
is divided into two sections, the first is hash-based table
|
||||
and the second is a linear access table. The division
|
||||
between the linear and hash-based sections is static and
|
||||
require reload before the changes take effect.
|
||||
|
||||
What: /kvd/linear
|
||||
Date: 08-Jan-2018
|
||||
KernelVersion: v4.16
|
||||
Contact: mlxsw@mellanox.com
|
||||
Description: The linear section of the KVD is managed by software as a
|
||||
flat memory accessed using an index.
|
||||
|
||||
What: /kvd/hash_single
|
||||
Date: 08-Jan-2018
|
||||
KernelVersion: v4.16
|
||||
Contact: mlxsw@mellanox.com
|
||||
Description: The hash based section of the KVD is managed by the switch
|
||||
device. Used in case the key size is smaller or equal to
|
||||
64bit.
|
||||
|
||||
What: /kvd/hash_double
|
||||
Date: 08-Jan-2018
|
||||
KernelVersion: v4.16
|
||||
Contact: mlxsw@mellanox.com
|
||||
Description: The hash based section of the KVD is managed by the switch
|
||||
device. Used in case the key is larger than 64 bit.
|
||||
@@ -259,3 +259,27 @@ Contact: netdev@vger.kernel.org
|
||||
Description:
|
||||
Symbolic link to the PHY device this network device is attached
|
||||
to.
|
||||
|
||||
What: /sys/class/net/<iface>/carrier_changes
|
||||
Date: Mar 2014
|
||||
KernelVersion: 3.15
|
||||
Contact: netdev@vger.kernel.org
|
||||
Description:
|
||||
32-bit unsigned integer counting the number of times the link has
|
||||
seen a change from UP to DOWN and vice versa
|
||||
|
||||
What: /sys/class/net/<iface>/carrier_up_count
|
||||
Date: Jan 2018
|
||||
KernelVersion: 4.16
|
||||
Contact: netdev@vger.kernel.org
|
||||
Description:
|
||||
32-bit unsigned integer counting the number of times the link has
|
||||
been up
|
||||
|
||||
What: /sys/class/net/<iface>/carrier_down_count
|
||||
Date: Jan 2018
|
||||
KernelVersion: 4.16
|
||||
Contact: netdev@vger.kernel.org
|
||||
Description:
|
||||
32-bit unsigned integer counting the number of times the link has
|
||||
been down
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -2,7 +2,10 @@
|
||||
|
||||
Required properties:
|
||||
|
||||
- compatible: should be "brcm,bcm7445-switch-v4.0" or "brcm,bcm7278-switch-v4.0"
|
||||
- compatible: should be one of
|
||||
"brcm,bcm7445-switch-v4.0"
|
||||
"brcm,bcm7278-switch-v4.0"
|
||||
"brcm,bcm7278-switch-v4.8"
|
||||
- reg: addresses and length of the register sets for the device, must be 6
|
||||
pairs of register addresses and lengths
|
||||
- interrupts: interrupts for the devices, must be two interrupts
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
Generic CAN transceiver Device Tree binding
|
||||
------------------------------
|
||||
|
||||
CAN transceiver typically limits the max speed in standard CAN and CAN FD
|
||||
modes. Typically these limitations are static and the transceivers themselves
|
||||
provide no way to detect this limitation at runtime. For this situation,
|
||||
the "can-transceiver" node can be used.
|
||||
|
||||
Required Properties:
|
||||
max-bitrate: a positive non 0 value that determines the max
|
||||
speed that CAN/CAN-FD can run. Any other value
|
||||
will be ignored.
|
||||
|
||||
Examples:
|
||||
|
||||
Based on Texas Instrument's TCAN1042HGV CAN Transceiver
|
||||
|
||||
m_can0 {
|
||||
....
|
||||
can-transceiver {
|
||||
max-bitrate = <5000000>;
|
||||
};
|
||||
...
|
||||
};
|
||||
@@ -18,6 +18,12 @@ Optional properties:
|
||||
|
||||
- xceiver-supply: Regulator that powers the CAN transceiver
|
||||
|
||||
- big-endian: This means the registers of FlexCAN controller are big endian.
|
||||
This is optional property.i.e. if this property is not present in
|
||||
device tree node then controller is assumed to be little endian.
|
||||
if this property is present then controller is assumed to be big
|
||||
endian.
|
||||
|
||||
Example:
|
||||
|
||||
can@1c000 {
|
||||
|
||||
@@ -43,6 +43,11 @@ Required properties:
|
||||
Please refer to 2.4.1 Message RAM Configuration in
|
||||
Bosch M_CAN user manual for details.
|
||||
|
||||
Optional Subnode:
|
||||
- can-transceiver : Can-transceiver subnode describing maximum speed
|
||||
that can be used for CAN/CAN-FD modes. See
|
||||
Documentation/devicetree/bindings/net/can/can-transceiver.txt
|
||||
for details.
|
||||
Example:
|
||||
SoC dtsi:
|
||||
m_can1: can@20e8000 {
|
||||
@@ -63,4 +68,8 @@ Board dts:
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&pinctrl_m_can1>;
|
||||
status = "enabled";
|
||||
|
||||
can-transceiver {
|
||||
max-bitrate = <5000000>;
|
||||
};
|
||||
};
|
||||
|
||||
@@ -2,7 +2,9 @@ Renesas R-Car CAN controller Device Tree Bindings
|
||||
-------------------------------------------------
|
||||
|
||||
Required properties:
|
||||
- compatible: "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
|
||||
- compatible: "renesas,can-r8a7743" if CAN controller is a part of R8A7743 SoC.
|
||||
"renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC.
|
||||
"renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
|
||||
"renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
|
||||
"renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
|
||||
"renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC.
|
||||
@@ -12,7 +14,8 @@ Required properties:
|
||||
"renesas,can-r8a7795" if CAN controller is a part of R8A7795 SoC.
|
||||
"renesas,can-r8a7796" if CAN controller is a part of R8A7796 SoC.
|
||||
"renesas,rcar-gen1-can" for a generic R-Car Gen1 compatible device.
|
||||
"renesas,rcar-gen2-can" for a generic R-Car Gen2 compatible device.
|
||||
"renesas,rcar-gen2-can" for a generic R-Car Gen2 or RZ/G1
|
||||
compatible device.
|
||||
"renesas,rcar-gen3-can" for a generic R-Car Gen3 compatible device.
|
||||
When compatible with the generic version, nodes must list the
|
||||
SoC-specific version corresponding to the platform first
|
||||
|
||||
@@ -0,0 +1,92 @@
|
||||
Cortina Systems Gemini Ethernet Controller
|
||||
==========================================
|
||||
|
||||
This ethernet controller is found in the Gemini SoC family:
|
||||
StorLink SL3512 and SL3516, also known as Cortina Systems
|
||||
CS3512 and CS3516.
|
||||
|
||||
Required properties:
|
||||
- compatible: must be "cortina,gemini-ethernet"
|
||||
- reg: must contain the global registers and the V-bit and A-bit
|
||||
memory areas, in total three register sets.
|
||||
- syscon: a phandle to the system controller
|
||||
- #address-cells: must be specified, must be <1>
|
||||
- #size-cells: must be specified, must be <1>
|
||||
- ranges: should be state like this giving a 1:1 address translation
|
||||
for the subnodes
|
||||
|
||||
The subnodes represents the two ethernet ports in this device.
|
||||
They are not independent of each other since they share resources
|
||||
in the parent node, and are thus children.
|
||||
|
||||
Required subnodes:
|
||||
- port0: contains the resources for ethernet port 0
|
||||
- port1: contains the resources for ethernet port 1
|
||||
|
||||
Required subnode properties:
|
||||
- compatible: must be "cortina,gemini-ethernet-port"
|
||||
- reg: must contain two register areas: the DMA/TOE memory and
|
||||
the GMAC memory area of the port
|
||||
- interrupts: should contain the interrupt line of the port.
|
||||
this is nominally a level interrupt active high.
|
||||
- resets: this must provide an SoC-integrated reset line for
|
||||
the port.
|
||||
- clocks: this should contain a handle to the PCLK clock for
|
||||
clocking the silicon in this port
|
||||
- clock-names: must be "PCLK"
|
||||
|
||||
Optional subnode properties:
|
||||
- phy-mode: see ethernet.txt
|
||||
- phy-handle: see ethernet.txt
|
||||
|
||||
Example:
|
||||
|
||||
mdio-bus {
|
||||
(...)
|
||||
phy0: ethernet-phy@1 {
|
||||
reg = <1>;
|
||||
device_type = "ethernet-phy";
|
||||
};
|
||||
phy1: ethernet-phy@3 {
|
||||
reg = <3>;
|
||||
device_type = "ethernet-phy";
|
||||
};
|
||||
};
|
||||
|
||||
|
||||
ethernet@60000000 {
|
||||
compatible = "cortina,gemini-ethernet";
|
||||
reg = <0x60000000 0x4000>, /* Global registers, queue */
|
||||
<0x60004000 0x2000>, /* V-bit */
|
||||
<0x60006000 0x2000>; /* A-bit */
|
||||
syscon = <&syscon>;
|
||||
#address-cells = <1>;
|
||||
#size-cells = <1>;
|
||||
ranges;
|
||||
|
||||
gmac0: ethernet-port@0 {
|
||||
compatible = "cortina,gemini-ethernet-port";
|
||||
reg = <0x60008000 0x2000>, /* Port 0 DMA/TOE */
|
||||
<0x6000a000 0x2000>; /* Port 0 GMAC */
|
||||
interrupt-parent = <&intcon>;
|
||||
interrupts = <1 IRQ_TYPE_LEVEL_HIGH>;
|
||||
resets = <&syscon GEMINI_RESET_GMAC0>;
|
||||
clocks = <&syscon GEMINI_CLK_GATE_GMAC0>;
|
||||
clock-names = "PCLK";
|
||||
phy-mode = "rgmii";
|
||||
phy-handle = <&phy0>;
|
||||
};
|
||||
|
||||
gmac1: ethernet-port@1 {
|
||||
compatible = "cortina,gemini-ethernet-port";
|
||||
reg = <0x6000c000 0x2000>, /* Port 1 DMA/TOE */
|
||||
<0x6000e000 0x2000>; /* Port 1 GMAC */
|
||||
interrupt-parent = <&intcon>;
|
||||
interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
|
||||
resets = <&syscon GEMINI_RESET_GMAC1>;
|
||||
clocks = <&syscon GEMINI_CLK_GATE_GMAC1>;
|
||||
clock-names = "PCLK";
|
||||
phy-mode = "rgmii";
|
||||
phy-handle = <&phy1>;
|
||||
};
|
||||
};
|
||||
@@ -59,7 +59,7 @@ ethernet@83fec000 {
|
||||
reg = <0x83fec000 0x4000>;
|
||||
interrupts = <87>;
|
||||
phy-mode = "mii";
|
||||
phy-reset-gpios = <&gpio2 14 0>; /* GPIO2_14 */
|
||||
phy-reset-gpios = <&gpio2 14 GPIO_ACTIVE_LOW>; /* GPIO2_14 */
|
||||
local-mac-address = [00 04 9F 01 1B B9];
|
||||
phy-supply = <®_fec_supply>;
|
||||
};
|
||||
@@ -71,7 +71,7 @@ ethernet@83fec000 {
|
||||
reg = <0x83fec000 0x4000>;
|
||||
interrupts = <87>;
|
||||
phy-mode = "mii";
|
||||
phy-reset-gpios = <&gpio2 14 0>; /* GPIO2_14 */
|
||||
phy-reset-gpios = <&gpio2 14 GPIO_ACTIVE_LOW>; /* GPIO2_14 */
|
||||
local-mac-address = [00 04 9F 01 1B B9];
|
||||
phy-supply = <®_fec_supply>;
|
||||
phy-handle = <ðphy>;
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
* ADF7242 IEEE 802.15.4 *
|
||||
|
||||
Required properties:
|
||||
- compatible: should be "adi,adf7242"
|
||||
- compatible: should be "adi,adf7242", "adi,adf7241"
|
||||
- spi-max-frequency: maximal bus speed (12.5 MHz)
|
||||
- reg: the chipselect index
|
||||
- interrupts: the interrupt generated by the device via pin IRQ1.
|
||||
|
||||
@@ -28,7 +28,7 @@ Required properties:
|
||||
- mediatek,sgmiisys: phandle to the syscon node that handles the SGMII setup
|
||||
which is required for those SoCs equipped with SGMII such as MT7622 SoC.
|
||||
- mediatek,pctl: phandle to the syscon node that handles the ports slew rate
|
||||
and driver current
|
||||
and driver current: only for MT2701 and MT7623 SoC
|
||||
|
||||
Optional properties:
|
||||
- interrupt-parent: Should be the phandle for the interrupt controller
|
||||
|
||||
@@ -53,6 +53,14 @@ Optional Properties:
|
||||
to ensure the integrated PHY is used. The absence of this property indicates
|
||||
the muxers should be configured so that the external PHY is used.
|
||||
|
||||
- reset-gpios: The GPIO phandle and specifier for the PHY reset signal.
|
||||
|
||||
- reset-assert-us: Delay after the reset was asserted in microseconds.
|
||||
If this property is missing the delay will be skipped.
|
||||
|
||||
- reset-deassert-us: Delay after the reset was deasserted in microseconds.
|
||||
If this property is missing the delay will be skipped.
|
||||
|
||||
Example:
|
||||
|
||||
ethernet-phy@0 {
|
||||
@@ -60,4 +68,8 @@ ethernet-phy@0 {
|
||||
interrupt-parent = <&PIC>;
|
||||
interrupts = <35 IRQ_TYPE_EDGE_RISING>;
|
||||
reg = <0>;
|
||||
|
||||
reset-gpios = <&gpio1 4 GPIO_ACTIVE_LOW>;
|
||||
reset-assert-us = <1000>;
|
||||
reset-deassert-us = <2000>;
|
||||
};
|
||||
|
||||
@@ -3,7 +3,9 @@ Transceiver
|
||||
|
||||
Required properties:
|
||||
|
||||
- compatible : must be "sff,sfp"
|
||||
- compatible : must be one of
|
||||
"sff,sfp" for SFP modules
|
||||
"sff,sff" for soldered down SFF modules
|
||||
|
||||
Optional Properties:
|
||||
|
||||
@@ -11,7 +13,8 @@ Optional Properties:
|
||||
interface
|
||||
|
||||
- mod-def0-gpios : GPIO phandle and a specifier of the MOD-DEF0 (AKA Mod_ABS)
|
||||
module presence input gpio signal, active (module absent) high
|
||||
module presence input gpio signal, active (module absent) high. Must
|
||||
not be present for SFF modules
|
||||
|
||||
- los-gpios : GPIO phandle and a specifier of the Receiver Loss of Signal
|
||||
Indication input gpio signal, active (signal lost) high
|
||||
@@ -24,10 +27,11 @@ Optional Properties:
|
||||
|
||||
- rate-select0-gpios : GPIO phandle and a specifier of the Rx Signaling Rate
|
||||
Select (AKA RS0) output gpio signal, low: low Rx rate, high: high Rx rate
|
||||
Must not be present for SFF modules
|
||||
|
||||
- rate-select1-gpios : GPIO phandle and a specifier of the Tx Signaling Rate
|
||||
Select (AKA RS1) output gpio signal (SFP+ only), low: low Tx rate, high:
|
||||
high Tx rate
|
||||
high Tx rate. Must not be present for SFF modules
|
||||
|
||||
Example #1: Direct serdes to SFP connection
|
||||
|
||||
|
||||
@@ -0,0 +1,48 @@
|
||||
* Socionext AVE ethernet controller
|
||||
|
||||
This describes the devicetree bindings for AVE ethernet controller
|
||||
implemented on Socionext UniPhier SoCs.
|
||||
|
||||
Required properties:
|
||||
- compatible: Should be
|
||||
- "socionext,uniphier-pro4-ave4" : for Pro4 SoC
|
||||
- "socionext,uniphier-pxs2-ave4" : for PXs2 SoC
|
||||
- "socionext,uniphier-ld11-ave4" : for LD11 SoC
|
||||
- "socionext,uniphier-ld20-ave4" : for LD20 SoC
|
||||
- reg: Address where registers are mapped and size of region.
|
||||
- interrupts: Should contain the MAC interrupt.
|
||||
- phy-mode: See ethernet.txt in the same directory. Allow to choose
|
||||
"rgmii", "rmii", or "mii" according to the PHY.
|
||||
- phy-handle: Should point to the external phy device.
|
||||
See ethernet.txt file in the same directory.
|
||||
- clocks: A phandle to the clock for the MAC.
|
||||
|
||||
Optional properties:
|
||||
- resets: A phandle to the reset control for the MAC.
|
||||
- local-mac-address: See ethernet.txt in the same directory.
|
||||
|
||||
Required subnode:
|
||||
- mdio: A container for child nodes representing phy nodes.
|
||||
See phy.txt in the same directory.
|
||||
|
||||
Example:
|
||||
|
||||
ether: ethernet@65000000 {
|
||||
compatible = "socionext,uniphier-ld20-ave4";
|
||||
reg = <0x65000000 0x8500>;
|
||||
interrupts = <0 66 4>;
|
||||
phy-mode = "rgmii";
|
||||
phy-handle = <ðphy>;
|
||||
clocks = <&sys_clk 6>;
|
||||
resets = <&sys_rst 6>;
|
||||
local-mac-address = [00 00 00 00 00 00];
|
||||
|
||||
mdio {
|
||||
#address-cells = <1>;
|
||||
#size-cells = <0>;
|
||||
|
||||
ethphy: ethphy@1 {
|
||||
reg = <1>;
|
||||
};
|
||||
};
|
||||
};
|
||||
@@ -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>;
|
||||
};
|
||||
};
|
||||
+16
-2
@@ -1,10 +1,18 @@
|
||||
TI WiLink 7/8 (wl12xx/wl18xx) Shared Transport BT/FM/GPS devices
|
||||
Texas Instruments Bluetooth Chips
|
||||
---------------------------------
|
||||
|
||||
This documents the binding structure and common properties for serial
|
||||
attached TI Bluetooth devices. The following chips are included in this
|
||||
binding:
|
||||
|
||||
* TI CC256x Bluetooth devices
|
||||
* TI WiLink 7/8 (wl12xx/wl18xx) Shared Transport BT/FM/GPS devices
|
||||
|
||||
TI WiLink devices have a UART interface for providing Bluetooth, FM radio,
|
||||
and GPS over what's called "shared transport". The shared transport is
|
||||
standard BT HCI protocol with additional channels for the other functions.
|
||||
|
||||
These devices also have a separate WiFi interface as described in
|
||||
TI WiLink devices also have a separate WiFi interface as described in
|
||||
wireless/ti,wlcore.txt.
|
||||
|
||||
This bindings follows the UART slave device binding in
|
||||
@@ -12,6 +20,7 @@ This bindings follows the UART slave device binding in
|
||||
|
||||
Required properties:
|
||||
- compatible: should be one of the following:
|
||||
"ti,cc2560"
|
||||
"ti,wl1271-st"
|
||||
"ti,wl1273-st"
|
||||
"ti,wl1281-st"
|
||||
@@ -32,6 +41,9 @@ Optional properties:
|
||||
See ../clocks/clock-bindings.txt for details.
|
||||
- clock-names : Must include the following entry:
|
||||
"ext_clock" (External clock provided to the TI combo chip).
|
||||
- nvmem-cells: phandle to nvmem data cell that contains a 6 byte BD address
|
||||
with the most significant byte first (big-endian).
|
||||
- nvmem-cell-names: "bd-address" (required when nvmem-cells is specified)
|
||||
|
||||
Example:
|
||||
|
||||
@@ -43,5 +55,7 @@ Example:
|
||||
enable-gpios = <&gpio1 7 GPIO_ACTIVE_HIGH>;
|
||||
clocks = <&clk32k_wl18xx>;
|
||||
clock-names = "ext_clock";
|
||||
nvmem-cells = <&bd_address>;
|
||||
nvmem-cell-names = "bd-address";
|
||||
};
|
||||
};
|
||||
@@ -0,0 +1,32 @@
|
||||
* MediaTek mt76xx devices
|
||||
|
||||
This node provides properties for configuring the MediaTek mt76xx wireless
|
||||
device. The node is expected to be specified as a child node of the PCI
|
||||
controller to which the wireless chip is connected.
|
||||
|
||||
Optional properties:
|
||||
|
||||
- mac-address: See ethernet.txt in the parent directory
|
||||
- local-mac-address: See ethernet.txt in the parent directory
|
||||
- ieee80211-freq-limit: See ieee80211.txt
|
||||
- mediatek,mtd-eeprom: Specify a MTD partition + offset containing EEPROM data
|
||||
|
||||
Optional nodes:
|
||||
- led: Properties for a connected LED
|
||||
Optional properties:
|
||||
- led-sources: See Documentation/devicetree/bindings/leds/common.txt
|
||||
|
||||
&pcie {
|
||||
pcie0 {
|
||||
wifi@0,0 {
|
||||
compatible = "mediatek,mt76";
|
||||
reg = <0x0000 0 0 0 0>;
|
||||
ieee80211-freq-limit = <5000000 6000000>;
|
||||
mediatek,mtd-eeprom = <&factory 0x8000>;
|
||||
|
||||
led {
|
||||
led-sources = <2>;
|
||||
};
|
||||
};
|
||||
};
|
||||
};
|
||||
@@ -41,6 +41,9 @@ Optional properties:
|
||||
- qcom,msi_addr: MSI interrupt address.
|
||||
- qcom,msi_base: Base value to add before writing MSI data into
|
||||
MSI address register.
|
||||
- qcom,ath10k-calibration-variant: string to search for in the board-2.bin
|
||||
variant list with the same bus and device
|
||||
specific ids
|
||||
- qcom,ath10k-calibration-data : calibration data + board specific data
|
||||
as an array, the length can vary between
|
||||
hw versions.
|
||||
|
||||
@@ -195,4 +195,4 @@ External interrupts:
|
||||
|
||||
fsl,mpc5200-mscan nodes
|
||||
-----------------------
|
||||
See file can.txt in this directory.
|
||||
See file Documentation/devicetree/bindings/powerpc/fsl/mpc5200.txt
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user