Home
last modified time | relevance | path

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

1234

/openbmc/linux/Documentation/driver-api/iio/
H A Dhw-consumer.rst4 An IIO device can be directly connected to another device in hardware. In this
5 case the buffers between IIO provider and IIO consumer are handled by hardware.
6 The Industrial I/O HW consumer offers a way to bond these IIO devices without
12 * :c:func:`iio_hw_consumer_alloc` — Allocate IIO hardware consumer
13 * :c:func:`iio_hw_consumer_free` — Free IIO hardware consumer
14 * :c:func:`iio_hw_consumer_enable` — Enable IIO hardware consumer
15 * :c:func:`iio_hw_consumer_disable` — Disable IIO hardware consumer
21 As standard IIO device the implementation is based on IIO provider/consumer.
22 A typical IIO HW consumer setup looks like this::
H A Dcore.rst16 * iio_device_register() - register a device with the IIO subsystem
17 * iio_device_unregister() - unregister a device from the IIO
20 An IIO device usually corresponds to a single hardware sensor and it
22 Let's first have a look at the functionality embedded in an IIO device
23 then we will show how a device driver makes use of an IIO device.
46 1. iio_device_unregister(), unregister the device from the IIO core.
47 2. iio_device_free(), free the memory allocated for the IIO device.
49 IIO device sysfs interface
66 IIO device channels
71 An IIO device channel is a representation of a data channel. An IIO device can
[all …]
H A Dtriggers.rst9 * :c:func:`iio_trigger_validate_own_device` — Check if a trigger and IIO
14 An IIO trigger can be provided by a device driver that also has an IIO device
21 IIO trigger sysfs interface
27 IIO trigger is registered with the IIO core and corresponds to trigger
42 IIO trigger setup
60 /* now register the trigger with the IIO core */
63 IIO trigger ops
H A Dtriggered-buffers.rst7 IIO triggered buffer setup
54 after disable). If not specified, the IIO core uses the default
59 timestamp and for this reason one can use the IIO core defined
H A Dintro.rst7 The main purpose of the Industrial I/O subsystem (IIO) is to provide support
15 In some cases there is considerable overlap between these and IIO.
/openbmc/linux/Documentation/translations/zh_CN/iio/
H A Diio_configfs.rst12 工业 IIO configfs支持
18 Configfs是一种内核对象的基于文件系统的管理系统，IIO使用一些可以通过
26 为了使configfs支持IIO，我们需要在编译时选中config的CONFIG_IIO_CONFIGFS
34 此时，将创建所有默认IIO组，并可以在/ config / iio下对其进行访问。 下一章
35 将介绍可用的IIO配置对象。
40 IIO默认configfs组之一是“触发器”组。挂载configfs后可以自动访问它，并且可
43 IIO软件触发器为创建多种触发器类型提供了支持。通常在include/linux/iio
57 * 这将分配并注册一个IIO触发器以及其他触发器类型特性的初始化。
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-devices-mapping5 Each IIO stack (PCIe root port) has its own IIO PMON block, so
7 for PCIe root port, which can be monitored by that IIO PMON
9 For example, on 4-die Xeon platform with up to 6 IIO stacks per
10 die and, therefore, 6 IIO PMON blocks per die, the mapping of
11 IIO PMON block 0 exposes as the following::
31 IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000
32 IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000
33 IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000
34 IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000
H A Dconfigfs-iio7 directory. It contains sub-groups corresponding to IIO
21 will result in creating a hrtimer trigger in the IIO subsystem.
33 Dummy IIO devices directory. Creating a directory here will result
34 in creating a dummy IIO device in the IIO subsystem.
/openbmc/linux/drivers/iio/common/scmi_sensors/
H A DKconfig2 # IIO over SCMI
6 menu "IIO SCMI Sensors"
9 tristate "IIO SCMI"
14 Say yes here to build support for IIO SCMI Driver.
15 This provides ARM SCMI Protocol based IIO device.
/openbmc/linux/drivers/iio/
H A DKconfig6 menuconfig IIO config
13 if IIO
16 bool "Enable buffer support within IIO"
26 tristate "Enable IIO configuration via configfs"
29 This allows configuring various IIO bits through configfs
39 Provides IIO core support for triggers. Currently these
53 tristate "Enable software IIO device support"
56 Provides IIO core support for software devices. A software
64 Provides IIO core support for software triggers. A software
77 Framework to handle complex IIO aggregate devices. The typical
[all …]
/openbmc/linux/Documentation/iio/
H A Diio_configfs.rst2 Industrial IIO configfs support
8 Configfs is a filesystem-based manager of kernel objects. IIO uses some
18 In order to use configfs support in IIO we need to select it at compile
26 At this point, all default IIO groups will be created and can be accessed
27 under /config/iio. Next chapters will describe available IIO configuration
33 One of the IIO default configfs groups is the "triggers" group. It is
37 IIO software triggers implementation offers support for creating multiple
51 * This allocates and registers an IIO trigger plus other
H A Dbno055.rst18 This driver supports also IIO buffers.
47 In non-fusion mode the IIO 'offset' attributes provide access to the
49 the accel, angvel and magn IIO attributes. In fusion mode they are not
/openbmc/linux/drivers/iio/common/hid-sensors/
H A DKconfig5 menu "Hid Sensor IIO Common"
8 tristate "Common modules for all HID Sensor IIO drivers"
13 HID sensor common processing for attributes and IIO triggers.
19 tristate "Common module (trigger) for all HID Sensor IIO drivers"
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Daudio-iio-aux.yaml7 title: Audio IIO auxiliary
40 Invert the sound control value compared to the IIO channel raw value.
42 minimum sound control value correspond to the maximum IIO channel
44 minimum IIO channel raw value.
47 minimum (resp maximum) IIO channel raw value.
/openbmc/linux/drivers/iio/buffer/
H A DKconfig8 tristate "IIO callback buffer used for push in-kernel interfaces"
16 Provides the generic IIO DMA buffer infrastructure that can be used by
17 drivers for devices with DMA support to implement the IIO buffer.
26 Provides a bonding of the generic IIO DMA buffer infrastructure with the
36 Provides a way to bonding when an IIO device has a direct connection
/openbmc/linux/drivers/staging/iio/Documentation/
H A Dinkernel.txt3 The IIO subsystem can act as a layer under other elements of the kernel
17 adc_channel_label identifies the channel on the IIO device by being
27 An array of these structures is then passed to the IIO driver.
36 The result of this is that the IIO core now has all the information needed
39 Acting as an IIO consumer (consumer.h)
/openbmc/linux/drivers/iio/test/
H A DKconfig8 tristate "Test IIO rescale conversion functions" if !KUNIT_ALL_TESTS
20 tristate "Test IIO formatting functions" if !KUNIT_ALL_TESTS
24 build unit tests for the IIO formatting functions.
/openbmc/phosphor-hwmon/
H A DREADME.iio.md1 # Phosphor OpenBMC and IIO devices
3 Phosphor OpenBMC currently does not provide an IIO device to DBUS bridge in the
12 If a true IIO bridging daemon becomes available in the future,
/openbmc/linux/drivers/staging/iio/
H A DKconfig5 menu "IIO staging drivers"
6 depends on IIO
/openbmc/linux/drivers/iio/multiplexer/
H A DKconfig10 tristate "IIO multiplexer driver"
13 Say yes here to build support for the IIO multiplexer.
/openbmc/linux/drivers/iio/afe/
H A DKconfig10 tristate "IIO rescale"
12 Say yes here to build support for the IIO rescaling
/openbmc/linux/drivers/iio/common/cros_ec_sensors/
H A DKconfig12 Contains core functions used by other IIO CrosEC sensor
23 Creates an IIO device for each functions.
/openbmc/linux/drivers/iio/trigger/
H A DKconfig13 Provides a frequency based IIO trigger using high resolution
22 Provides support for using an interrupt of any type as an IIO
65 Provides support for using SYSFS entries as IIO triggers.
/openbmc/linux/drivers/iio/dummy/
H A DKconfig5 menu "IIO dummy driver"
6 depends on IIO
/openbmc/linux/Documentation/devicetree/bindings/phy/
H A Dphy-cpcap-usb.txt9 io-channels: IIO ADC channels used by the USB PHY
10 io-channel-names: IIO ADC channel names

1234