microchip,ac-g1-comparator
Description
Microchip G1 Analog Comparator
Binding for the Microchip Comparator driver supporting AC G1 peripherals.
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Comparator channel index (0 or 1).
This property is required. Legal values: |
|
|
Enable single-shot mode operation. When enabled, the comparator performs a single comparison
and disables itself. This must be disabled for continuous-mode features like hysteresis.
|
|
|
Positive input source selection (MUXPOS):
- pin0: I/O pin 0 (0x0)
- pin1: I/O pin 1 (0x1)
- pin2: I/O pin 2 (0x2)
- pin3: I/O pin 3 (0x3)
- vscale: VDDANA scaler (0x4)
Legal values: |
|
|
Negative input source selection (MUXNEG):
- pin0: I/O pin 0 (0x0)
- pin1: I/O pin 1 (0x1)
- pin2: I/O pin 2 (0x2)
- pin3: I/O pin 3 (0x3)
- gnd: Ground (0x4)
- vscale: VDDANA scaler (0x5)
- bandgap: Internal bandgap voltage (0x6)
- dac: DAC output (0x7)
Legal values: |
|
|
VSCALE = (VDDANA * (value + 1)) / 64
Only used when either positive or negative input is configured as "vscale".
Valid range: 0 to 63
|
|
|
Comparator output routing mode:
- off: Output is not routed to COMPn I/O pin (0x0)
- async: Asynchronous output is routed (0x1)
- sync: Synchronous filtered output is routed (0x2)
Default value: Legal values: |
|
|
Keep the comparator running in standby mode (when the core is sleeping).
|
|
|
Enable hysteresis on comparator output.
This is only valid when single-shot mode is disabled (i.e., in continuous mode).
|
|
|
Hysteresis voltage level to apply when hysteresis is enabled:
- hyst50: 50 mV (0x0)
- hyst100: 100 mV (0x1)
- hyst150: 150 mV (0x2)
This setting is effective only if hysteresis is enabled and single-shot mode is disabled.
Default value: Legal values: |
|
|
Output filtering (debounce) mode:
- off: No filtering (0x0)
- maj3: 3-bit majority filter (2 of 3) (0x1)
- maj5: 5-bit majority filter (3 of 5) (0x2)
Default value: Legal values: |
|
|
Swap the comparator inputs and invert the output:
- false: MUXPOS → positive input, MUXNEG → negative input
- true: MUXNEG → positive input, MUXPOS → negative input (output inverted)
This can be used for offset cancellation.
It must be configured before enabling the comparator.
|
|
|
Enable the event input path for the comparator.
|
|
|
Enable the event output path for the comparator.
|
|
|
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.
|
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 “microchip,ac-g1-comparator” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Base address of AC peripheral and its size
This property is required. See Important properties for more information. |
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" 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.
|