Home
last modified time | relevance | path

Searched full:requirements (Results 1 – 25 of 762) sorted by relevance

12345678910>>...31

/linux/rust/kernel/
H A Dopp.rs43 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in new()
44 // requirements. in new()
183 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in new()
184 // requirements. in new()
195 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in drop()
196 // requirements. in drop()
493 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in set()
494 // requirements. The OPP core guarantees not to access fields of [`Config`] after this in set()
626 // SAFETY: By the safety requirements, ptr is valid and its refcount will be incremented. in from_raw_table()
642 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety in from_dev()
[all …]
H A Dconfigfs.rs282 // SAFETY: By impl and function safety requirements this field in group()
347 // SAFETY: By function safety requirements of this function, this call in make_group()
353 // SAFETY: By function safety requirements, name points to a null in make_group()
393 // SAFETY: By function safety requirements of this function, this call in drop_item()
397 // SAFETY: By function safety requirements, `item` is embedded in a in drop_item()
400 // SAFETY: By function safety requirements, `c_child_group_ptr` is in drop_item()
446 // SAFETY: By function safety requirements, `this` is embedded in a in release()
449 // SAFETY: By function safety requirements, `c_group_ptr` is in release()
554 // SAFETY: By function safety requirements, `item` is embedded in a in show()
558 // SAFETY: The function safety requirements fo in show()
[all...]
H A Dtracepoint.rs9 /// This macro generates an unsafe function that calls into C, and its safety requirements will be
10 /// whatever the relevant C code requires. To document these safety requirements, you may add
H A Dpid_namespace.rs37 // SAFETY: The safety requirements guarantee the validity of the dereference, while the in from_ptr()
53 // SAFETY: The safety requirements guarantee that the refcount is non-zero. in dec_ref()
/linux/drivers/mtd/nand/raw/
H A Dnand_samsung.c14 struct nand_ecc_props requirements = {}; in samsung_nand_decode_id() local
73 /* Extract ECC requirements from 5th id byte*/ in samsung_nand_decode_id()
76 requirements.step_size = 512; in samsung_nand_decode_id()
77 requirements.strength = 1 << extid; in samsung_nand_decode_id()
79 requirements.step_size = 1024; in samsung_nand_decode_id()
82 requirements.strength = 24; in samsung_nand_decode_id()
85 requirements.strength = 40; in samsung_nand_decode_id()
88 requirements.strength = 60; in samsung_nand_decode_id()
92 requirements.step_size = 0; in samsung_nand_decode_id()
102 requirements.step_size = 512; in samsung_nand_decode_id()
[all …]
H A Dnand_esmt.c14 struct nand_ecc_props requirements = {}; in esmt_nand_decode_id() local
18 /* Extract ECC requirements from 5th id byte. */ in esmt_nand_decode_id()
20 requirements.step_size = 512; in esmt_nand_decode_id()
23 requirements.strength = 4; in esmt_nand_decode_id()
26 requirements.strength = 2; in esmt_nand_decode_id()
29 requirements.strength = 1; in esmt_nand_decode_id()
33 requirements.step_size = 0; in esmt_nand_decode_id()
38 nanddev_set_ecc_requirements(base, &requirements); in esmt_nand_decode_id()
H A Dnand_hynix.c498 struct nand_ecc_props requirements = {}; in hynix_nand_extract_ecc_requirements() local
503 requirements.step_size = 1024; in hynix_nand_extract_ecc_requirements()
507 requirements.step_size = 0; in hynix_nand_extract_ecc_requirements()
508 requirements.strength = 0; in hynix_nand_extract_ecc_requirements()
511 requirements.strength = 4; in hynix_nand_extract_ecc_requirements()
514 requirements.strength = 24; in hynix_nand_extract_ecc_requirements()
517 requirements.strength = 32; in hynix_nand_extract_ecc_requirements()
520 requirements.strength = 40; in hynix_nand_extract_ecc_requirements()
523 requirements.strength = 50; in hynix_nand_extract_ecc_requirements()
526 requirements.strength = 60; in hynix_nand_extract_ecc_requirements()
[all …]
H A Dnand_toshiba.c149 struct nand_ecc_props requirements = {}; in toshiba_nand_decode_id() local
173 * Extract ECC requirements from 6th id byte. in toshiba_nand_decode_id()
180 requirements.step_size = 512; in toshiba_nand_decode_id()
183 requirements.strength = 1; in toshiba_nand_decode_id()
186 requirements.strength = 4; in toshiba_nand_decode_id()
189 requirements.strength = 8; in toshiba_nand_decode_id()
193 requirements.step_size = 0; in toshiba_nand_decode_id()
198 nanddev_set_ecc_requirements(base, &requirements); in toshiba_nand_decode_id()
H A Dnand_micron.c416 const struct nand_ecc_props *requirements = in micron_supports_on_die_ecc() local
430 if (requirements->strength != 4 && requirements->strength != 8) in micron_supports_on_die_ecc()
471 if (requirements->strength != 4 && requirements->strength != 8) in micron_supports_on_die_ecc()
480 const struct nand_ecc_props *requirements = in micron_nand_init() local
531 if (requirements->strength == 4) { in micron_nand_init()
541 if (requirements->strength == 4) in micron_nand_init()
548 chip->ecc.bytes = requirements->strength * 2; in micron_nand_init()
550 chip->ecc.strength = requirements->strength; in micron_nand_init()
H A Dnand_onfi.c38 struct nand_ecc_props requirements; in nand_flash_detect_ext_param_page() local
99 requirements.strength = ecc->ecc_bits; in nand_flash_detect_ext_param_page()
100 requirements.step_size = 1 << ecc->codeword_size; in nand_flash_detect_ext_param_page()
101 nanddev_set_ecc_requirements(base, &requirements); in nand_flash_detect_ext_param_page()
272 struct nand_ecc_props requirements = { in nand_onfi_detect() local
277 nanddev_set_ecc_requirements(base, &requirements); in nand_onfi_detect()
294 pr_warn("Could not retrieve ONFI ECC requirements\n"); in nand_onfi_detect()
/linux/include/linux/
H A Dzconf.h11 /* The memory requirements for deflate are (in bytes):
15 the default memory requirements from 256K to 128K, compile with
19 The memory requirements for inflate are (in bytes) 1 << windowBits
/linux/arch/mips/tools/
H A Dgeneric-board-config.sh8 # generic MIPS kernel. It checks each for requirements specified using
10 # fragments which have no unmet requirements.
12 # An example of requirements in your board config fragment might be:
/linux/Documentation/kbuild/
H A DKconfig.recursion-issue-0212 # annotate those requirements, ie, some drivers use "depends on" while others
19 # core requirements are not carefully synced, as drivers evolve features
20 # they select or depend on end up becoming shared requirements which cannot be
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-dma-buffer9 This property reports the alignment requirements in bytes.
13 The alignment requirements in number of sample sets will depend
/linux/drivers/gpu/drm/xen/
H A Dxen_drm_front.h29 * Depending on the requirements for the para-virtualized environment, namely
30 * requirements dictated by the accompanying DRM/(v)GPU drivers running in both
53 * requirements for display buffers it is possible to allocate such buffers
/linux/Documentation/iio/
H A Dad7191.rst73 SPI Interface Requirements
76 The AD7191 has specific SPI interface requirements:
84 Power Supply Requirements
/linux/Documentation/power/regulator/
H A Ddesign.rst15 have different power requirements, and not all components with power
16 requirements are visible to software.
/linux/rust/kernel/list/
H A Dimpl_list_item_mod.rs292 // `post_remove`, or `view_value`. By the safety requirements of those methods,
314 // may choose to satisfy the safety requirements of `post_remove` instead of the safety
315 // requirements for `view_value`.
323 // GUARANTEES: (only when using the `view_value` safety requirements)
344 // value is `prepare_to_insert`, but by the safety requirements the
354 // promise the safety requirements of `post_remove` instead of the safety
355 // requirements for `view_value`.
/linux/rust/kernel/alloc/
H A Dallocator.rs76 /// This method has the same safety requirements as [`Allocator::realloc`].
107 // - `ptr` is either NULL or valid by the safety requirements of this function. in call()
155 // SAFETY: `ReallocFunc::call` has the same safety requirements as `Allocator::realloc`. in realloc()
200 // - `page` is a valid pointer to a `struct page`, given that by the safety requirements of in to_page()
202 // - By the safety requirements of this function `ptr` is valid for the entire lifetime of in to_page()
H A Dkbox.rs208 // SAFETY: `raw` comes from a previous call to `Box::into_raw`. By the safety requirements
476 // SAFETY: The safety requirements of this function ensure that `ptr` comes from a previous in try_init()
482 // SAFETY: The safety requirements of this method ensure that the object remains alive and
489 // SAFETY: The safety requirements of this method ensure that the pointer is valid and that
511 // SAFETY: The safety requirements of this function ensure that `ptr` comes from a previous
517 // SAFETY: The safety requirements for this function ensure that the object is still alive, in borrow_mut()
519 // The safety requirements of `from_foreign` also ensure that the object remains alive for
529 // SAFETY: The safety requirements for this function ensure that the object is still alive,
531 // The safety requirements of `from_foreign` also ensure that the object remains alive for in into_foreign()
/linux/Documentation/devicetree/bindings/display/panel/
H A Dolimex,lcd-olinuxino.yaml21 - AT24C16C EEPROM holding panel identification and timing requirements
27 device information (id, serial, etc.) and timing requirements.
/linux/Documentation/devicetree/bindings/iio/adc/
H A Dfsl,vf610-adc.yaml47 Maximum frequencies from datasheet operating requirements.
59 operating requirements. A safe default across a wide range of R_as and
/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Digbvf.rst23 For questions related to hardware requirements, refer to the documentation
24 supplied with your Intel adapter. All hardware requirements listed apply to use
H A Dixgbevf.rst20 For questions related to hardware requirements, refer to the documentation
21 supplied with your Intel adapter. All hardware requirements listed apply to use
/linux/drivers/leds/
H A DTODO9 * Review atomicity requirements in LED subsystem
13 not sleep.) Review the requirements for any bugs and document them

12345678910>>...31