nxp,pcf8523 (on i2c bus)
Vendor: NXP Semiconductors N.V.
Description
NXP PCF8523 RTC
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Number of alarms supported by RTC device. The number of
alarms defaults to 0, which indicates that the RTC has
no alarms.
|
|
|
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.
|
|
|
Capacitive load of the quartz crystal in femtofarads (fF). Default is 7000 femtofarads (equal
to 7pF) which corresponds to the reset value of the CAP_SEL field in the "Control 1" register
of the PCF8523.
Default value: Legal values: |
|
|
Frequency of the CLKOUT signal in Hertz (Hz). Default is 32768 Hz which corresponds to the
reset value of the COF field in the Tmr_CLKOUT_ctrl register of the PCF8523. Set to 0 to
disable the CLKOUT signal (High-Z).
Default value: Legal values: |
|
|
Battery switch-over function selection:
- standard: The power failure condition happens when VDD < VBAT and VDD < Vth(sw)bat
- direct: The power failure condition happens when VDD < VBAT
- disabled: Battery switch-over disabled - only one power supply (VDD)
This property is required. Legal values: |
|
|
GPIO connected to the PC8523 INT1 interrupt output. This signal is open-drain, active low.
|
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,pcf8523” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
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.
|
|
|
Power domain the device belongs to.
The device will be notified when the power domain it belongs to is either
suspended or resumed.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|
|
|
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. |
|
|
register space
This property is required. See Important properties for more information. |
|
|
name of each register space
|
|
|
interrupts for device
See Important properties for more information. |
|
|
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
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|