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

Commit 7844b892 authored by Greg Kroah-Hartman's avatar Greg Kroah-Hartman
Browse files

Merge 4.6-rc7 into usb-next



We want the USB fixes in here to resolve merge issues and make it easier
for testing.

Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parents 545feeff 44549e8f
Loading
Loading
Loading
Loading
+1 −0
Original line number Original line Diff line number Diff line
@@ -69,6 +69,7 @@ Jean Tourrilhes <jt@hpl.hp.com>
Jeff Garzik <jgarzik@pretzel.yyz.us>
Jeff Garzik <jgarzik@pretzel.yyz.us>
Jens Axboe <axboe@suse.de>
Jens Axboe <axboe@suse.de>
Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
John Stultz <johnstul@us.ibm.com>
John Stultz <johnstul@us.ibm.com>
<josh@joshtriplett.org> <josh@freedesktop.org>
<josh@joshtriplett.org> <josh@freedesktop.org>
<josh@joshtriplett.org> <josh@kernel.org>
<josh@joshtriplett.org> <josh@kernel.org>
+4 −0
Original line number Original line Diff line number Diff line
@@ -32,6 +32,10 @@ Optional properties:
- target-supply     : regulator for SATA target power
- target-supply     : regulator for SATA target power
- phys              : reference to the SATA PHY node
- phys              : reference to the SATA PHY node
- phy-names         : must be "sata-phy"
- phy-names         : must be "sata-phy"
- ports-implemented : Mask that indicates which ports that the HBA supports
		      are available for software to use. Useful if PORTS_IMPL
		      is not programmed by the BIOS, which is true with
		      some embedded SOC's.


Required properties when using sub-nodes:
Required properties when using sub-nodes:
- #address-cells    : number of cells to encode an address
- #address-cells    : number of cells to encode an address
+3 −3
Original line number Original line Diff line number Diff line
@@ -45,13 +45,13 @@ Required properties:
Optional properties:
Optional properties:
- dual_emac_res_vlan	: Specifies VID to be used to segregate the ports
- dual_emac_res_vlan	: Specifies VID to be used to segregate the ports
- mac-address		: See ethernet.txt file in the same directory
- mac-address		: See ethernet.txt file in the same directory
- phy_id		: Specifies slave phy id
- phy_id		: Specifies slave phy id (deprecated, use phy-handle)
- phy-handle		: See ethernet.txt file in the same directory
- phy-handle		: See ethernet.txt file in the same directory


Slave sub-nodes:
Slave sub-nodes:
- fixed-link		: See fixed-link.txt file in the same directory
- fixed-link		: See fixed-link.txt file in the same directory
			  Either the property phy_id, or the sub-node

			  fixed-link can be specified
Note: Exactly one of phy_id, phy-handle, or fixed-link must be specified.


Note: "ti,hwmods" field is used to fetch the base address and irq
Note: "ti,hwmods" field is used to fetch the base address and irq
resources from TI, omap hwmod data base during device registration.
resources from TI, omap hwmod data base during device registration.
+3 −3
Original line number Original line Diff line number Diff line
@@ -6,7 +6,7 @@ This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
using the SGDMA and MSGDMA soft DMA IP components. The driver uses the
using the SGDMA and MSGDMA soft DMA IP components. The driver uses the
platform bus to obtain component resources. The designs used to test this
platform bus to obtain component resources. The designs used to test this
driver were built for a Cyclone(R) V SOC FPGA board, a Cyclone(R) V FPGA board,
driver were built for a Cyclone(R) V SOC FPGA board, a Cyclone(R) V FPGA board,
and tested with ARM and NIOS processor hosts seperately. The anticipated use
and tested with ARM and NIOS processor hosts separately. The anticipated use
cases are simple communications between an embedded system and an external peer
cases are simple communications between an embedded system and an external peer
for status and simple configuration of the embedded system.
for status and simple configuration of the embedded system.


@@ -65,14 +65,14 @@ Driver parameters can be also passed in command line by using:
4.1) Transmit process
4.1) Transmit process
When the driver's transmit routine is called by the kernel, it sets up a
When the driver's transmit routine is called by the kernel, it sets up a
transmit descriptor by calling the underlying DMA transmit routine (SGDMA or
transmit descriptor by calling the underlying DMA transmit routine (SGDMA or
MSGDMA), and initites a transmit operation. Once the transmit is complete, an
MSGDMA), and initiates a transmit operation. Once the transmit is complete, an
interrupt is driven by the transmit DMA logic. The driver handles the transmit
interrupt is driven by the transmit DMA logic. The driver handles the transmit
completion in the context of the interrupt handling chain by recycling
completion in the context of the interrupt handling chain by recycling
resource required to send and track the requested transmit operation.
resource required to send and track the requested transmit operation.


4.2) Receive process
4.2) Receive process
The driver will post receive buffers to the receive DMA logic during driver
The driver will post receive buffers to the receive DMA logic during driver
intialization. Receive buffers may or may not be queued depending upon the
initialization. Receive buffers may or may not be queued depending upon the
underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
to queue receive buffers to the SGDMA receive logic). When a packet is
to queue receive buffers to the SGDMA receive logic). When a packet is
received, the DMA logic generates an interrupt. The driver handles a receive
received, the DMA logic generates an interrupt. The driver handles a receive
+3 −3
Original line number Original line Diff line number Diff line
@@ -8,7 +8,7 @@ Initial Release:
	This is conceptually very similar to the macvlan driver with one major
	This is conceptually very similar to the macvlan driver with one major
exception of using L3 for mux-ing /demux-ing among slaves. This property makes
exception of using L3 for mux-ing /demux-ing among slaves. This property makes
the master device share the L2 with it's slave devices. I have developed this
the master device share the L2 with it's slave devices. I have developed this
driver in conjuntion with network namespaces and not sure if there is use case
driver in conjunction with network namespaces and not sure if there is use case
outside of it.
outside of it.




@@ -56,7 +56,7 @@ situations defines your use case then you can choose to use ipvlan -
	(a) The Linux host that is connected to the external switch / router has
	(a) The Linux host that is connected to the external switch / router has
policy configured that allows only one mac per port.
policy configured that allows only one mac per port.
	(b) No of virtual devices created on a master exceed the mac capacity and
	(b) No of virtual devices created on a master exceed the mac capacity and
puts the NIC in promiscous mode and degraded performance is a concern.
puts the NIC in promiscuous mode and degraded performance is a concern.
	(c) If the slave device is to be put into the hostile / untrusted network
	(c) If the slave device is to be put into the hostile / untrusted network
namespace where L2 on the slave could be changed / misused.
namespace where L2 on the slave could be changed / misused.


Loading