Home
last modified time | relevance | path

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

/Linux-v5.4/drivers/hwtracing/stm/
DKconfig2 config STM config
7 A System Trace Module (STM) is a device exporting data in System
9 Examples of such devices are Intel(R) Trace Hub and Coresight STM.
13 if STM
16 tristate "Basic STM framing protocol driver"
19 This is a simple framing protocol for sending data over STM
20 devices. This was the protocol that the STM framework used
22 driver for compatibility with your existing STM setup.
31 tristate "MIPI SyS-T STM framing protocol driver"
45 tristate "Dummy STM driver"
[all …]
/Linux-v5.4/Documentation/trace/
Dsys-t.rst7 The MIPI SyS-T protocol driver can be used with STM class devices to
11 In order to use the MIPI SyS-T protocol driver with your STM device,
15 a policy for your STM device, by specifying it in the policy name:
25 If the protocol name is omitted, the STM class will chose whichever
Dstm.rst7 System Trace Module (STM) is a device described in MIPI STP specs as
36 the STM device name to which this policy applies and and arbitrary
83 Some STM devices may allow direct mapping of the channel mmio regions
93 Examples of STM devices are Intel(R) Trace Hub [1] and Coresight STM
Dcoresight.rst38 0 CPU 0<-->: C : 0 CPU 0<-->: C : : C : @ STM @ || System ||
91 intricate IP blocks such as STM and CTI.
103 STM:
121 ETMv3.x ETMv4, PTMv1.0, PTMv1.1, STM, STM500, ITM
464 How to use the STM module
471 As with any other CoreSight component, specifics about the STM tracer can be
479 Like any other source a sink needs to be identified and the STM enabled before
486 interface provided for that purpose by the generic STM API::
492 Details on how to use the generic STM API can be found here [#second]_.
Dintel_th.rst24 Module (STM) device,
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-stm7 this STM device.
14 Shows the number of channels per master on this STM device.
Dconfigfs-stp-policy6 for software sources wishing to send trace data over an STM
23 STM device to which this policy applies, read only. Same as the
/Linux-v5.4/arch/arm/mach-sti/
Dboard-dt.c31 DT_MACHINE_START(STM, "STi SoC with Flattened Device Tree")
/Linux-v5.4/sound/soc/sti/
DKconfig3 # STM SoC audio configuration
/Linux-v5.4/drivers/gpu/drm/sti/
DKconfig13 Choose this option to enable DRM on STM stiH4xx chipset
/Linux-v5.4/drivers/iio/imu/st_lsm6dsx/
DKconfig4 tristate "ST_LSM6DSx driver for STM 6-axis IMU MEMS sensors"
/Linux-v5.4/drivers/crypto/ux500/
DKconfig25 Depends on UX500/STM DMA if running in DMA mode.
/Linux-v5.4/Documentation/devicetree/bindings/iio/humidity/
Dhts221.txt1 * HTS221 STM humidity + temperature sensor
/Linux-v5.4/Documentation/devicetree/bindings/iio/imu/
Dst_lsm6dsx.txt1 * ST_LSM6DSx driver for STM 6-axis (acc + gyro) imu Mems sensors
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dcoresight.txt67 * Additional required properties for System Trace Macrocells (STM):
327 4. STM
364 [1]. There is currently two version of STM: STM32 and STM500. Both
/Linux-v5.4/drivers/hwtracing/intel_th/
DKconfig53 depends on STM
/Linux-v5.4/drivers/hwtracing/coresight/
DKconfig91 select STM
/Linux-v5.4/drivers/i2c/busses/
Di2c-rcar.c63 #define STM (1 << 5) /* slave transmit mode */ macro
573 if (ssr_raw & STM) { in rcar_i2c_slave_irq()
/Linux-v5.4/arch/arm/boot/dts/
Duniphier-pxs2.dtsi378 /* chip-internal connection for STM */
Dqcom-msm8974.dtsi953 * 7 - connected to STM
Dqcom-apq8064.dtsi1651 * 2 - connected to STM component
/Linux-v5.4/arch/arm64/boot/dts/qcom/
Dmsm8916.dtsi1188 * 7 - connected to STM component
/Linux-v5.4/arch/arm/
DKconfig1052 - Cortex-A12 818325: Execution of an UNPREDICTABLE STR or STM
1640 cores where a 8-word STM instruction give significantly higher
/Linux-v5.4/drivers/pinctrl/sh-pfc/
Dpfc-r8a7779.c753 PINMUX_IPSR_GPSR(IP2_11_8, STM),
/Linux-v5.4/
DMAINTAINERS5522 DRM DRIVERS FOR STM