~hc/RK356X_SDK_RELEASE.git

..	..	@@ -35,6 +35,12 @@
35	35	Due to above changes, Tegra114 I2C driver makes incompatible with
36	36	previous hardware driver. Hence, tegra114 I2C controller is compatible
37	37	with "nvidia,tegra114-i2c".
	38	+ nvidia,tegra210-i2c-vi: Tegra210 has one I2C controller that is on host1x bus
	39	+ and is part of VE power domain and typically used for camera use-cases.
	40	+ This VI I2C controller is mostly compatible with the programming model
	41	+ of the regular I2C controllers with a few exceptions. The I2C registers
	42	+ start at an offset of 0xc00 (instead of 0), registers are 16 bytes
	43	+ apart (rather than 4) and the controller does not support slave mode.
38	44	- reg: Should contain I2C controller registers physical address and length.
39	45	- interrupts: Should contain I2C controller interrupts.
40	46	- address-cells: Address cells for I2C device address.
..	..	@@ -47,10 +53,17 @@
47	53	- fast-clk
48	54	Tegra114:
49	55	- div-clk
	56	+ Tegra210:
	57	+ - div-clk
	58	+ - slow (only for nvidia,tegra210-i2c-vi compatible node)
50	59	- resets: Must contain an entry for each entry in reset-names.
51	60	See ../reset/reset.txt for details.
52	61	- reset-names: Must include the following entries:
53	62	- i2c
	63	+- power-domains: Only for nvidia,tegra210-i2c-vi compatible node and must
	64	+ include venc powergate node as vi i2c is part of VE power domain.
	65	+ tegra210-i2c-vi:
	66	+ - pd_venc
54	67	- dmas: Must contain an entry for each entry in clock-names.
55	68	See ../dma/dma.txt for details.
56	69	- dma-names: Must include the following entries: