Home
last modified time | relevance | path

Searched refs:segmented (Results 1 – 14 of 14) sorted by relevance

/linux-6.1.9/net/caif/
Dcfrfml.c100 bool segmented; in cfrfml_receive() local
114 segmented = tmp & RFM_SEGMENTATION_BIT; in cfrfml_receive()
116 if (segmented) { in cfrfml_receive()
/linux-6.1.9/Documentation/powerpc/
Dpci_iov_resource_on_powernv.rst118 * 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-6.1.9/drivers/firmware/arm_scmi/
Dvoltage.c94 bool segmented) in scmi_init_voltage_levels() argument
104 (segmented && (num_remaining || num_returned != 3))) { in scmi_init_voltage_levels()
116 v->segmented = segmented; in scmi_init_voltage_levels()
Dsensors.c291 s->intervals.segmented = SEGMENTED_INTVL_FORMAT(flags); in iter_intervals_update_state()
294 if (s->intervals.segmented && in iter_intervals_update_state()
299 s->intervals.segmented = false; in iter_intervals_update_state()
311 s->intervals.segmented = false; in iter_intervals_update_state()
607 s->intervals.segmented = false; in iter_sens_descr_process_response()
/linux-6.1.9/Documentation/networking/
Dsegmentation-offloads.rst125 assembled by GRO should be segmented to create an identical sequence of
126 frames using GSO, and any sequence of frames segmented by GSO should be
130 altered so that it is when a frame assembled via GRO is segmented via GSO.
159 cannot be just segmented to (P)MTU. Rather, the chunks must be contained in
Dtimestamping.rst294 coalescing sections of previously segmented buffers associated with
/linux-6.1.9/include/linux/
Dscmi_protocol.h241 bool segmented; member
531 bool segmented; member
/linux-6.1.9/net/can/
DKconfig61 CAN Transport Protocols offer support for segmented Point-to-Point
/linux-6.1.9/drivers/iio/common/scmi_sensors/
Dscmi_iio.c226 if (sensor->sensor_info->intervals.segmented) in scmi_iio_read_avail()
528 if (sensor->sensor_info->intervals.segmented) { in scmi_iio_set_sampling_freq_avail()
/linux-6.1.9/drivers/regulator/
Dscmi-regulator.c236 if (vinfo->segmented) in scmi_regulator_common_init()
/linux-6.1.9/Documentation/crypto/
Darchitecture.rst218 CRYPTO_ALG_TYPE_COMPRESS allowing for segmented compression /
/linux-6.1.9/Documentation/driver-api/
Dxillybus.rst267 Even though a non-segmented data stream is presented to the user at both
/linux-6.1.9/Documentation/RCU/Design/Data-Structures/
DData-Structures.rst670 The ``rcu_segcblist`` structure maintains a segmented list of callbacks
895 The ``->cblist`` structure is the segmented callback list described
/linux-6.1.9/arch/x86/
DKconfig2410 call. This is required to run 16-bit or segmented code such as