hynitron,cst8xx (on i2c bus)
Description
Hynitron CST8XX touchscreen sensor
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
The irq signal defaults to active low as produced by the
sensor. The property value should ensure the flags properly
describe the signal that is presented to the driver.
|
|
|
The reset signal defaults to active low to the
sensor. The property value should ensure the flags properly
describe the signal that is presented to the driver.
|
|
|
Auto-recalibration period during low-power mode in minutes. Range 1–5. The default value is specified in the data sheet.
Default value: Legal values: |
|
|
Low-power scan wake-up threshold. Smaller = more sensitive. The default value is specified in the data sheet.
Default value: Value range: |
|
|
Measurement range for low-power scan. Larger = more sensitive but higher consumption. The datasheet is mentiones values from 0 to 3 as valid options with 3 as default. But you can go higher as it is an 8-bit register and higher values than 3 seem to work fine. They improve the sensitivity further at the cost of power consumption.
Default value: Value range: |
|
|
Frequency for low-power scan. Smaller = more sensitive. The default value is specified in the data sheet.
Default value: Value range: |
|
|
Current for low-power scan. Smaller = more sensitive. The default value is not specified in the data sheet. Instead, 200 is chosen as a reasonable default based on typical usage.
Default value: Value range: |
|
|
Time (in seconds) of inactivity after which the controller automatically enters standby / low-power mode. The default value is specified in the data sheet.
Default value: |
|
|
GPIO specifier that controls power to the device.
This property should be provided when the device has a dedicated
switch that controls power to the device. The supply state is
entirely the responsibility of the device driver.
Contrast with vin-supply.
|
|
|
Reference to the regulator that controls power to the device.
The referenced devicetree node must have a regulator compatible.
This property should be provided when device power is supplied
by a shared regulator. The supply state is dependent on the
request status of all devices fed by the regulator.
Contrast with supply-gpios. If both properties are provided
then the regulator must be requested before the supply GPIOS is
set to an active state, and the supply GPIOS must be set to an
inactive state before releasing the regulator.
|
|
|
Horizontal resolution of touchscreen (maximum x coordinate reported + 1). The default
corresponds to a valid value for non-inverted axis, required for a display with an inverted x
axis.
Default value: |
|
|
Vertical resolution of touchscreen (maximum y coordinate reported + 1). The default
corresponds to a valid value for non-inverted axis, required for a display with an inverted y
axis.
Default value: |
|
|
X axis is inverted.
|
|
|
Y axis is inverted.
|
|
|
X and Y axis are swapped. Swapping is done after inverting the axis.
|
|
|
Optional handle to the display controller this touchscreen feeds. When set, output-width /
output-height are taken from the referenced node's width / height instead of the properties
below, so the panel resolution is not duplicated. Falls back to output-width / output-height
when this is not set.
|
|
|
Horizontal resolution of the display the touchscreen is bonded to. The two pairs name two
different spaces: screen-width / screen-height describe what the touch controller reports,
output-width / output-height describe the panel those reports should land on. When this
and output-height are both set, reported coordinates are scaled from the former into
the latter. Omitting them disables scaling, so coordinates are reported exactly as the
controller produced them. Ignored when display is set, which supplies these
dimensions instead.
Scaling is applied after inverting and swapping, and is what makes swapped-x-y usable on a
rotated panel whose two dimensions differ: the swapped axes carry each other's range, which
a bare swap would leave mismatched against the display.
|
|
|
Vertical resolution of the display the touchscreen is bonded to. See output-width.
|
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 “hynitron,cst8xx” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
device address on i2c bus
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 used to define a mapping (or translation) between the address
space of a bus (the "child address space") and the address space of the
bus node's parent (the "parent address space").
The "ranges" property is typically empty, or a sequence of triplets
(child bus address, parent bus address, length).
If the "ranges" property is empty, it specifies that the parent and child
address spaces are identical and no address translation is required.
If the "ranges" property is not present in a bus node, it is assumed that
no mapping exists between children of the node and the parent address space.
For details, see "2.3.8 ranges" in Devicetree Specification v0.4.
|
|
|
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.
|
|
|
Indicates that the device is capable of coherent DMA operations.
For details, see "2.3.10 dma-coherent" 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.
|