Home
last modified time | relevance | path

Searched full:structured (Results 1 – 25 of 95) sorted by relevance

1234

/linux/Documentation/power/regulator/
H A Ddesign.rst5 This document provides a brief, partially structured, overview of some
36 The consumer API should be structured so that these use cases are
/linux/net/ethtool/
H A Dcmis_fw_update.c21 * struct cmis_cdb_fw_mng_features_rpl is a structured layout of the flat
102 * struct cmis_cdb_start_fw_download_pl is a structured layout of the
150 * struct cmis_cdb_write_fw_block_lpl_pl is a structured layout of the
355 * struct cmis_cdb_run_fw_image_pl is a structured layout of the flat
H A Dcmis_cdb.c148 * structured layouts of the flat arrays,
226 * struct cmis_cdb_module_features_rpl is structured layout of the flat
/linux/fs/nilfs2/
H A DKconfig8 NILFS2 is a log-structured file system (LFS) supporting continuous
/linux/drivers/net/ipa/
H A Dipa_uc.c31 * A 128 byte block of structured memory within the IPA SRAM is used together
68 * size, but only the first 40 bytes (structured this way) are used.
/linux/Documentation/mm/
H A Dindex.rst34 algorithms. It should all be integrated nicely into the above structured
/linux/arch/riscv/kernel/
H A Dcompat_signal.c108 /* sc_regs is structured the same as the start of pt_regs */ in compat_restore_sigcontext()
168 /* sc_regs is structured the same as the start of pt_regs */ in compat_setup_sigcontext()
H A Dsignal.c156 /* sc_regs is structured the same as the start of pt_regs */ in restore_sigcontext()
275 /* sc_regs is structured the same as the start of pt_regs */ in setup_sigcontext()
/linux/Documentation/arch/loongarch/
H A Dbooting.rst31 a 64-byte header structured like::
/linux/Documentation/arch/arm/spear/
H A Doverview.rst8 SPEAr (Structured Processor Enhanced Architecture).
/linux/arch/mips/include/asm/
H A Dirq.h26 * genex.S (handle_int & except_vec_vi_handler) which is structured as follows:
/linux/arch/s390/include/uapi/asm/
H A Draw3270.h11 #define TC_WRITESF 0x11 /* Write structured field */
/linux/Documentation/driver-api/
H A Di2c.rst18 structured around two kinds of driver, and two kinds of device. An I2C
/linux/Documentation/driver-api/gpio/
H A Dusing-gpio.rst46 For structured and managed applications, we recommend that you make use of the
/linux/Documentation/driver-api/thermal/
H A Dexynos_thermal.rst67 The exynos thermal driver is structured as::
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dfsl,imx27-pinctrl.txt91 and MUX_ID. They are structured as MX27_PAD_<Pad name>__<Signal name>. The names
/linux/Documentation/driver-api/usb/
H A Dtypec.rst103 Structured VDM "Discover Identity", the port driver needs to register the cable
158 Delivery Structured VDM Discover SVIDs message, each SVID needs to be
/linux/fs/f2fs/
H A DKconfig19 F2FS is based on Log-structured File System (LFS), which supports
/linux/Documentation/devicetree/bindings/clock/
H A Dmediatek,mt8196-clock.yaml14 The clock architecture in MediaTek SoCs is structured like below:
H A Dmediatek,mt8196-sys-clock.yaml14 The clock architecture in MediaTek SoCs is structured like below:
/linux/include/uapi/linux/
H A Dnbd.h79 /* magic 0x668e33ef for structured reply not supported by kernel yet */
/linux/Documentation/ABI/testing/
H A Dsysfs-firmware-dmi-entries15 DMI is structured as a large table of entries, where
/linux/drivers/gpu/drm/imagination/
H A Dpvr_drv.h40 * Macros used to aid copying structured and array data to and from
/linux/Documentation/filesystems/xfs/
H A Dxfs-self-describing-metadata.rst221 A typical buffer read verifier is structured as follows::
246 the case it can't, the code is structured as follows::
/linux/drivers/usb/typec/
H A Dbus.c211 * with the partner. The port drivers use it to deliver the Structured VDMs
318 * with the cable plugs. The port drivers use it to deliver the Structured VDMs

1234