Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-04-10 Thread Bin Meng
Hi Vasyl, On Tue, Apr 10, 2018 at 5:16 PM, Vasyl Vavrychuk wrote: > Without armv8_setup_psci register VBAR_EL3 is not set up property which > makes SMC calls jump to invalid location. > > smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. >

[U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-04-10 Thread Vasyl Vavrychuk
Without armv8_setup_psci register VBAR_EL3 is not set up property which makes SMC calls jump to invalid location. smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. Without this they will never pursue booting process. Fix was applied to the two ways of booting

Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-04-02 Thread Vasyl Vavrychuk
Hi Bin, On Sun, Apr 1, 2018 at 4:51 PM, Bin Meng wrote: > > Why I mentioned the 'bootm' command, is that AFAIK the only official > way of booting a VxWorks 7 ARM kernel is to use 'bootm'. Are you > saying that 'bootm' command does not work on your Intel Stratix 10 > DevKit

[U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-04-02 Thread Vasyl Vavrychuk
Without armv8_setup_psci register VBAR_EL3 is not set up property which makes SMC calls jump to invalid location. smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. Without this they will never pursue booting process. Fix was applied to the two ways of booting

Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-04-01 Thread Bin Meng
Hi Vasyl, On Wed, Mar 28, 2018 at 7:27 PM, Vasyl Vavrychuk wrote: > Hi, Bin Meng, > > Thanks for your suggestions. Please find my comments below > > On Wed, Mar 28, 2018 at 7:36 AM, Bin Meng wrote: >> >> > >> > Tested on VxWorks 7 release

Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-03-28 Thread Vasyl Vavrychuk
Hi, Bin Meng, Thanks for your suggestions. Please find my comments below On Wed, Mar 28, 2018 at 7:36 AM, Bin Meng wrote: > > > > > Tested on VxWorks 7 release SR0520 2017-12-08. > > > > On what board? Intel Stratix 10 DevKit > As I mentioned before, why do you want to use

Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-03-27 Thread Bin Meng
Hi Vasyl, On Wed, Mar 28, 2018 at 3:29 AM, Vasyl Vavrychuk wrote: > Without armv8_setup_psci register VBAR_EL3 is not set up property which > makes SMC calls jump to invalid location. > > smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. >

[U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-03-27 Thread Vasyl Vavrychuk
Without armv8_setup_psci register VBAR_EL3 is not set up property which makes SMC calls jump to invalid location. smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. Without this they will never pursue booting process. This implementation is very similiar to what is

Re: [U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-03-27 Thread Bin Meng
Hi Vasyl, On Mon, Mar 26, 2018 at 3:58 PM, Vasyl Vavrychuk wrote: > Without armv8_setup_psci register VBAR_EL3 is not set up properly which > makes SMC calls jump to invalid location. > > smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. >

[U-Boot] [PATCH] vxworks: fixed cpu enable using PSCI on armv8

2018-03-27 Thread Vasyl Vavrychuk
Without armv8_setup_psci register VBAR_EL3 is not set up properly which makes SMC calls jump to invalid location. smp_kick_all_cpus is required to make slave cpus leave gic_wait_for_interrupt. Without this they will never pursue booting process. This implementation is very similiar to what is