nxp,mcux-qdec
Vendor: NXP Semiconductors
Note
An implementation of a driver matching this compatible is available in drivers/sensor/nxp/qdec_mcux/qdec_mcux.c.
Description
NXP MCUX QDEC
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
---|---|---|
|
|
This is a number that is used to determine how many revolutions
were done based on the current counter's value.
This property is required. |
|
|
Bypass the quadrature decoder. A positive transition of the PHASEA input
generates a count signal. The PHASEB input and the REV bit control the
counter direction.
|
|
|
The number of consecutive samples that must agree prior to the input
filter accepting an input transition. A value of 0 represents 3
samples. A value of 7 represents 10 samples.
Legal values: |
|
|
The sampling period (in IPBus clock cycles) of the decoder input signals.
Each input is sampled multiple times at the rate specified by the Filter
Sample Period. If FILT_PER is 0 (default), then the input filter is
bypassed. Bypassing the digital filter enables the position/position
difference counters to operate with count rates up to the IPBus
frequency. Turning on the input filter introduces a latency of:
((FILT_CNT + 3) * FILT_PER) FILT clock cycles + 2 IPBus clock periods.
|
|
|
The xbar phandle.
This property is required. |
|
|
Pin configuration/s for the first state. Content is specific to the
selected pin controller driver implementation.
|
|
|
Pin configuration/s for the second state. See pinctrl-0.
|
|
|
Pin configuration/s for the third state. See pinctrl-0.
|
|
|
Pin configuration/s for the fourth state. See pinctrl-0.
|
|
|
Pin configuration/s for the fifth state. See pinctrl-0.
|
|
|
Names for the provided states. The number of names needs to match the
number of states.
|
|
|
Human readable string describing the sensor. It can be used to
distinguish multiple instances of the same model (e.g., lid accelerometer
vs. base accelerometer in a laptop) to a host operating system.
This property is defined in the Generic Sensor Property Usages of the HID
Usage Tables specification
(https://usb.org/sites/default/files/hut1_3_0.pdf, section 22.5).
|
Deprecated properties not inherited from the base binding file.
(None)
Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “nxp,mcux-qdec” compatible.
Name |
Type |
Details |
---|---|---|
|
|
register space
This property is required. See Important properties for more information. |
|
|
interrupts for device
This property is required. See Important properties for more information. |
|
|
indicates the operational status of a device
Legal values: See Important properties for more information. |
|
|
compatible strings
This property is required. See Important properties for more information. |
|
|
name of each register space
|
|
|
extended interrupt specifier for device
|
|
|
name of each interrupt
|
|
|
phandle to interrupt controller node
|
|
|
Human readable string describing the device (used as device_get_binding() argument)
See Important properties for more information. This property is deprecated. |
|
|
Clock gate information
|
|
|
name of each clock
|
|
|
number of address cells in reg property
|
|
|
number of size cells in reg property
|
|
|
DMA channels specifiers
|
|
|
Provided names of DMA channel specifiers
|
|
|
IO channels specifiers
|
|
|
Provided names of IO channel specifiers
|
|
|
mailbox / IPM channels specifiers
|
|
|
Provided names of mailbox / IPM channel specifiers
|
|
|
Power domain specifiers
|
|
|
Provided names of power domain specifiers
|
|
|
Number of cells in power-domains property
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|