Re: [meta-xilinx] Kernel version, xilinx git repo, yocto kernel

2019-04-05 Thread Mike Looijmans
On 04-04-19 14:03, Arno Steffens wrote:
> 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.

Well if you need recovery, something is broken on the bus...

> I'll check the bitbang option. Do I have to expect performance/timing issues?
> I guess I have to adjust devicetree for that too? Phu. Thats always magic 
> to me.
> Kind regards, Arno

Here's our devicetree that sets up the bitbank stuff:

https://github.com/topic-embedded-products/linux/blob/topic-miami/arch/arm/boot/dts/topic-miami.dtsi

Don't forget to activate the bitbang GPIO I2C driver in the "drivers" section 
of the kernel configuration as well.

> 
>> Gesendet: Donnerstag, 04. April 2019 um 07:31 Uhr
>> Von: "Mike Looijmans" 
>> An: "Arno Steffens" , "meta xilinx" 
>> 
>> 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
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] [meta-xilinx-bsp][RFC] kernel-module-mali: Fix errors associated with kernel upgrade to 4.19

2019-04-05 Thread Jean-Francois Dagenais



> On Apr 4, 2019, at 16:19, Madhurkiran Harikrishnan  
> wrote:
> 
> Hi JFD,
> 
> It is trying to reset the PP, and fails. Can you check if the power islands 
> are turned on. 
> 
> Can you tell me the output of the following:
> Devmem 0xFD4B006C
> Devmem 0xFD4B4004

Thanks for the support guys. I had to revert back to 4.14 for the time being.

I will get back on this in a bit and test this. Bear with me.

Talk in a couple of days...
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] [meta-xilinx-bsp][RFC] kernel-module-mali: Fix errors associated with kernel upgrade to 4.19

2019-04-05 Thread Manjukumar Harthikote Matha
Hi JFD,

> -Original Message-
> From: Jean-Francois Dagenais [mailto:jeff.dagen...@gmail.com]
> Sent: Monday, April 1, 2019 1:45 PM
> To: Manjukumar Harthikote Matha 
> Cc: meta-xilinx@yoctoproject.org; Madhurkiran Harikrishnan
> 
> Subject: Re: [meta-xilinx] [meta-xilinx-bsp][RFC] kernel-module-mali: Fix
> errors associated with kernel upgrade to 4.19
> 
> 
> 
> > On Apr 1, 2019, at 16:36, Jean-Francois Dagenais
>  wrote:
> >
> >> We don't see the issue with above tree and the RFC patches.
> >>
> >
> > Any idea where to start? Could it be related to our handoff file?
> >
> 
> Or something missing in my defconfig? Is ./configs/xilinx_zynqmp_defconfig
> kept up to date in the kernel tree?

This is up to date 

> 
> For example, comparing zynqmp_defconfig changes from 4.14 to master, I
> see I am missing ZYNQMP_RESET_CONTROLLER.
> 
> I will check for more discrepancies, but any pointers from this community will
> help a lot.


Were you able to solve this? I am not seeing this issue in our builds.

> 
> Thanks again.
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx