generally (full) in projects: OK3568_Linux_fs

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:generally (Results 1 – 25 of 1462) sorted by relevance

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

/OK3568_Linux_fs/kernel/Documentation/driver-api/media/
H A D	camera-sensor.rst	`15 divisors. The clock tree is generally configured by the driver based on a few 17 and the link frequency. The two parameters generally are obtained from system 45 Register list based drivers generally, instead of able to configure the device 95 level interface natively, generally use the concept of frame interval (or frame`
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-other.json	557 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 569 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 581 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 593 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 605 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 617 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 629 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 641 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… 845 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… 857 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-other.json	578 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 602 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 614 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 626 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 638 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 650 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 662 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… 866 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… 878 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… [all …]
/OK3568_Linux_fs/kernel/Documentation/power/
H A D	suspend-and-interrupts.rst	`12 Device interrupt request lines (IRQs) are generally disabled during system 61 System wakeup interrupts generally need to be configured to wake up the system 72 After wakeup, it generally is better to disable that input to prevent the 128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally`
H A D	freezing-of-tasks.rst	`36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally 104 Generally speaking, there is a couple of reasons to use the freezing of tasks: 123 devices are deactivated, because we generally need them for swapping out. 206 tasks, since it generally exists anyway.`
/OK3568_Linux_fs/kernel/Documentation/core-api/
H A D	bus-virt-phys-mapping.rst	`48 not generally necessarily true on other PCI/ISA setups. 125 And you generally never want to use the physical address, because you can't 143 memory" on the PCI or ISA bus. That's generally not RAM (although in the case 213 It's generally not hard to fix drivers, and in many cases the code`
/OK3568_Linux_fs/u-boot/arch/mips/lib/
H A D	reloc.c	`98 * relocate_code() - Relocate U-Boot, generally from flash to DDR 103 * Relocate U-Boot from its current location (generally in flash) to a new one 104 * (generally in DDR). This function will copy the U-Boot binary & apply`
/OK3568_Linux_fs/buildroot/docs/manual/
H A D	rebuilding-packages.txt	`25 generally is needed. Changing the toolchain configuration often 50 package. However, generally you don't necessarily need this package 78 Generally speaking, when you're facing a build error and you're unsure`
/OK3568_Linux_fs/u-boot/doc/
H A D	README.kconfig	`109 When adding a new board, the following steps are generally needed: 125 It is generally placed at board/<board>/MAINTAINERS or 129 When removing an obsolete board, the following steps are generally needed:`
/OK3568_Linux_fs/u-boot/include/configs/
H A D	ti_armv7_common.h	`103 * large malloc pool as we generally have a lot of DDR, and we opt for 105 * generally easily constrained later if needed. We enable the config 138 * SPL framework found under common/spl/. Given our generally common memory`
/OK3568_Linux_fs/kernel/drivers/soc/rockchip/fiq_debugger/
H A D	fiq_debugger.h	`38 * @uart_dev_suspend: called during PM suspend, generally not needed 40 * @uart_dev_resume: called during PM resume, generally not needed`
/OK3568_Linux_fs/kernel/Documentation/admin-guide/pm/
H A D	intel_pstate.rst	81 names of some of those governors. Moreover, confusingly enough, they generally 182 registers of the CPU. It generally selects P-states proportional to the 266 In turn, the P-states below the turbo threshold generally are sustainable. In 273 but the maximum P-state that can be set for them generally depends on the number 291 generally causes turbo P-states to be set more often when ``intel_pstate`` is 320 Generally, ways to obtain that information are specific to the processor model 449 and it generally depends on the driver's `operation mode <Operation Modes_>`_. 700 diagnostics. One of them is the ``cpu_frequency`` trace event generally used 706 their output (if the kernel is generally configured to support event tracing)::
H A D	cpufreq.rst	42 the utilization of the system generally changes over time, that has to be done 160 scheduler tick or generally whenever the CPU utilization may change (from the 215 and their behavior generally does not depend on what scaling driver is in use 388 generally is regarded as a part of the CPU scheduler, so it can access the 430 This governor generally is regarded as a replacement for the older `ondemand`_ 460 It generally selects CPU frequencies proportional to the estimated load, so that 702 The frequency boost mechanism is generally intended to help to achieve optimum 713 conditions. Generally, the processor's energy consumption increases
H A D	cpuidle.rst	19 Modern processors are generally able to enter states in which the execution of 24 generally allows power drawn by the processor to be reduced and, in consequence, 40 physically. Generally, three different cases can be consider here. 153 (in particular, before the closest timer triggers) and it generally is not known 255 generally regarded as more energy-efficient than the systems running kernels in 417 generally happens if the target residency of the idle state selected so far is 560 hierarchy of units in the processor, and it generally is hard to obtain idle 565 The number in the :file:`time` file generally may be greater than the total time 579 Generally, an interrupt received when trying to enter an idle state causes the
/OK3568_Linux_fs/external/xserver/doc/
H A D	c-extensions	`24 * _X_INLINE: inline this function if possible (generally obeyed unless 67 OSX support is generally limited to the most recent version. Currently`
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/
H A D	target-hooks-macros.h	`50 /* A hook should generally be documented by a string in the DOC parameter, 69 and is mainly used internally for DEFHOOK_UNDOC. It should generally not`
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/
H A D	target-hooks-macros.h	`50 /* A hook should generally be documented by a string in the DOC parameter, 69 and is mainly used internally for DEFHOOK_UNDOC. It should generally not`
/OK3568_Linux_fs/kernel/Documentation/vm/
H A D	active_mm.rst	`76 should generally just do 81 we have a user context", and is generally done by the page fault handler`
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/location/doc/src/plugins/
H A D	places-backend.qdoc	`97 A place generally cannot be saved directly between managers as is because it contains manager speci… 123 be displayed to users. \note It is generally expected that all managers should set the \c x_provid… 146 Generally however it is recommended that cross referencing be implemented via alternative identifie…`
/OK3568_Linux_fs/buildroot/package/elf2flt/
H A D	0001-ld-elf2flt-behave-properly-when-called-with-a-name-d.patch	`9 1 It is called as the wrapper for <TARGET_ALIAS>-ld, generally 12 2 It is called as the wrapper for "ld", generally installed in the`
/OK3568_Linux_fs/kernel/Documentation/i2c/busses/
H A D	i2c-ali15x3.rst	`61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't 121 SMBus. Therefore the SMBus hangs can generally be avoided`
/OK3568_Linux_fs/kernel/Documentation/driver-api/pm/
H A D	devices.rst	57 However, devices are not generally independent of each other (for 200 by the bus type (or generally subsystem) code using :c:func:`pm_runtime_allow()` 401 vectors, like PCI, generally need it; otherwise a driver might encounter 432 generally means undoing the actions of the ``suspend_noirq`` phase. If 445 of the resume methods. This generally involves undoing the actions of 449 state, so that it can perform normal I/O. This generally involves 654 been thawed. Generally speaking, the PM notifiers are suitable for performing 698 cases it generally is not possible to put devices into low-power states 820 the case generally depends on the state of the device before the given system 842 ``DPM_FLAG_MAY_SKIP_RESUME`` flag is necessary, but generally not sufficient,
/OK3568_Linux_fs/kernel/kernel/power/
H A D	Kconfig	`174 Hardware support is generally required for this functionality to work 279 Generally, if you don't have a battery in your machine, there isn't 298 Per-cpu workqueues are generally preferred because they show`
/OK3568_Linux_fs/u-boot/include/
H A D	dwmmc.h	`256 * Generally your driver will have a platform data structure which holds both 275 * @cfg: Configuration structure to fill in (generally &plat->mmc) 293 * @cfg: Empty configuration structure (generally &plat->cfg). This is`
/OK3568_Linux_fs/u-boot/drivers/usb/dwc3/
H A D	dwc3-omap.c	`373 * Generally called from board_usb_init() implemented in board file. 412 * Generally called from board file. 436 * Generally called from board file.`

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