To find gpiochip for non-OF platforms like x86
Signed-off-by: hongzha1
---
include/cobalt/kernel/rtdm/gpio.h | 3 +++
kernel/drivers/gpio/gpio-core.c | 23 +++
2 files changed, 26 insertions(+)
diff --git a/include/cobalt/kernel/rtdm/gpio.h
Measure response time to GPIO events sent by a remote Zephyr-based
latency monitor (latmon). This monitor collects then sends the latency
data over a network connection to the latmus front-end which displays
the results received:
[Linux device under test running latmus] <--+
To support the latmus application for determining the best
gravity values for the cobalt core clock, and measuring
the response time to timer events.
Signed-off-by: hongzha1
---
include/rtdm/uapi/testing.h | 63 ++
kernel/drivers/testing/Kconfig | 10 +
kernel/drivers/testing/Makefile
Latmus is a backport from EVL to Cobalt, the procedure is fully
described here: https://evlproject.org/core/benchmarks/
I verified all functions of latmus on hardware environment under which
Rock PI X board connect GPIOs with FRDM K64F.But actually Rock PI X V1.4
board's GPIO I/O voltage is 1.8V
:
<http://xenomai.org/pipermail/xenomai/attachments/20210420/690665c9/attachment.c>
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: DetailsLessLineWrapping.txt
URL:
<http://xenomai.org/pipermail/xenomai/attachments/20210420
Chen, Hongzhan via Xenomai writes:
>>-Original Message-
>>From: Jan Kiszka
>>Sent: Tuesday, April 20, 2021 2:48 PM
>>To: Chen, Hongzhan ; xenomai@xenomai.org
>>Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
>>
>>On 20.04.21 03:02, Chen, Hongzhan wrote:
>>>
>-Original Message-
>From: Jan Kiszka
>Sent: Tuesday, April 20, 2021 2:48 PM
>To: Chen, Hongzhan ; xenomai@xenomai.org
>Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
>
>On 20.04.21 03:02, Chen, Hongzhan wrote:
>>
>>
>>> -Original Message-
>>> From:
On 20.04.21 03:02, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Friday, April 16, 2021 8:05 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark
>>
>> On 16.04.21 07:31, hongzha1 via
From: chensong
Add a syscall specific for clock_nanosleep with 64bit
time_t.
Signed-off-by: chensong
---
v2:
1, new helper __cobalt_clock_nanosleep64
---
include/cobalt/uapi/syscall.h | 1 +
kernel/cobalt/posix/clock.c | 30 ++
kernel/cobalt/posix/clock.h
From: chensong
add test case for clock_nanosleep64 in testsuite
Signed-off-by: chensong
---
v2:
1, REALTIME --> MONOTONIC
2, more combinations
3, smokey warning in clock_gettime
4, remove magic number
---
testsuite/smokey/y2038/syscall-tests.c | 50 ++
1 file
From: chensong
new test case for clock_settime64 and clock_gettime64 and reorganize
run_2038.
If you want to trigger and verify y2038 problem, please be careful and
make sure it has no impact to your test device.
Signed-off-by: chensong
---
v3:
1, rename structs, variables
2, reorganize
From: chensong
Adding a new syscall clock_settime64 specific for timespec64,
It can solve y2038 in below scenarios:
1, 64bit kernel, 64bit process, no break. y2038 safe
2, 32bit kernel, 32bit process, 32bit time_t, go to clock_settime,
no break, y2038 not safe.
3, 32bit kernel, 32bit process,
From: chensong
Add a syscall specific for clock_gettime with 64bit
time_t.
Signed-off-by: chensong
---
v5:
1, new helper __cobalt_clock_gettime64
---
include/cobalt/kernel/time.h| 11 +++
include/cobalt/uapi/syscall.h | 1 +
kernel/cobalt/posix/clock.c | 23
13 matches
Mail list logo