On 02/06/2018 03:15 PM, Volodymyr Babchuk wrote:
Hi Julien,
Hi,
On 06.02.18 16:53, Julien Grall wrote:
On 02/02/2018 01:46 PM, Volodymyr Babchuk wrote:
On 02.02.18 13:41, Julien Grall wrote:
The current implementation of SMCCC relies on the fact only function
number (bits [15:0]) is
Hi Julien,
On 06.02.18 16:53, Julien Grall wrote:
Hi Volodymyr,
On 02/02/2018 01:46 PM, Volodymyr Babchuk wrote:
On 02.02.18 13:41, Julien Grall wrote:
The current implementation of SMCCC relies on the fact only function
number (bits [15:0]) is enough to identify what to implement.
Hi Volodymyr,
On 02/02/2018 01:46 PM, Volodymyr Babchuk wrote:
On 02.02.18 13:41, Julien Grall wrote:
The current implementation of SMCCC relies on the fact only function
number (bits [15:0]) is enough to identify what to implement.
However, PSCI call are only available in the range
On 02.02.18 13:41, Julien Grall wrote:
The current implementation of SMCCC relies on the fact only function
number (bits [15:0]) is enough to identify what to implement.
However, PSCI call are only available in the range 0x8400-0x841F
and 0xC400-0xC41F. Furthermore, not all
The current implementation of SMCCC relies on the fact only function
number (bits [15:0]) is enough to identify what to implement.
However, PSCI call are only available in the range 0x8400-0x841F
and 0xC400-0xC41F. Furthermore, not all SMC32 functions have
equivalent in the SMC64.
