Re: [PATCH 0/4] Add support for AM654 evm

Wed, 20 Mar 2019 07:52:46 -0700 


On 20/03/19 7:54 PM, Jan Kiszka wrote:
> On 20.03.19 15:19, Lokesh Vutla wrote:
>> Hi Jan,
>>
>> On 20/03/19 7:24 PM, Jan Kiszka wrote:
>>> On 20.03.19 13:47, Lokesh wrote:
>>>> From: Lokesh Vutla <[email protected]>
>>>>
>>>> The AM654 SoC is a lead device of the TI's K3 Multicore SoC architecture
>>>> platform, targeted for broad market and industrial control with aim to
>>>> meet the complex processing needs of modern embedded products.
>>>>
>>>> This series add support for the AM654 based board to Jailhouse.
>>>>
>>>> Kernel used: 
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
>>>
>>> What is the minimum version needed? 5.1-rc1?
>>
>> 5.0 should do for basic boot. But mmc fs is still not ready in upstream 
>> because
>> of some erratas.
> 
> Means you were booting from network when testing this with upstream?

As shown in the logs, u-boot is loading images from network. But kernel FS is
still ramdisk. I know you are not happy with this support :)

> 
>>
>>>
>>>> U-boot used: 
>>>> http://git.ti.com/cgit/cgit.cgi/ti-u-boot/ti-u-boot.git/log/?h=ti-u-boot-2019.01
>>>>
>>>> It is assumed that for uart and gic demos, the mcu uart0 power-domain and
>>>> pinmux is enabled by u-boot.
>>>
>>> How is that ensured?
>>
>> U-Boot definitely enables it all the time as it is used for very early 
>> debug. If
>> we do not want to depend on u-boot then hypervisor should take care of two 
>> things:
>> - Pinmux
>> - Enabling power-domain which is done by calling a sysfw api.
>>
>> Not sure how we can handle this. So I have this assumption.
> 
> OK, I see. So this is just documenting a currently automatically fulfilled
> assumption.

Right.

Thanks and regards,
Lokesh


> 
> Jan
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.






















					Reply via email to