Home
last modified time | relevance | path

Searched full:underlying (Results 1 – 25 of 1245) sorted by relevance

12345678910>>...50

/openbmc/sdeventplus/src/sdeventplus/
H A Devent.hpp29 * @param[in] sdevent - Optional underlying sd_event implementation
30 * @throws SdEventError for underlying sd_event errors
42 * @param[in] sdevent - Optional underlying sd_event implementation
43 * @throws SdEventError for underlying sd_event errors
61 * @param[in] sdevent - Optional underlying sd_event implementation
62 * @throws SdEventError for underlying sd_event errors
70 * @param[in] sdevent - Optional underlying sd_event implementation
71 * @throws SdEventError for underlying sd_event errors
77 /** @brief Get the underlying sd_event
91 * @throws SdEventError for underlying sd_event errors
[all …]
H A Dclock.hpp14 /** @brief Specifies the underlying clock implementation
27 * Based on the underlying sd_event time functions
50 * @throws SdEventError for underlying sd_event errors
/openbmc/gpioplus/src/gpioplus/internal/
H A Dfd.hpp22 * @param[in] sys - Optional underlying syscall implementation
23 * @throws std::system_error for underlying syscall failures
31 * @param[in] sys - Optional underlying syscall implementation
32 * @throws std::system_error for underlying syscall failures
41 * @param[in] sys - Optional underlying syscall implementation
72 * @throws std::system_error for underlying syscall failures
78 * @throws std::system_error for underlying syscall failures
85 * @throws std::system_error for underlying syscall failures
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Dstriped.rst6 device across one or more underlying devices. Data is written in "chunks",
7 with consecutive chunks rotating among the underlying devices. This can
13 Number of underlying devices.
18 Full pathname to the underlying block-device, or a
23 One or more underlying devices can be specified. The striped device size must
24 be a multiple of the chunk size multiplied by the number of underlying devices.
33 # Create a striped device across any number of underlying devices. The device
H A Ddm-ebs.rst13 Underlying block size can be set to > 4K to test buffering larger units.
18 <dev path> <offset> <emulated sectors> [<underlying sectors>]
23 Full pathname to the underlying block-device,
34 <underlying sectors>:
43 offset 1024 sectors with underlying devices block size automatically set:
48 offset 128 sectors, enforce 2KiB underlying device block size.
H A Dwritecache.rst17 2. the underlying device that will be cached
47 underlying device
53 - some underlying devices perform better with fua, some
69 written to the underlying device and cleaned up.
105 to the underlying device
/openbmc/sdeventplus/src/sdeventplus/source/
H A Dbase.hpp54 /** @brief Gets the underlying sd_event_source
68 * @throws SdEventError for underlying sd_event errors
76 * @throws SdEventError for underlying sd_event errors
84 * @throws SdEventError for underlying sd_event errors
91 * @throws SdEventError for underlying sd_event errors
100 * @throws SdEventError for underlying sd_event errors
109 * @throws SdEventError for underlying sd_event errors
115 * @throws SdEventError for underlying sd_event errors
123 * @throws SdEventError for underlying sd_event errors
129 * @throws SdEventError for underlying sd_event errors
[all …]
H A Dtime.hpp46 * @throws SdEventError for underlying sd_event errors
59 * @throws SdEventError for underlying sd_event errors
71 * @throws SdEventError for underlying sd_event errors
79 * @throws SdEventError for underlying sd_event errors
85 * @throws SdEventError for underlying sd_event errors
93 * @throws SdEventError for underlying sd_event errors
115 * @throws SdEventError for underlying sd_event errors
H A Dio.hpp61 * @throws SdEventError for underlying sd_event errors
69 * @throws SdEventError for underlying sd_event errors
76 * @throws SdEventError for underlying sd_event errors
85 * @throws SdEventError for underlying sd_event errors
92 * @throws SdEventError for underlying sd_event errors
116 * @throws SdEventError for underlying sd_event errors
H A Dsignal.hpp39 * @throws SdEventError for underlying sd_event errors
51 * @throws SdEventError for underlying sd_event errors
63 * @throws SdEventError for underlying sd_event errors
86 * @throws SdEventError for underlying sd_event errors
H A Devent.hpp83 * @throws SdEventError for underlying sd_event errors
122 * @throws SdEventError for underlying sd_event errors
135 * @throws SdEventError for underlying sd_event errors
148 * @throws SdEventError for underlying sd_event errors
/openbmc/sdeventplus/src/sdeventplus/utility/
H A Dtimer.hpp59 * @throws SdEventError for underlying sd_event errors
91 * @throws SdEventError for underlying sd_event errors
101 * @throws SdEventError for underlying sd_event errors
114 * @throws SdEventError for underlying sd_event errors
130 * @throws SdEventError for underlying sd_event errors
140 * @throws SdEventError for underlying sd_event errors
148 * @throws SdEventError for underlying sd_event errors
154 * @throws SdEventError for underlying sd_event errors
174 * @throws SdEventError for underlying sd_event errors
184 * @throws SdEventError for underlying sd_event errors
[all …]
/openbmc/linux/Documentation/filesystems/
H A Doverlayfs.rst32 In the special case of all overlay layers on the same underlying
34 filesystem and st_ino from the underlying filesystem. This will
40 underlying filesystem, the same compliant behavior could be achieved
42 identifier from the real object st_ino and an underlying fsid index.
44 underlying filesystems rarely use the high inode number bits. In case
45 the underlying inode number does overflow into the high xino bits, overlay
49 If all underlying filesystems support NFS file handles, the value of st_ino
187 underlying directory (upper or lower).
293 compared to direct access on underlying lower or upper filesystems
301 upper layer based on underlying filesystem permissions, again including
[all …]
/openbmc/gpioplus/src/gpioplus/
H A Devent.hpp59 * The underlying implementation of the event is independent of
68 * @throws std::system_error for underlying syscall failures
80 * Follows the read(2) semantics of the underlying file descriptor
82 * @throws std::system_error for underlying syscall failures
90 * @throws std::system_error for underlying syscall failures
H A Dhandle.hpp70 * The underlying implementation of the handle is independent of
78 * @throws std::system_error for underlying syscall failures
91 * @throws std::system_error for underlying syscall failures
99 * @throws std::system_error for underlying syscall failures
106 * @throws std::system_error for underlying syscall failures
H A Dchip.hpp65 * @param[in] sys - Optional underlying syscall implementation
71 * @throws std::system_error for underlying syscall failures
78 * @throws std::system_error for underlying syscall failures
/openbmc/linux/drivers/gpio/
H A Dgpio-grgpio.c45 /* Structure for an irq of the core - called an underlying irq */
48 u8 uirq; /* Underlying irq of the gpio driver */
53 * used to map to the corresponding underlying irq.
68 * The grgpio core can have multiple "underlying" irqs. The gpio lines
69 * can be mapped to any one or none of these underlying irqs
76 * This array contains information on each underlying irq, each
85 * the irq to the underlying irq by pointing into the uirqs array.
205 * For each gpio line, call its interrupt handler if it its underlying in grgpio_irq_handler()
252 /* Request underlying irq if not already requested */ in grgpio_irq_map()
261 "Could not request underlying irq %d\n", in grgpio_irq_map()
[all …]
/openbmc/linux/drivers/md/
H A Ddm-ebs-target.c24 struct dm_dev *dev; /* Underlying device to emulate block size on. */
32 …unsigned int u_bs; /* Underlying block size in sectors retrieved from/set on lower layer device. …
34 bool u_bs_set:1; /* Flag to indicate underlying block size is set on table line. */
151 * Partial first underlying block (__nr_blocks() may have in __ebs_discard_bio()
159 /* Partial last underlying block if any. */ in __ebs_discard_bio()
241 * <dev_path>: path of the underlying device
244 * [<ubs>]: underlying block size in units of 512 bytes imposed on the lower layer;
245 * optional, if not supplied, retrieve logical block size from underlying device
285 ti->error = "Invalid underlying block size"; in ebs_ctr()
304 ti->error = "Invalid retrieved underlying block size"; in ebs_ctr()
[all …]
/openbmc/linux/security/landlock/
H A Dobject.h19 * struct landlock_object_underops - Operations on an underlying object
23 * @release: Releases the underlying object (e.g. iput() for an inode).
59 * tied to its underlying kernel structure. This pointer is protected
73 * underlying object (e.g. inode).
/openbmc/phosphor-networkd/src/
H A Dncsi_util.hpp75 /* @brief This function will ask underlying NCSI driver
107 /* @brief This function will ask underlying NCSI driver
118 /* @brief This function will ask underlying NCSI driver
127 * of the package and the channels underlying
/openbmc/linux/Documentation/devicetree/bindings/soc/samsung/
H A Dexynos-usi.yaml66 Enable this property if underlying protocol requires the clock to be
77 description: Child node describing underlying I2C
81 description: Child node describing underlying UART/serial
85 description: Child node describing underlying SPI
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-intel-m10-bmc-sec-update8 visible if the underlying device supports it.
18 is only visible if the underlying device supports it.
28 underlying device supports it.
H A Dsysfs-bus-event_source-devices-hv_gpci103 underlying platform/firmware.
135 underlying platform/firmware.
167 underlying platform/firmware.
199 underlying platform/firmware.
231 underlying platform/firmware.
/openbmc/linux/arch/m68k/include/asm/
H A Dtimex.h12 * CLOCK_TICK_RATE should give the underlying frequency of the tick timer
22 #define CLOCK_TICK_RATE 1193180 /* Underlying HZ */
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/composefs/
H A Dcomposefs_1.0.8.bb2 DESCRIPTION = "The composefs project combines several underlying Linux \
4 filesystem trees, stacking on top of an underlying "lower" Linux filesystem."

12345678910>>...50