| /linux/Documentation/arch/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 118 * Can be configured to be segmented. When not segmented, we can
119 specify the PE# for the entire window. When segmented, a window
132 as segmented.
198 - Non-segmented M64 window: A non-segmented M64 window is mapped entirely
201 - Single segmented M64 windows: A segmented M64 window could be used just
207 - Multiple segmented M64 windows: As usual, each window is split into 256
234 IODA supports 256 PEs, so segmented windows contain 256 segments, so if
290 set the PE# for the window. But if it's in a segmented M64 window, the
|
| /linux/net/caif/ |
| H A D | cfrfml.c | 100 bool segmented; in cfrfml_receive() local
114 segmented = tmp & RFM_SEGMENTATION_BIT; in cfrfml_receive()
116 if (segmented) { in cfrfml_receive()
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | voltage.c | 96 bool segmented) in scmi_init_voltage_levels() argument
106 (segmented && (num_remaining || num_returned != 3))) { in scmi_init_voltage_levels()
118 v->segmented = segmented; in scmi_init_voltage_levels()
|
| H A D | sensors.c | 307 s->intervals.segmented = SEGMENTED_INTVL_FORMAT(flags); in iter_intervals_update_state()
310 if (s->intervals.segmented && in iter_intervals_update_state()
315 s->intervals.segmented = false; in iter_intervals_update_state()
327 s->intervals.segmented = false; in iter_intervals_update_state()
623 s->intervals.segmented = false; in iter_sens_descr_process_response()
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-memory-encryption.rst | 192 Bit[23] indicates support for segmented RMP
194 If supported, segmented RMP attributes can be found using the CPUID
206 To enable a segmented RMP, a new MSR is available::
209 Bit[0] indicates if segmented RMP is enabled
221 When a segmented RMP is enabled, RMP_BASE points to the RMP bookkeeping
241 the segmented RMP (the bookkeeping area, RST, and all segments), build the RST
|
| /linux/net/can/ |
| H A D | Kconfig | 62 CAN Transport Protocols offer support for segmented Point-to-Point
64 This protocol driver implements segmented data transfers for CAN CC
|
| /linux/Documentation/networking/ |
| H A D | segmentation-offloads.rst | 134 assembled by GRO should be segmented to create an identical sequence of
135 frames using GSO, and any sequence of frames segmented by GSO should be
165 cannot be just segmented to (P)MTU. Rather, the chunks must be contained in
|
| H A D | timestamping.rst | 364 coalescing sections of previously segmented buffers associated with
|
| /linux/include/linux/ |
| H A D | scmi_protocol.h | 284 bool segmented; member
574 bool segmented; member
|
| /linux/drivers/iio/common/scmi_sensors/ |
| H A D | scmi_iio.c | 229 if (sensor->sensor_info->intervals.segmented) in scmi_iio_read_avail()
530 if (sensor->sensor_info->intervals.segmented) { in scmi_iio_set_sampling_freq_avail()
|
| /linux/drivers/regulator/ |
| H A D | scmi-regulator.c | 236 if (vinfo->segmented) in scmi_regulator_common_init()
|
| /linux/Documentation/core-api/ |
| H A D | folio_queue.rst | 24 The folio_queue struct forms a single segment in a segmented list of folios
|
| /linux/Documentation/crypto/ |
| H A D | architecture.rst | 218 CRYPTO_ALG_TYPE_COMPRESS allowing for segmented compression /
|
| /linux/Documentation/driver-api/ |
| H A D | xillybus.rst | 267 Even though a non-segmented data stream is presented to the user at both
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 703 The ``rcu_segcblist`` structure maintains a segmented list of callbacks
928 The ``->cblist`` structure is the segmented callback list described
|
| /linux/arch/x86/ |
| H A D | Kconfig | 2326 call. This is required to run 16-bit or segmented code such as
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-online-fsck-design.rst | 3117 XFS inumbers are segmented, so the cursor needs to be marked as having
|