Yes, this is a Hikey issue.
It's good to know that you are giving the UARTs some thought.
Let me clarify our use case:
We have a hypervisor that will run two guests.
We want to direct log prints for ATF and Hypervisor to one UART and the two guests to a UART each.
This is desirable both for readability- and isolation purposes.
Also, we plan to patch ATF with needed modifications to control UART configuration.
If Jerome's hints leads to a fix we will also patch start.S.
________________________________ Från: Grant Likely [email@example.com] Skickat: den 16 september 2015 09:10 Till: Stefan Johansson Kopia: dev [firstname.lastname@example.org] Ämne: Re: [Dev] SoC UART2
On 8 Sep 2015 10:35, "Stefan Johansson" <email@example.com:firstname.lastname@example.org> wrote:
We would need to use UART2 in final stages of A-T-F. (UART0 and UART3 works fine)
(I'm assuming you're talking about hikey here)
Out of curiosity, what do you plan to use ttyAMA2 for? I ask because we're talking about better defining how the UARTs are expected to be used so that mezzanine boards can be designed consistently.
We're settling on specifying UART1 (ttyAMA3 on HiKey) as the console and UART0 (ttyAMA2) as peripheral IO. If ATF takes over ttyAMA2 by default then it will not be available for peripherals.
Thoughts? Is this something you want by default, or an option for specific use cases? What are your expected use cases?