Thanks Mike for this clear (and surprising) words.
The reason I thought it might help is that functions like this 
(cdns_i2c_init_recovery_info) has been added.
I'll check the bitbang option. Do I have to expect performance/timing issues?
I guess I have to adjust devicetree for that too? Phuuuuu. Thats always magic 
to me.
Kind regards, Arno

> Gesendet: Donnerstag, 04. April 2019 um 07:31 Uhr
> Von: "Mike Looijmans" <[email protected]>
> An: "Arno Steffens" <[email protected]>, "meta xilinx" 
> <[email protected]>
> Betreff: Re: [meta-xilinx] Kernel version, xilinx git repo, yocto kernel
>
> Simple solution would be to just stop using the cadence driver. There are
> issues in the Zynq that cannot really be resolved in software apparently, and
> the only way around them we've found is to just use a bitbang GPIO controller
> on the same pins. That made all problems go away.
>
> Chances are that moving to a newer kernel will not resolve your I2C issues 
> anyway.
>
> On 03-04-19 13:53, Arno Steffens wrote:
> > I need a more recent kernel (Zynq 7000) and wondering, what can I do.
> > Why I am looking for that?
> > I have I2C issues and guess I need the recovery functionality, but the 
> > Cadence I2c driver that supports it is only in the current xilinx master 
> > branch. Even not in mainline 4.19.
> >
> > Before this I2C issue popped up I took a kernel.org LTS kernel and 
> > patch/take over the qspi/dma stuff that I need from the xilinx kernel. But 
> > this time it will not work. What would you recommend me?
> >
> > Just take to master branch? That will probably never work with RT patches 
> > ...
> > The xlx-kernel - Which kernel-org version it is based on?
> >
> > Best regards, Arno
> >
>
>
-- 
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to