Home
last modified time | relevance | path

Searched full:usable (Results 1 – 25 of 745) sorted by relevance

12345678910>>...30

/Linux-v5.10/arch/powerpc/kexec/
Dfile_load_64.c29 u64 *buf; /* data buffer for usable-memory property */
34 /* usable memory ranges to look up */
94 * get_usable_memory_ranges - Get usable memory ranges. This list includes
107 * block?) is not added to usable memory. So, add [0, crashk_res.end] in get_usable_memory_ranges()
127 pr_err("Failed to setup usable memory ranges\n"); in get_usable_memory_ranges()
433 * @um_info: Usable memory buffer and ranges info.
460 * add_usable_mem - Add the usable memory ranges within the given memory range
462 * @um_info: Usable memory buffer and ranges info.
504 * usable memory ranges.
506 * @usm: linux,drconf-usable-memory property value.
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/powerpc/
Dibm,powerpc-cpu-features.txt94 - usable-privilege
179 This property may exist when the usable-privilege property value has PR bit set.
191 features usable by userspace will have a hwcap-bit-nr property.
213 usable-privilege = <1 | 2 | 4>;
219 usable-privilege = <1 | 2>;
226 usable-privilege = <2 | 4>;
233 usable-privilege = <1 | 2 | 4>;
241 usable-privilege = <1 | 2 | 4>;
/Linux-v5.10/drivers/net/ethernet/freescale/fs_enet/
DKconfig13 bool "Chip has an SCC usable for ethernet"
18 bool "Chip has an FCC usable for ethernet"
23 bool "Chip has an FEC usable for ethernet"
/Linux-v5.10/arch/mips/include/uapi/asm/
Dptrace.h80 * bit 0 -- 1 if W bit is usable.
81 * bit 1 -- 1 if R bit is usable.
82 * bit 2 -- 1 if I bit is usable.
/Linux-v5.10/arch/powerpc/kvm/
DKconfig97 that KVM is not usable under PowerVM (pHyp), is only usable
114 machines where hypervisor mode is not available or not usable,
/Linux-v5.10/arch/mips/vdso/
Dvgettimeofday.c24 * possibility of there being a usable clocksource, because there's nothing we
60 * possibility of there being a usable clocksource, because there's nothing we
/Linux-v5.10/Documentation/devicetree/bindings/
Dchosen.txt79 linux,usable-memory-range
94 linux,usable-memory-range = <0x9 0xf0000000 0x0 0x10000000>;
98 The main usage is for crash dump kernel to identify its own usable
/Linux-v5.10/arch/arm/boot/dts/
Dberlin2cd-google-chromecast.dts26 * We're using "linux,usable-memory" instead of "reg" here
34 linux,usable-memory = <0x00000000 0x20000000>; /* 512 MB */
/Linux-v5.10/Documentation/vm/
Dpage_frags.rst32 called. The "netdev" prefixed functions are usable in any context as these
34 only usable within the softirq context.
/Linux-v5.10/arch/mips/generic/
Dyamon-dt.c108 /* allow the user to override the usable memory */ in yamon_dt_append_memory()
147 err = fdt_setprop(fdt, mem_off, "linux,usable-memory", in yamon_dt_append_memory()
150 pr_err("Unable to set linux,usable-memory property: %d\n", err); in yamon_dt_append_memory()
/Linux-v5.10/arch/mips/include/asm/
Dtimex.h77 return 0; /* no usable counter */ in get_cycles()
97 return 0; /* no usable register */ in random_get_entropy()
/Linux-v5.10/Documentation/core-api/
Dpacking.rst34 - Packing a CPU-usable number into a memory buffer (with hardware
37 into a CPU-usable number.
60 That is, the MSByte (7) of the CPU-usable u64 sits at memory offset 0, and the
Dpadata.rst65 different from the 'usable' cpumask.
68 and the 'usable' cpumasks. (Each pair consists of a parallel and a serial
70 allocation and may be changed as above. The usable cpumasks are always a
/Linux-v5.10/arch/x86/include/asm/
Dirq_vectors.h33 * IDT vectors usable for external interrupt sources start at 0x20.
39 * Reserve the lowest usable vector (and hence lowest priority) 0x20 for
/Linux-v5.10/tools/arch/x86/include/asm/
Dirq_vectors.h33 * IDT vectors usable for external interrupt sources start at 0x20.
39 * Reserve the lowest usable vector (and hence lowest priority) 0x20 for
/Linux-v5.10/arch/um/drivers/
Dpty.c98 /* verify slave side is usable */ in getmaster()
109 printk(UM_KERN_ERR "getmaster - no usable host pty devices\n"); in getmaster()
/Linux-v5.10/drivers/gpu/drm/i915/display/
Dintel_tc.c561 * not be available/usable by the graphics driver: see the comment on
563 * concept of "usable" and make everything check for "connected and usable" we
565 * is usable by the rest of the driver. That maintains the old assumption that
566 * connected ports are usable, and avoids exposing to the users objects they
/Linux-v5.10/fs/f2fs/
Dgc.h77 * zone-capacity, these blocks are not usable.
78 * Such spanning segments can be in free list so calculate the sum of usable
/Linux-v5.10/lib/
DKconfig.kgdb141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
/Linux-v5.10/arch/mips/mti-malta/
Dmalta-dtshim.c178 /* allow the user to override the usable memory */ in append_memory()
221 err = fdt_setprop(fdt, mem_off, "linux,usable-memory", mem_array, in append_memory()
224 panic("Unable to set linux,usable-memory property: %d", err); in append_memory()
/Linux-v5.10/drivers/clocksource/
Darc_timer.c172 /* Local to CPU hence not usable in SMP */ in arc_cs_setup_rtc()
174 pr_warn("Local-64-bit-Ctr not usable in SMP\n"); in arc_cs_setup_rtc()
218 /* Local to CPU hence not usable in SMP */ in arc_cs_setup_timer1()
/Linux-v5.10/net/rxrpc/
Dconn_client.c460 * Add a connection to a bundle if there are no usable connections or we have
466 int i, usable; in rxrpc_maybe_add_conn() local
472 /* See if there are any usable connections. */ in rxrpc_maybe_add_conn()
473 usable = 0; in rxrpc_maybe_add_conn()
476 usable++; in rxrpc_maybe_add_conn()
478 if (!usable && !list_empty(&bundle->waiting_calls)) { in rxrpc_maybe_add_conn()
485 if (!usable) in rxrpc_maybe_add_conn()
491 usable < ARRAY_SIZE(bundle->conns)) in rxrpc_maybe_add_conn()
/Linux-v5.10/Documentation/devicetree/bindings/rtc/
Ddallas,ds1390.txt9 Values usable for ds1390 are 250, 2000, 4000
Dti,bq32k.txt9 Values usable are 1120 and 20180
/Linux-v5.10/Documentation/
DCOPYING-logo4 and is freely usable as long as you acknowledge Larry as the original

12345678910>>...30