Home
last modified time | relevance | path

Searched refs:CORE (Results 1 – 19 of 19) sorted by relevance

/linux-4.4.14/Documentation/kbuild/
DKconfig.recursion-issue-0113 # * What values are possible for CORE?
15 # CORE_BELL_A_ADVANCED selects CORE, which means that it influences the values
16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
17 # CORE must be 'y' too.
27 # CORE_BELL_A depends on CORE, so CORE influences CORE_BELL_A.
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
38 # of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already
39 # since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
[all …]
DKconfig.recursion-issue-0225 # have. Let's assume we have some CORE functionality, then the kernel has a
32 # with CORE, one uses "depends on" while the other uses "select". Another
38 # To fix this the "depends on CORE" must be changed to "select CORE", or the
39 # "select CORE" must be changed to "depends on CORE".
49 config CORE config
54 depends on CORE
63 select CORE
Dkconfig-language.txt446 of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already
447 since CORE_BELL_A depends on CORE. At times it may not be possible to remove
/linux-4.4.14/arch/s390/numa/
Dmode_emu.c46 enum toptree_level {CORE, MC, BOOK, NODE, TOPOLOGY}; enumerator
105 toptree_for_each(core, tree, CORE) { in cores_free()
157 toptree_for_each(core_node, node, CORE) in dist_node_to_core()
213 toptree_for_each_safe(core, tmp, phys, CORE) { in toptree_to_numa_single()
232 cores_free = cores_target - toptree_count(node, CORE); in move_level_to_numa_node()
234 if (cores_free == toptree_count(cur, CORE)) in move_level_to_numa_node()
237 if (cores_free >= toptree_count(cur, CORE)) in move_level_to_numa_node()
270 toptree_for_each(core, numa, CORE) in toptree_to_numa_first()
389 toptree_for_each(core, numa, CORE) in toptree_to_topology()
/linux-4.4.14/drivers/staging/rdma/hfi1/
Dchip_registers.h54 #define CORE 0x000000000000 macro
55 #define CCE (CORE + 0x000000000000)
56 #define ASIC (CORE + 0x000000400000)
57 #define MISC (CORE + 0x000000500000)
58 #define DC_TOP_CSRS (CORE + 0x000000600000)
59 #define CHIP_DEBUG (CORE + 0x000000700000)
60 #define RXE (CORE + 0x000001000000)
61 #define TXE (CORE + 0x000001800000)
/linux-4.4.14/arch/arm/boot/dts/
Domap5-core-thermal.dtsi2 * Device Tree Source for OMAP543x SoC CORE thermal
/linux-4.4.14/arch/arm/mach-omap2/
DKconfig233 access SDRAM during CORE DVFS, select Y here. This should boost
234 SDRAM performance at lower CORE OPPs. There are relatively few
Dsleep34xx.S384 cmp r4, #0x0 @ Check if previous power state of CORE is OFF
404 cmp r2, #0x0 @ Check if previous power state of CORE is OFF
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Ddwc3.txt1 synopsys DWC3 CORE
/linux-4.4.14/Documentation/arm/OMAP/
Domap_pm40 3. Set the maximum system DMA transfer start latency (CORE pwrdm):
/linux-4.4.14/drivers/net/wireless/brcm80211/brcmsmac/phy/
Dphy_n.c16442 WRITE_RADIO_REG4(pi, RADIO_2057, CORE, in wlc_phy_workarounds_nphy()
16445 WRITE_RADIO_REG4(pi, RADIO_2057, CORE, in wlc_phy_workarounds_nphy()
16448 WRITE_RADIO_REG4(pi, RADIO_2057, CORE, in wlc_phy_workarounds_nphy()
16467 CORE, coreNum, in wlc_phy_workarounds_nphy()
16477 CORE, coreNum, in wlc_phy_workarounds_nphy()
16481 CORE, coreNum, in wlc_phy_workarounds_nphy()
16486 CORE, coreNum, in wlc_phy_workarounds_nphy()
16490 CORE, coreNum, in wlc_phy_workarounds_nphy()
16495 CORE, coreNum, in wlc_phy_workarounds_nphy()
16506 CORE, 0, in wlc_phy_workarounds_nphy()
[all …]
/linux-4.4.14/Documentation/
Dedac.txt74 Controller (MC) driver modules. On a given system, the CORE is loaded
75 and one MC driver will be loaded. Both the CORE and the MC driver (or
80 both the CORE's and the MC driver's versions.
/linux-4.4.14/Documentation/RCU/
DwhatisRCU.txt23 2. WHAT IS RCU'S CORE API?
24 3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API?
115 2. WHAT IS RCU'S CORE API?
354 3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API?
/linux-4.4.14/drivers/tty/serial/jsm/
Djsm_tty.c403 jsm_dbg(CORE, &brd->pci_dev, in jsm_tty_init()
/linux-4.4.14/arch/xtensa/
DKconfig176 Enabled SMP Software; allows more than one CPU/CORE
/linux-4.4.14/Documentation/networking/
Dixgb.txt229 ### CORE settings (mostly for socket and UDP effect)
/linux-4.4.14/drivers/pinctrl/
Dpinctrl-tegra210.c1453 …PINGROUP(core_pwr_req, CORE, RSVD1, RSVD2, RSVD3, 0x317c, N, N, N, 0x…
/linux-4.4.14/drivers/scsi/bfa/
Dbfa_core.c22 BFA_TRC_FILE(HAL, CORE);
/linux-4.4.14/
DMAINTAINERS1190 ARM/INTEL XSC3 (MANZANO) ARM CORE
2910 COMPACTPCI HOTPLUG CORE
3609 DRIVER CORE, KOBJECTS, DEBUGFS, KERNFS AND SYSFS
3932 EDAC-CORE
4895 HARDWARE RANDOM NUMBER GENERATOR CORE
4904 HARDWARE SPINLOCK CORE
4986 HID CORE LAYER
5112 Hyper-V CORE AND DRIVERS
7567 NTB DRIVER CORE
9369 TIMEKEEPING, CLOCKSOURCE CORE, NTP
[all …]