Hey guys,
On Tue, Jun 06, 2017 at 03:24:38PM +0100, Neil Williams wrote:
On 6 June 2017 at 14:32, Vincent Guittot vincent.guittot@linaro.org wrote:
...
arm-probe supports multi AEP and we are using with multi AEPs with the mtk8173 evb. arm-probe just rely of the config file to get the path of the AEP. I have put the content of the config file below:
# arm-probe configuration file # # setup name mt8173-evb
# <device path> /dev/serial/by-id/usb-NXP_SEMICOND_ARM_Energy_Probe_S_NO81730001-if00 VDD_CA57_0 0.500000 1 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A57/Cache A57_CACHE #ff0000 SoC VDD_CA57_1 0.100000 2 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A57/Core0 A57_CORE #ff0000 SoC VDD_CA57_2 0.100000 3 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A57/Core1 A57_CORE #ff0000 SoC
/dev/serial/by-id/usb-NXP_SEMICOND_ARM_Energy_Probe_S_NO81730000-if00 VDD_CA53_0 0.500000 1 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A53/Cache A53_CACHE #ff0000 SoC VDD_CA53_1 0.100000 2 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A53/Core0 A53_CORE #ff0000 SoC VDD_CA53_2 0.100000 3 -0.179000 13.363000 -0.000000 0.163300 0 SoC/A53/Core1 A53_CORE #ff0000 SoC
Vincent: how have you configured your tests with these specific /dev paths? Are your tests set up to only use specific test boards with a specific arm-probe config file (device tags?), or are you generating the config file somehow for each test?
At the moment, in LAVA we're passing the appropriate /dev/ttyACMx device node into the LXC as we start things up. That's clearly not going to scale here once you're wanting to use more than one AEP in a single test. So, I'm working on this right now. *Hopefully* I'll be able to replicate the /dev/serial/by-id paths - I'll update you shortly.
I don't catch why the config file is insane and how this will help for this problem
If the config file is to be generated for each test job, the syntax is awkward to handle as it would need a line inserted instead of supporting a parser or similar.
*nod* IMHO this is not a great design for the config file, but let's see what we can do.
...
Note also that physically fitting more AEPs will involve work by the LAB team - especially for devices like the panda, because the power connector which comes with the AEP does not fit the panda and a one-off daughter board is required.
This is something that has been already handled and in the case of the mt8173evb everything is already done and working on our server with current arm-probe, AEPs and workload automation
OK, cool.
Cheers,