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

Commit f03ee46b authored by Dave Airlie's avatar Dave Airlie
Browse files

Backmerge tag 'v4.9-rc8' into drm-next 

Linux 4.9-rc8

Daniel requested this so we could apply some follow on fixes cleanly to -next.
parents 0d5320fc 3e5de27e

CREDITS

+4 −4
Original line number Diff line number Diff line
@@ -9,7 +9,7 @@ 
			Linus

----------



M: Matt Mackal

N: Matt Mackal

E: mpm@selenic.com

D: SLOB slab allocator
@@ -1910,7 +1910,7 @@ S: Ra'annana, Israel 


N: Andi Kleen

E: andi@firstfloor.org

U: http://www.halobates.de

W: http://www.halobates.de

D: network, x86, NUMA, various hacks

S: Schwalbenstr. 96

S: 85551 Ottobrunn
@@ -2089,8 +2089,8 @@ D: ST Microelectronics SPEAr13xx PCI host bridge driver 
D: Synopsys Designware PCI host bridge driver



N: Gabor Kuti

M: seasons@falcon.sch.bme.hu

M: seasons@makosteszta.sote.hu

E: seasons@falcon.sch.bme.hu

E: seasons@makosteszta.sote.hu

D: Original author of software suspend



N: Jaroslav Kysela

Documentation/devicetree/bindings/ipmi/aspeed,ast2400-bt-bmc.txt→Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.txt

+2 −2
Original line number Diff line number Diff line
@@ -6,7 +6,7 @@ perform in-band IPMI communication with their host. 


Required properties:



- compatible : should be "aspeed,ast2400-bt-bmc"

- compatible : should be "aspeed,ast2400-ibt-bmc"

- reg: physical address and size of the registers



Optional properties:
@@ -17,7 +17,7 @@ Optional properties: 
Example:



	ibt@1e789140 {

		compatible = "aspeed,ast2400-bt-bmc";

		compatible = "aspeed,ast2400-ibt-bmc";

		reg = <0x1e789140 0x18>;

		interrupts = <8>;

	};

Documentation/devicetree/bindings/net/ethernet.txt

+20 −4
Original line number Diff line number Diff line
@@ -9,10 +9,26 @@ The following properties are common to the Ethernet controllers: 
- max-speed: number, specifies maximum speed in Mbit/s supported by the device;

- max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than

  the maximum frame size (there's contradiction in ePAPR).

- phy-mode: string, operation mode of the PHY interface; supported values are

  "mii", "gmii", "sgmii", "qsgmii", "tbi", "rev-mii", "rmii", "rgmii", "rgmii-id",

  "rgmii-rxid", "rgmii-txid", "rtbi", "smii", "xgmii", "trgmii"; this is now a

  de-facto standard property;

- phy-mode: string, operation mode of the PHY interface. This is now a de-facto

  standard property; supported values are:

  * "mii"

  * "gmii"

  * "sgmii"

  * "qsgmii"

  * "tbi"

  * "rev-mii"

  * "rmii"

  * "rgmii" (RX and TX delays are added by the MAC when required)

  * "rgmii-id" (RGMII with internal RX and TX delays provided by the PHY, the

     MAC should not add the RX or TX delays in this case)

  * "rgmii-rxid" (RGMII with internal RX delay provided by the PHY, the MAC

     should not add an RX delay in this case)

  * "rgmii-txid" (RGMII with internal TX delay provided by the PHY, the MAC

     should not add an TX delay in this case)

  * "rtbi"

  * "smii"

  * "xgmii"

  * "trgmii"

- phy-connection-type: the same as "phy-mode" property but described in ePAPR;

- phy-handle: phandle, specifies a reference to a node representing a PHY

  device; this property is described in ePAPR and so preferred;

Documentation/devicetree/bindings/sound/omap-abe-twl6040.txt

+1 −1
Original line number Diff line number Diff line
@@ -12,7 +12,7 @@ Required properties: 


Optional properties:

- ti,dmic: phandle for the OMAP dmic node if the machine have it connected

- ti,jack_detection: Need to be present if the board capable to detect jack

- ti,jack-detection: Need to be present if the board capable to detect jack

  insertion, removal.



Available audio endpoints for the audio-routing table:

Documentation/networking/dsa/dsa.txt

+2 −1
Original line number Diff line number Diff line
@@ -67,13 +67,14 @@ Note that DSA does not currently create network interfaces for the "cpu" and 
Switch tagging protocols

------------------------



DSA currently supports 4 different tagging protocols, and a tag-less mode as

DSA currently supports 5 different tagging protocols, and a tag-less mode as

well. The different protocols are implemented in:



net/dsa/tag_trailer.c: Marvell's 4 trailer tag mode (legacy)

net/dsa/tag_dsa.c: Marvell's original DSA tag

net/dsa/tag_edsa.c: Marvell's enhanced DSA tag

net/dsa/tag_brcm.c: Broadcom's 4 bytes tag

net/dsa/tag_qca.c: Qualcomm's 2 bytes tag



The exact format of the tag protocol is vendor specific, but in general, they

all contain something which: