Re: [meta-xilinx] Strange I2C problem after updating to Sumo

2019-01-20 Thread Peter Milne
Hi Mike On 01/12/2018 09:55, Mike Looijmans wrote: One thing you may want to try is replace the cadence I2C driver with the generic bit-bang GPIO driver (on the same pins). Example devicetree that does this in the kernel (you'll need to activate the bitbang gpio i2c driver in the kernel conf

Re: [meta-xilinx] Strange I2C problem after updating to Sumo

2018-12-06 Thread Martin Townsend
Hi Mike, Thanks for the reply, I'll give this a go. - Martin. On Sat, Dec 1, 2018 at 10:01 AM Mike Looijmans wrote: > One thing you may want to try is replace the cadence I2C driver with the > generic bit-bang GPIO driver (on the same pins). > > Example devicetree that does this in the kernel

Re: [meta-xilinx] Strange I2C problem after updating to Sumo

2018-12-01 Thread Mike Looijmans
One thing you may want to try is replace the cadence I2C driver with the generic bit-bang GPIO driver (on the same pins). Example devicetree that does this in the kernel (you'll need to activate the bitbang gpio i2c driver in the kernel config though): https://github.com/topic-embedded-product

[meta-xilinx] Strange I2C problem after updating to Sumo

2018-11-30 Thread Martin Townsend
Hi, We are in the process of upgrading to Sumo which has the 4.14 linux-xlnx kernel and everything is working fine except for our LTC-3375 regulator device driver which was working fine with the 4.9 kernel but with the newer kernel we are getting the following in the log. SW1: failed to get the c