Home
last modified time | relevance | path

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

12345678910>>...34

/Linux-v5.10/drivers/mtd/nand/raw/
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 …]
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()
Dnand_hynix.c499 struct nand_ecc_props requirements = {}; in hynix_nand_extract_ecc_requirements() local
504 requirements.step_size = 1024; in hynix_nand_extract_ecc_requirements()
508 requirements.step_size = 0; in hynix_nand_extract_ecc_requirements()
509 requirements.strength = 0; in hynix_nand_extract_ecc_requirements()
512 requirements.strength = 4; in hynix_nand_extract_ecc_requirements()
515 requirements.strength = 24; in hynix_nand_extract_ecc_requirements()
518 requirements.strength = 32; in hynix_nand_extract_ecc_requirements()
521 requirements.strength = 40; in hynix_nand_extract_ecc_requirements()
524 requirements.strength = 50; in hynix_nand_extract_ecc_requirements()
527 requirements.strength = 60; in hynix_nand_extract_ecc_requirements()
[all …]
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()
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()
273 struct nand_ecc_props requirements = { in nand_onfi_detect() local
278 nanddev_set_ecc_requirements(base, &requirements); in nand_onfi_detect()
295 pr_warn("Could not retrieve ONFI ECC requirements\n"); in nand_onfi_detect()
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()
/Linux-v5.10/Documentation/gpu/
Ddrm-uapi.rst40 Open-Source Userspace Requirements
43 The DRM subsystem has stricter requirements than most other kernel subsystems on
45 explains what exactly those requirements are, and why they exist.
80 leads to a few additional requirements:
96 requirements by doing a quick fork.
98 - The kernel patch can only be merged after all the above requirements are met,
103 These are fairly steep requirements, but have grown out from years of shared
207 The goal raises at least the following requirements for the kernel and
210 Requirements for KMS UAPI
229 Requirements for Render and Cross-Device UAPI
[all …]
/Linux-v5.10/include/linux/
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-v5.10/arch/mips/tools/
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-v5.10/Documentation/kbuild/
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-v5.10/Documentation/RCU/
Dindex.rst30 Design/Requirements/Requirements
/Linux-v5.10/Documentation/ABI/testing/
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-v5.10/drivers/gpu/drm/xen/
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-v5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-compressed.rst41 then the decoder has no requirements since it can parse all the
97 then the decoder has no requirements since it can parse all the
106 then the decoder has no requirements since it can parse all the
186 then the decoder has no requirements since it can parse all the
Dpixfmt-v4l2-mplane.rst38 alignment requirements or minimum/maximum size requirements.
/Linux-v5.10/Documentation/power/regulator/
Ddesign.rst15 have different power requirements, and not all components with power
16 requirements are visible to software.
/Linux-v5.10/include/linux/mtd/
Dnand.h284 * @requirements: ECC requirements from the NAND chip perspective
286 * @ctx: ECC context for the ECC engine, derived from the device @requirements
293 struct nand_ecc_props requirements; member
312 * struct_nand_device->memorg and struct_nand_device->ecc.requirements should
314 * capabilities/requirements. Once this is done nanddev_init() can be called.
537 * nanddev_get_ecc_requirements() - Extract the ECC requirements from a NAND
544 return &nand->ecc.requirements; in nanddev_get_ecc_requirements()
548 * nanddev_set_ecc_requirements() - Assign the ECC requirements of a NAND
551 * @reqs: Requirements
557 nand->ecc.requirements = *reqs; in nanddev_set_ecc_requirements()
/Linux-v5.10/Documentation/devicetree/bindings/display/panel/
Dolimex,lcd-olinuxino.yaml21 - AT24C16C EEPROM holding panel identification and timing requirements
27 device information (id, serial, etc.) and timing requirements.
/Linux-v5.10/Documentation/power/
Dpm_qos_interface.rst188 certain protocol requirements or target frame or sample rates etc.
199 latency tolerance requirements for the device is empty, the callback is expected
214 requirements from the kernel side in the device's list.
218 latency tolerance requirements for devices.
/Linux-v5.10/Documentation/devicetree/bindings/iio/adc/
Dfsl,vf610-adc.yaml40 Maximum frequencies from datasheet operating requirements.
52 operating requirements. A safe default across a wide range of R_as and
/Linux-v5.10/drivers/leds/
DTODO9 * Review atomicity requirements in LED subsystem
13 not sleep.) Review the requirements for any bugs and document them
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/intel/
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
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
/Linux-v5.10/drivers/scsi/mpt3sas/
DKconfig62 parameter will reduce memory requirements on a per controller instance.
74 parameter will reduce memory requirements on a per controller instance.
/Linux-v5.10/drivers/misc/cb710/
Dsgbuf2.c85 * Same requirements as in sg_miter_next().
129 * Same requirements as in sg_miter_next().

12345678910>>...34