Home
last modified time | relevance | path

Searched refs:subsystem (Results 1 – 25 of 100) sorted by relevance

1234

/drivers/remoteproc/
Dqcom_common.c104 static int qcom_add_minidump_segments(struct rproc *rproc, struct minidump_subsystem *subsystem) in qcom_add_minidump_segments() argument
118 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments()
119 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments()
145 struct minidump_subsystem *subsystem; in qcom_minidump() local
158 subsystem = &toc->subsystems[minidump_id]; in qcom_minidump()
164 if (subsystem->regions_baseptr == 0 || in qcom_minidump()
165 le32_to_cpu(subsystem->status) != 1 || in qcom_minidump()
166 le32_to_cpu(subsystem->enabled) != MD_SS_ENABLED || in qcom_minidump()
167 le32_to_cpu(subsystem->encryption_status) != MD_SS_ENCR_DONE) { in qcom_minidump()
172 ret = qcom_add_minidump_segments(rproc, subsystem); in qcom_minidump()
DKconfig5 bool "Support for Remote Processor subsystem"
136 subsystem via the remote processor framework.
173 tristate "Qualcomm Hexagon V5 self-authenticating modem subsystem support"
188 subsystem based on Hexagon V5. The TrustZone based system is
229 a non-TrustZone wireless subsystem.
/drivers/target/
DKconfig14 subsystem logic for virtual LUN 0 access
22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
/drivers/rapidio/
DKconfig33 this switch is set the RapidIO subsystem will enable all
52 bool "RapidIO subsystem debug messages"
55 Say Y here if you want the RapidIO subsystem to produce a bunch of
57 problem with the RapidIO subsystem and want to see more of what is
68 for RapidIO subsystem. You may select single built-in method or
/drivers/staging/fieldbus/Documentation/
Dfieldbus_dev.txt29 Part I - Why do we need this subsystem?
38 The purpose of this subsystem is:
42 Part II - How can drivers use the subsystem?
49 Part III - How can userspace use the subsystem?
/drivers/cpuidle/
DKconfig.powerpc12 through cpuidle subsystem.
21 through cpuidle subsystem.
/drivers/staging/most/Documentation/
Ddriver_usage.txt29 subsystem and consists basically of the module core.c and its API. It
40 subsystem. It is registered with the core to connect the MOST subsystem to
82 This layer implements the MOST subsystem. It contains the core module and
105 the driver via the networking subsystem.
109 driver via the V4L subsystem.
113 used to access the driver via the ALSA subsystem.
121 object (see section 1.3) registers a subsystem with configfs, which is used to
174 with the ALSA subsystem.
/drivers/staging/media/av7110/
Daudio-set-bypass-mode.rst42 the Digital TV subsystem.
54 DigitalTM streams are automatically forwarded by the Digital TV subsystem if
/drivers/soundwire/
DKconfig3 # SoundWire subsystem configuration
14 systems. Say Y to enable this subsystem, N if you do not have such
/drivers/isdn/capi/
DKconfig14 This subsystem requires a hardware specific driver.
16 in the kernel that uses the CAPI subsystem.
/drivers/platform/surface/aggregator/
DKconfig23 This option controls whether the Surface SAM subsystem core will be
40 Choose m if you want to build the SAM subsystem core and SSH driver as
62 Aggregator Module subsystem and Surface Serial Hub driver.
/drivers/gpio/
DTODO2 subsystem.
7 Starting with commit 79a9becda894 the GPIO subsystem embarked on a journey
11 used in the inception of the GPIO subsystem.
97 similar and probe a proper driver in the gpiolib subsystem.
140 creating pin control as its own subsystem was that we could avoid any
144 and the same pin control and GPIO subsystem.
/drivers/i2c/muxes/
DKconfig42 by a MUX-controller from the MUX subsystem.
83 multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
108 demultiplexer that uses the pinctrl subsystem. This is useful if you
/drivers/staging/fbtft/
DTODO2 into the DRM subsystem under drivers/gpu/drm - fbdev doesn't take any new
/drivers/iio/test/
DKconfig3 # Industrial I/O subsystem unit tests configuration
/drivers/iio/
DKconfig3 # Industrial I/O subsystem configuration
9 The industrial I/O subsystem provides a unified framework for
/drivers/media/dvb-core/
DKconfig39 increases the memory consumption of the DVB subsystem even
50 If you say Y here, the DVB subsystem will use dynamic minor
/drivers/staging/gs_fpgaboot/
DTODO7 And please CC to "Staging subsystem" mail list <devel@driverdev.osuosl.org> too.
/drivers/net/ethernet/mellanox/mlxbf_gige/
DKconfig13 Arm subsystem.
/drivers/media/test-drivers/vidtv/
DKconfig7 validate the existing APIs in the media subsystem. It can also aid developers
/drivers/gpu/drm/xlnx/
DKconfig16 subsystem.
/drivers/mmc/
DKconfig3 # MMC subsystem configuration
/drivers/staging/iio/
DKconfig3 # Industrial I/O subsystem configuration
/drivers/misc/cxl/
Dflash.c21 u16 subsystem; member
247 header->subsystem = cpu_to_be16(adapter->guest->subsystem); in handle_image()
/drivers/memstick/
DKconfig3 # MemoryStick subsystem configuration

1234