solution (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:solution (Results 1 – 25 of 539) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...22

/kernel/liteos_m/arch/risc-v/nuclei/gcc/
D	los_arch_interrupt.h	77 …* Solution: Ensure that the interrupt number is valid. The value range of the interrupt number app… 88 * Solution: Pass in a valid non-null hardware interrupt handling function. 98 * Solution: Increase the configured maximum number of supported hardware interrupts. 108 * Solution: Expand the configured memory. 118 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 128 * Solution: Ensure that the interrupt priority is valid. 138 …* Solution: The interrupt creation mode can be only set to ECLIC_NON_VECTOR_INTERRUPT or ECLIC_VEC… 149 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 159 * * Solution: Do not call the API during an interrupt. 169 …* * Solution:check the input params hwiMode and irqParam of ArchHwiCreate or ArchHwiDelete whether… [all …]
/kernel/liteos_m/arch/risc-v/riscv32/gcc/
D	los_arch_interrupt.h	155 …* Solution: Ensure that the interrupt number is valid. The value range of the interrupt number app… 166 * Solution: Pass in a valid non-null hardware interrupt handling function. 176 * Solution: Increase the configured maximum number of supported hardware interrupts. 186 * Solution: Expand the configured memory. 196 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 206 * Solution: Ensure that the interrupt priority is valid. 216 …* Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or OS_HWI_MODE_FAST of… 227 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 237 * * Solution: Do not call the API during an interrupt. 247 …* * Solution:check the input params hwiMode and irqParam of ArchHwiCreate or ArchHwiDelete whether… [all …]
/kernel/liteos_a/kernel/include/
D	los_swtmr.h	56 * Solution: Define the timeout handling function. 66 * Solution: Re-define the expiration time. 76 * Solution: Check the mode value. The value range is [0,3]. 86 * Solution: Define the software timer ID before passing it in. 96 …* Solution: Re-configure the permitted maximum number of software timers, or wait for a software t… 107 * Solution: Pass in a valid software timer ID. 117 * Solution: Create a software timer. 127 * Solution: Allocate bigger memory partition to software timer linked list creation. 137 * Solution: Re-configure the number of software timers. 147 * Solution: Change the source code and do not use the software timer during an interrupt. [all …]
D	los_task.h	`78 * Solution: Allocate bigger memory partition to task creation. 88 * Solution: Check the parameter. 98 * Solution: Align the task stack. 108 * Solution: Re-configure the task priority by referring to the priority range. 118 * Solution: Define the task entrance function. 128 * Solution: Set the task name. 138 * Solution: Expand the task stack. 148 * Solution: Check the task ID. 158 * Solution: Suspend the task after it is resumed. 168 * Solution: Suspend the task. [all …]`
D	los_queue.h	55 …* Solution: Configure the maximum number of queue resources to be greater than 0. If queue modules… 66 …* Solution: Allocate the queue block bigger memory partition, or decrease the maximum number of qu… 76 …* Solution: Allocate more memory for queue creation, or decrease the queue length and the number o… 87 * Solution: Change the size of the biggest message in the created queue. 97 * Solution: Increase the configured number of resources for queues. 107 * Solution: Ensure that the passed-in queue ID is valid. 117 * Solution: Unlock the task before using a queue. 127 * Solution: Check whether the expiry time setting is appropriate. 137 * Solution: Enable the task to obtain resources rather than be blocked on the queue. 148 * Solution: Set the expiry time to the never-waiting mode, or use asynchronous queues. [all …]
D	los_sem.h	57 * Solution: Allocate more memory. 67 * Solution: Change the passed-in invalid parameter value to a valid value. 77 * Solution: Change the passed-in null pointer to a valid non-null pointer. 87 * Solution: Perform corresponding operations based on the requirements in the code context. 98 * Solution: Change the passed-in parameter value to a valid nonzero value. 108 * Solution: Do not call the API during an interrupt. 118 * Solution: Do not call LOS_SemPend when task scheduling is locked. 128 * Solution: Change the passed-in parameter value to the value within the valid range. 138 * Solution: Perform corresponding operations based on the requirements in the code context. 148 * Solution: Delete the semaphore after awaking all tasks that are waiting on the semaphore. [all …]
D	los_event.h	73 * Solution: Set bits excluding bit 25 of the event mask to events. 83 …* Solution: Increase the waiting time for event reading, or make another task write a mask for the… 93 * Solution: Pass in a valid EVENTMASK value. 103 * Solution: Read the event in a task. 116 * Solution: Pass in a valid flag value. 126 * Solution: Unlock the task and read the event. 136 * Solution: Check whether the input parameter is null. 146 * Solution: Read the event in a vailid task. 156 * Solution: Check whether the event list is not empty.
/kernel/liteos_m/arch/xtensa/lx6/gcc/
D	los_arch_interrupt.h	128 * Solution: Ensure that the interrupt number is valid. 138 * Solution: Pass in a valid non-null hardware interrupt handling function. 148 * Solution: Increase the configured maximum number of supported hardware interrupts. 158 * Solution: Expand the configured memory. 168 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 178 * Solution: Ensure that the interrupt priority is valid. 188 * Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or OS_HWI_MODE_FAST. 198 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be…
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/pm/powerplay/hwmgr/
D	ppevvmath.h	117 fInt solution = fPositiveOne; /Starting off with baseline of 1 / in fExponential() local 132 solution = fMultiply(solution, GetScaledFraction(expk_array[i], 10000)); in fExponential() 139 solution = fMultiply(solution, error_term); in fExponential() 142 solution = fDivide(fPositiveOne, solution); in fExponential() 144 return solution; in fExponential() 152 fInt solution = ConvertToFraction(0); /Starting off with baseline of 0 / in fNaturalLog() local 162 solution = fAdd(solution, GetScaledFraction(logk_array[i], 10000)); in fNaturalLog() 169 return (fAdd(solution, error_term)); in fNaturalLog() 542 fInt solution; in fRoundUpByStepSize() local 544 solution = fDivide(A, fStepSize); in fRoundUpByStepSize() [all …]
/kernel/liteos_m/kernel/include/
D	los_swtmr.h	55 * Solution: Define the timeout handling function. 65 * Solution: Re-define the expiration time. 75 * Solution: Check the mode value. The value range is [0,3]. 85 * Solution: Define the software timer ID before passing it in. 95 …* Solution: Re-configure the permitted maximum number of software timers, or wait for a software t… 106 * Solution: Pass in a valid software timer ID. 116 * Solution: Create a software timer. 126 * Solution: Allocate bigger memory partition to software timer linked list creation. 136 * Solution: Re-configure the number of software timers. 146 * Solution: Change the source code and do not use the software timer during an interrupt. [all …]
D	los_sem.h	54 * Solution: Allocate more memory. 64 * Solution: Change the passed-in invalid parameter value to a valid value. 74 * Solution: Change the passed-in null pointer to a valid non-null pointer. 84 * Solution: Perform corresponding operations based on the requirements in the code context. 95 * Solution: Change the passed-in parameter value to a valid nonzero value. 105 * Solution: Do not call the API during an interrupt. 115 * Solution: Do not call LOS_SemPend when task scheduling is locked. 125 * Solution: Change the passed-in parameter value to the value within the valid range. 135 * Solution: Perform corresponding operations based on the requirements in the code context. 145 * Solution: Delete the semaphore after awaking all tasks that are waiting on the semaphore. [all …]
D	los_queue.h	55 …* Solution: Configure the maximum number of queue resources to be greater than 0. If queue modules… 66 …* Solution: Allocate the queue block bigger memory partition, or decrease the maximum number of qu… 76 …* Solution: Allocate more memory for queue creation, or decrease the queue length and the number o… 87 * Solution: Change the size of the biggest message in the created queue. 97 * Solution: Increase the configured number of resources for queues. 107 * Solution: Ensure that the passed-in queue ID is valid. 117 * Solution: Unlock the task before using a queue. 127 * Solution: Check whether the expiry time setting is appropriate. 137 * Solution: Enable the task to obtain resources rather than be blocked on the queue. 148 * Solution: Set the expiry time to the never-waiting mode, or use asynchronous queues. [all …]
D	los_task.h	`58 * Solution: Allocate bigger memory partition to task creation. 68 * Solution: Check the parameter. 78 * Solution: Align the task stack. 88 * Solution: Re-configure the task priority by referring to the priority range. 98 * Solution: Define the task entrance function. 108 * Solution: Set the task name. 118 * Solution: Expand the task stack. 128 * Solution: Check the task ID. 138 * Solution: Suspend the task after it is resumed. 148 * Solution: Suspend the task. [all …]`
D	los_mux.h	54 * Solution: Decrease the number of mutexes defined by LOSCFG_BASE_IPC_MUX_LIMIT. 64 …* Solution: Check whether the mutex ID and the mutex state are applicable for the current operatio… 74 * Solution: Check whether the input parameter is usable. 84 * Solution: Increase the number of mutexes defined by LOSCFG_BASE_IPC_MUX_LIMIT. 94 * Solution: Lock the mutex after it is unlocked by the thread that owns it, or set a waiting time. 104 * Solution: Check whether the mutex is being locked during an interrupt. 115 * Solution: Check whether the task scheduling is disabled, or set timeout to 0, which means that the 126 * Solution: Increase the waiting time or set the waiting time to LOS_WAIT_FOREVER (forever-blocking… 144 * Solution: Delete the mutex after it is unlocked. 170 * Solution: LOS_ERRNO_MUX_MAXNUM_ZERO should not be zero. [all …]
D	los_event.h	72 * Solution: Set bits excluding bit 25 of the event mask to events. 81 …* Solution: Increase the waiting time for event reading, or make another task write a mask for the… 91 * Solution: Pass in a valid EVENTMASK value. 101 * Solution: Read the event in a task. 114 * Solution: Pass in a valid uwFlags value. 124 * Solution: Unlock the task and read the event. 134 * Solution: Check whether the input parameter is null. 144 * Solution: Check whether the event is initialized. 154 * Solution: Check whether the event list is not empty. 163 * Solution: Read the event in a valid task.
D	los_tick.h	`55 * Solution: Change values of the OS_SYS_CLOCK and LOSCFG_BASE_CORE_TICK_PER_SECOND 66 * Solution: None. 76 * Solution: Change values of the OS_SYS_CLOCK and LOSCFG_BASE_CORE_TICK_PER_SECOND 170 * Solution: Check whether the input parameter is null. 180 * Solution: Configure a valid system clock in los_config.h. 190 * Solution: None. 200 * Solution: None. 210 * Solution: None. 220 * Solution: None. 230 * Solution: None. [all …]`
/kernel/linux/linux-5.10/Documentation/hwmon/
D	sch5636.rst	`20 their own custom hwmon solution based upon the SCH5636. 23 hwmon solution. The sch5636 driver runs a sanity check on loading to ensure 25 hwmon solution. 32 The Fujitsu Theseus hwmon solution also contains an integrated watchdog.`
/kernel/linux/linux-5.10/arch/mips/lib/
D	bitops.c	`17 * set_bit() if it cannot find a faster solution. 38 * it cannot find a faster solution. 59 * if it cannot find a faster solution. 80 * called by test_and_set_bit_lock() if it cannot find a faster solution. 105 * called by test_and_clear_bit() if it cannot find a faster solution. 129 * called by test_and_change_bit() if it cannot find a faster solution.`
/kernel/liteos_a/arch/arm/include/
D	los_hwi.h	97 * Solution: Ensure that the interrupt number is valid. 107 * Solution: Pass in a valid non-null hardware interrupt handling function. 117 * Solution: Increase the configured maximum number of supported hardware interrupts. 127 * Solution: Expand the configured memory. 137 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 147 * Solution: Ensure that the interrupt priority is valid. 157 * Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or OS_HWI_MODE_FAST of 168 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 178 * * Solution: Do not call the API during an interrupt. 188 * * Solution: Check the input params hwiMode and irqParam of LOS_HwiCreate or [all …]
/kernel/liteos_m/arch/csky/v2/gcc/
D	los_arch_interrupt.h	137 * Solution: Ensure that the interrupt number is valid. 147 * Solution: Pass in a valid non-null hardware interrupt handling function. 157 * Solution: Increase the configured maximum number of supported hardware interrupts. 167 * Solution: Expand the configured memory. 177 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 187 * Solution: Ensure that the interrupt priority is valid. 197 * Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or OS_HWI_MODE_FAST. 207 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 217 * Solution: Ensure that the interrupt number is valid.
/kernel/linux/linux-5.10/Documentation/process/
D	3.Early-stage.rst	20 with the proposed solution, and that can lead to difficulties. 24 by excessive latency in the system. The solution they arrived at was a 38 The audio community, however, could not see past the particular solution 53 the right solution to the problem than they were with a specific module. 54 The moral of the story is to focus on the problem - not a specific solution 64 solution address? 87 - There may be elements of the proposed solution which will not be 92 problem; they may have ideas for a better solution, and may be willing 93 to help in the creation of that solution.
/kernel/liteos_m/arch/arm/arm9/gcc/
D	los_arch_interrupt.h	100 * Solution: Ensure that the interrupt number is valid. 111 * Solution: Pass in a valid non-null hardware interrupt handling function. 121 * Solution: Increase the configured maximum number of supported hardware interrupts. 131 * Solution: Expand the configured memory. 141 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be… 151 * Solution: Ensure that the interrupt priority is valid. 162 * Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or 173 …* Solution: Check whether the interrupt specified by the passed-in interrupt number has already be…
/kernel/linux/linux-5.10/drivers/mtd/maps/
D	solutionengine.c	`2 * Flash and EPROM on Hitachi Solution Engine and similar boards. 23 .name = "Solution Engine EPROM", 29 .name = "Solution Engine FLASH", 62 printk(KERN_NOTICE "Solution Engine: Flash at 0x%pap, EPROM at 0x%pap\n", in init_soleng_maps()`
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/cable/
D	sb1000.rst	`141 Solution 153 Solution 161 Solution 170 Solution 175 Solution 183 Solution 196 Solution`
/kernel/linux/linux-5.10/Documentation/kbuild/
D	Kconfig.recursion-issue-01	`37 # obvious that an easy to solution to this problem should just be the removal 41 # implications of this recursive issue where the solution is perhaps not so 43 # CORE also consist of a solution to this recursive problem.`

12 3 4 5 6 7 8 9 10 >>...22