renesas,smartbond-uart
Vendor: Renesas Electronics Corporation
Description
These nodes are “uart” bus nodes.
Renesas SmartBond(tm) UART
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Clock frequency information for UART operation
|
|
|
Initial baud rate setting for UART. Only a fixed set of baud
rates are selectable on these devices.
Legal values: |
|
|
Set to enable RTS/CTS flow control at boot time
|
|
|
Configures the parity of the adapter. Enumeration id 0 for none, 1 for odd
and 2 for even parity. Default to none if not specified.
Legal values: |
|
|
Sets the number of stop bits.
Legal values: |
|
|
Sets the number of data bits.
Legal values: |
|
|
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.
|
|
|
Peripheral clock register configuration (COM domain)
This property is required. |
|
|
Set to indicate RTS/CTS flow control is supported.
|
|
|
GPIO configured as wake source
|
|
|
Time to prevent UART entering sleep mode after receiving data (ms)
|
|
|
DTR pin specification. DTR pin when active tells that the driver that there
is active client on the other side of serial line.
The device driver does not use DTR for hardware flow control.
When device is connected to computer serial converter usually asserts DTR
line when serial port is opened and ready for communication.
This line can be used in Smartbond(tm) driver to detect remote client presence.
If client is not present the device can disable UART, allowing for
power system management to enter more efficient power levels.
|
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 “renesas,smartbond-uart” 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
This property is required. 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().
|