Pull in char-misc-next from Greg

							cpld3_version

Date:		November 2018

KernelVersion:	4.21

KernelVersion:	5.0

Contact:	Vadim Pasternak <vadimpmellanox.com>

Description:	These files show with which CPLD versions have been burned

		on LED board.

							jtag_enable

Date:		November 2018

KernelVersion:	4.21

KernelVersion:	5.0

Contact:	Vadim Pasternak <vadimpmellanox.com>

Description:	These files enable and disable the access to the JTAG domain.

		By default access to the JTAG domain is disabled.

						reset_voltmon_upgrade_fail

Date:		November 2018

KernelVersion:	4.21

KernelVersion:	5.0

Contact:	Vadim Pasternak <vadimpmellanox.com>

Description:	These files show the system reset cause, as following: ComEx

		power fail, reset from ComEx, system platform reset, reset

			By default, super page will be supported if Intel IOMMU

			has the capability. With this option, super page will

			not be supported.

		sm_off [Default Off]

			By default, scalable mode will be supported if the

		sm_on [Default Off]

			By default, scalable mode will be disabled even if the

			hardware advertises that it has support for the scalable

			mode translation. With this option set, scalable mode

			will not be used even on hardware which claims to support

			it.

			will be used on hardware which claims to support it.

		tboot_noforce [Default Off]

			Do not force the Intel IOMMU enabled under tboot.

			By default, tboot will force Intel IOMMU on, which

* PTN5150 CC (Configuration Channel) Logic device

PTN5150 is a small thin low power CC logic chip supporting the USB Type-C

connector application with CC control logic detection and indication functions.

It is interfaced to the host controller using an I2C interface.

Required properties:

- compatible: should be "nxp,ptn5150"

- reg: specifies the I2C slave address of the device

- int-gpio: should contain a phandle and GPIO specifier for the GPIO pin

	connected to the PTN5150's INTB pin.

- vbus-gpio: should contain a phandle and GPIO specifier for the GPIO pin which

	is used to control VBUS.

- pinctrl-names : a pinctrl state named "default" must be defined.

- pinctrl-0 : phandle referencing pin configuration of interrupt and vbus

	control.

Example:

	ptn5150@1d {

		compatible = "nxp,ptn5150";

		reg = <0x1d>;

		int-gpio = <&msmgpio 78 GPIO_ACTIVE_HIGH>;

		vbus-gpio = <&msmgpio 148 GPIO_ACTIVE_HIGH>;

		pinctrl-names = "default";

		pinctrl-0 = <&ptn5150_default>;

		status = "okay";

	};

Interconnect Provider Device Tree Bindings

=========================================

The purpose of this document is to define a common set of generic interconnect

providers/consumers properties.

= interconnect providers =

The interconnect provider binding is intended to represent the interconnect

controllers in the system. Each provider registers a set of interconnect

nodes, which expose the interconnect related capabilities of the interconnect

to consumer drivers. These capabilities can be throughput, latency, priority

etc. The consumer drivers set constraints on interconnect path (or endpoints)

depending on the use case. Interconnect providers can also be interconnect

consumers, such as in the case where two network-on-chip fabrics interface

directly.

Required properties:

- compatible : contains the interconnect provider compatible string

- #interconnect-cells : number of cells in a interconnect specifier needed to

			encode the interconnect node id

Example:

		snoc: interconnect@580000 {

			compatible = "qcom,msm8916-snoc";

			#interconnect-cells = <1>;

			reg = <0x580000 0x14000>;

			clock-names = "bus_clk", "bus_a_clk";

			clocks = <&rpmcc RPM_SMD_SNOC_CLK>,

				 <&rpmcc RPM_SMD_SNOC_A_CLK>;

		};

= interconnect consumers =

The interconnect consumers are device nodes which dynamically express their

bandwidth requirements along interconnect paths they are connected to. There

can be multiple interconnect providers on a SoC and the consumer may consume

multiple paths from different providers depending on use case and the

components it has to interact with.

Required properties:

interconnects : Pairs of phandles and interconnect provider specifier to denote

	        the edge source and destination ports of the interconnect path.

Optional properties:

interconnect-names : List of interconnect path name strings sorted in the same

		     order as the interconnects property. Consumers drivers will use

		     interconnect-names to match interconnect paths with interconnect

		     specifier pairs.

Example:

	sdhci@7864000 {

		...

		interconnects = <&pnoc MASTER_SDCC_1 &bimc SLAVE_EBI_CH0>;

		interconnect-names = "sdhc-mem";

	};

Qualcomm SDM845 Network-On-Chip interconnect driver binding

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

SDM845 interconnect providers support system bandwidth requirements through

RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is

able to communicate with the BCM through the Resource State Coordinator (RSC)

associated with each execution environment. Provider nodes must reside within

an RPMh device node pertaining to their RSC and each provider maps to a single

RPMh resource.

Required properties :

- compatible : shall contain only one of the following:

			"qcom,sdm845-rsc-hlos"

- #interconnect-cells : should contain 1

Examples:

apps_rsc: rsc {

	rsc_hlos: interconnect {

		compatible = "qcom,sdm845-rsc-hlos";

		#interconnect-cells = <1>;

	};

};