| /linux/drivers/mtd/nand/raw/ |
| H A D | nand_samsung.c | 14 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 D | nand_esmt.c | 14 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 D | nand_hynix.c | 498 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 D | nand_toshiba.c | 149 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 D | nand_micron.c | 416 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 D | nand_onfi.c | 38 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 D | zconf.h | 11 /* 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/Documentation/gpu/ |
| H A D | drm-uapi.rst | 49 Open-Source Userspace Requirements
52 The DRM subsystem has stricter requirements than most other kernel subsystems on
54 explains what exactly those requirements are, and why they exist.
89 leads to a few additional requirements:
105 requirements by doing a quick fork.
107 - The kernel patch can only be merged after all the above requirements are met,
112 These are fairly steep requirements, but have grown out from years of shared
218 The goal raises at least the following requirements for the kernel and
221 Requirements for KMS UAPI
240 Requirements for Render and Cross-Device UAPI
[all …]
|
| /linux/drivers/platform/x86/intel/pmc/ |
| H A D | core_ssram.c | 81 * IP state requirements for the given mode. The IP mapping is platform in pmc_core_get_lpm_req()
83 * Platforms only use a subset of the space to track the requirements in pmc_core_get_lpm_req()
97 * | 2 | LPM0 Requirements 0 | in pmc_core_get_lpm_req()
101 * | 29 | LPM0 Requirements 27 | in pmc_core_get_lpm_req()
110 * | 60 | LPM7 Requirements 0 | in pmc_core_get_lpm_req()
114 * | 87 | LPM7 Requirements 27 | in pmc_core_get_lpm_req()
129 "couldn't read Low Power Mode requirements: %d\n", ret); in pmc_core_get_lpm_req()
|
| /linux/rust/kernel/ |
| H A D | device.rs | 55 // SAFETY: By the safety requirements, ptr is valid. in from_raw()
63 // SAFETY: `ptr` is valid by the safety requirements of this function. By the above call to in from_raw()
82 // SAFETY: Guaranteed by the safety requirements of the function. in as_ref()
95 // SAFETY: The safety requirements guarantee that the refcount is non-zero. in dec_ref()
|
| H A D | types.rs | 61 /// `ptr` must either be null or satisfy the safety requirements for
67 // SAFETY: Since `ptr` is not null here, then `ptr` satisfies the safety requirements in try_from_foreign()
68 // of `from_foreign` given the safety requirements of this function. in try_from_foreign()
82 // SAFETY: The safety requirements for this function ensure that the object is still alive, in borrow()
84 // The safety requirements of `from_foreign` also ensure that the object remains alive for in borrow()
90 // SAFETY: The safety requirements of this function ensure that `ptr` comes from a previous in from_foreign()
105 // SAFETY: The safety requirements for this function ensure that the object is still alive, in borrow()
107 // The safety requirements of `from_foreign` also ensure that the object remains alive for in borrow()
116 // SAFETY: The safety requirements of this function ensure that `ptr` comes from a previous in from_foreign()
392 // INVARIANT: The safety requirements guarantee that the new instance now owns the in from_raw()
|
| /linux/arch/mips/tools/ |
| H A D | generic-board-config.sh | 8 # 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 D | Kconfig.recursion-issue-02 | 12 # 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/rust/kernel/list/ |
| H A D | impl_list_item_mod.rs | 215 // `post_remove`, or `view_value`. By the safety requirements of those methods,
235 // may choose to satisfy the safety requirements of `post_remove` instead of the safety
236 // requirements for `view_value`.
244 // GUARANTEES: (only when using the `view_value` safety requirements)
257 // value is `prepare_to_insert`, but by the safety requirements the
267 // promise the safety requirements of `post_remove` instead of the safety
268 // requirements for `view_value`.
|
| /linux/Documentation/RCU/ |
| H A D | index.rst | 29 Design/Requirements/Requirements
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-dma-buffer | 9 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 D | xen_drm_front.h | 29 * 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/rust/ |
| H A D | quick-start.rst | 20 Alternatively, the next two "Requirements" sections explain each component and
90 Requirements: Building
95 To easily check whether the requirements are met, the following target
199 Requirements: Developing
273 above), as long as the other requirements are met. In turn, this will make
|
| /linux/include/linux/mtd/ |
| H A D | nand.h | 385 * @requirements: ECC requirements from the NAND chip perspective
387 * @ctx: ECC context for the ECC engine, derived from the device @requirements
394 struct nand_ecc_props requirements;
413 * struct_nand_device->memorg and struct_nand_device->ecc.requirements should
415 * capabilities/requirements. Once this is done nanddev_init() can be called.
658 * nanddev_get_ecc_requirements() - Extract the ECC requirements from a NAND
665 return &nand->ecc.requirements;
669 * nanddev_set_ecc_requirements() - Assign the ECC requirements of a NAND
672 * @reqs: Requirements in nanddev_set_ecc_requirements()
391 struct nand_ecc_props requirements; global() member
[all...] |
| /linux/Documentation/power/regulator/ |
| H A D | design.rst | 15 have different power requirements, and not all components with power
16 requirements are visible to software.
|
| /linux/Documentation/process/ |
| H A D | maintainer-soc-clean-dts.rst | 4 SoC Platforms with DTS Compliance Requirements
12 MAINTAINERS impose additional requirements listed below.
|
| /linux/rust/kernel/sync/lock/ |
| H A D | spinlock.rs | 101 // SAFETY: The safety requirements ensure that `ptr` is valid for writes, and `name` and in init()
107 // SAFETY: The safety requirements of this function ensure that `ptr` points to valid in lock()
113 // SAFETY: The safety requirements of this function ensure that `ptr` is valid and that the in unlock()
|
| H A D | mutex.rs | 102 // SAFETY: The safety requirements ensure that `ptr` is valid for writes, and `name` and in init()
108 // SAFETY: The safety requirements of this function ensure that `ptr` points to valid in lock()
114 // SAFETY: The safety requirements of this function ensure that `ptr` is valid and that the in unlock()
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 24 with these requirements:
76 The minimum requirements for the policy were:
90 considered against these list of requirements, and did not fulfill
91 all of the minimum requirements. Extending IMA to cover these
92 requirements was considered, but ultimately discarded for a
232 to express the first stage bootup requirements appropriately.
237 As requirements change over time (vulnerabilities are found in previously
|
| /linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | olimex,lcd-olinuxino.yaml | 21 - AT24C16C EEPROM holding panel identification and timing requirements
27 device information (id, serial, etc.) and timing requirements.
|