It's up to you. I think if the NV guys are ok with the tegra i2c change,
Wolfram can merge it right away for 4.3.
I asked him to resend, because I *want* to merge it for 4.3 :) Only the
slave-mode enablement for i2c, of course. The other patches need to go
via some other tree (when they are
On 21.07.2015 1:19, Stephen Warren wrote:
On 07/20/2015 02:35 PM, Andrey Danin wrote:
NVEC driver was reimplemented to use tegra i2c. Use common i2c bindings
for NVEC node.
diff --git a/arch/arm/boot/dts/tegra20-paz00.dts
b/arch/arm/boot/dts/tegra20-paz00.dts
+nvec: nvec@45 {
+
Am Dienstag, 21. Juli 2015, 09:35:21 schrieb Andrey Danin:
On 21.07.2015 1:19, Stephen Warren wrote:
On 07/20/2015 02:35 PM, Andrey Danin wrote:
NVEC driver was reimplemented to use tegra i2c. Use common i2c bindings
for NVEC node.
diff --git a/arch/arm/boot/dts/tegra20-paz00.dts
Am Dienstag, 21. Juli 2015, 11:51:15 schrieb Andrey Danin:
On 21.07.2015 11:25, Marc Dietrich wrote:
I think in this case it would be better to leave nvec and dt as it is for
now, and just add the slave function to tegra-i2c. Otherwise we will
again have two different nvidia,nvec-slave
On 21.07.2015 11:25, Marc Dietrich wrote:
I think in this case it would be better to leave nvec and dt as it is for now,
and just add the slave function to tegra-i2c. Otherwise we will again have two
different nvidia,nvec-slave bindings (one for the intermediate hack and one
for the final
NVEC driver was reimplemented to use tegra i2c. Use common i2c bindings
for NVEC node.
Signed-off-by: Andrey Danin danind...@mail.ru
---
No changes for v3:
Changes for v2:
- swap reg and request-gpios properties
- use nvec-slave instead of nvec to keep ABI compatibility
- place doc in separate
On 07/20/2015 02:35 PM, Andrey Danin wrote:
NVEC driver was reimplemented to use tegra i2c. Use common i2c bindings
for NVEC node.
diff --git a/arch/arm/boot/dts/tegra20-paz00.dts
b/arch/arm/boot/dts/tegra20-paz00.dts
+ nvec: nvec@45 {
+ compatible =
