CHAMPION-147
Three sensor types (ecg, ppg and impd) had been added in sensor.h(http://git.xiaomi.com/c/miot/mirtos/nuttx/+/813239), while they had not been added to sensor.c, causing that a sensor of these 3 types can't be registered. This fixes it.
Change-Id: I313b9bdc621d91b0ff934ca8322270fd6552948b
Signed-off-by: liucheng5 <liucheng5@xiaomi.com>
and remove the batsem initialization since it is arleady done in common code
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
Change-Id: I6561eb53f3211edae8f699fbf9d7625689ee581c
CHAMPION-91
change FBIOPAN_DISPLAY IOCTL command to _FBIOC(0x0016).
change xoffest to xoffset in fb_planeinfo_s.
modify comments for xoffset and yoffset in fb_planeinfo_s.
add comment for pandisplay interface.
Signed-off-by: liushuai25 <liushuai25@xiaomi.com>
Change-Id: Idb7805dd9691b849f19e3d7010bcfabbaa48797b
THOR-208
As before commit 070ad15f14 and 1621fcb09e
Fix issue about CPU affinity, But these two comments don't
update comment. Github version updated that. So sync it.
Signed-off-by: chenhonglin <chenhonglin@xiaomi.com>
Change-Id: Ie5abf10893e66334d3dd9939bd85f2a40741a2c5
so the userspace program can handle the different battery driver equally
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
Change-Id: Ib00bb6bd6c543c01cb0ed03bc631ec8337720528
MIRTOS-1055
when enable SYSTEM_TIME64, tick may exceed the int32 range
example:
pthread_cond_clockwait
---->clock_abstime2ticks
---->wd_start
Change-Id: Id6b8f9e92cbcad285c8fa684a73b7d75a8ccfebc
Signed-off-by: Jiuzhu Dong <dongjiuzhu1@xiaomi.com>
THOR-208
In "nxsched_nexttcb": the task may not running on this_cpu,
and rtrtcb->affinity(the affinity of the task in g_readytorun)
may not include the current cpu which should be the tcb->cpu.
Signed-off-by: chenhonglin <chenhonglin@xiaomi.com>
Change-Id: I2523c9431b480a3afeb29a9260804c5b37e91d4b
THOR-208
In "nxsched_remove_readytorun":
the logical may choose the head of g_readytorun(the greatest priority)
task as the next while ignoring the cpu affinity of it.
Signed-off-by: chenhonglin <chenhonglin@xiaomi.com>
Change-Id: I819dd6f3fc0feff4e378cfda2a6c581814065cb3
CHAMPION-25
fix commit miss to delete the config of battery fuel gauge CW2218
Signed-off-by: zhangguoliang <zhangguoliang3@xiaomi.com>
Change-Id: I2b6fdfcdc8d3ce35a91defe9fa6a5d76681d5f8b
The resulting time complexities are as follows:
* devif_callback_alloc() time complexity is O(1) (i.e. O(n) to fill the whole list).
* devif_callback_free() time complexity is O(1) (i.e. O(n) to empty the whole list).
* devif_conn_event() time complexity is O(n).
Change-Id: Id43218407bfd67659bbf5daf40b1d096ea201e45
Signed-off-by: chao.an <anchao@xiaomi.com>
In case of enabled packet forwarding mode, packets were forwarded in a reverse order
because of LIFO behavior of the connection event list.
The issue exposed only during high network traffic. Thus the event list started to grow
that resulted in changing the order of packets inside of groups of several packets
like the following: 3, 2, 1, 6, 5, 4, 8, 7 etc.
Remarks concerning the connection event list implementation:
* Now the queue (list) is FIFO as it should be.
* The list is singly linked.
* The list has a head pointer (inside of outer net_driver_s structure),
and a tail pointer is added into outer net_driver_s structure.
* The list item is devif_callback_s structure.
It still has two pointers to two different list chains (*nxtconn and *nxtdev).
* As before the first argument (*dev) of the list functions can be NULL,
while the other argument (*list) is effective (not NULL).
* An extra (*tail) argument is added to devif_callback_alloc()
and devif_conn_callback_free() functions.
* devif_callback_alloc() time complexity is O(1) (i.e. O(n) to fill the whole list).
* devif_callback_free() time complexity is O(n) (i.e. O(n^2) to empty the whole list).
* devif_conn_event() time complexity is O(n).
Change-Id: I1123657f9a591b29f2a7546691d58dff58896a18
Signed-off-by: chao.an <anchao@xiaomi.com>