infineon,tle927x (on spi bus)

Description

These nodes are “tle927x” bus nodes.

Infineon TLE927x high-end System Basis Chip (SBC).

The binding covers all TLE927x variants. They differ only in the VCC1
voltage and the number of LIN transceivers (FAM_PROD_STAT.PROD), which the
driver does not depend on.

The SPI interface runs at up to 4 MHz, so spi-max-frequency must be set
accordingly. The SBC requires SPI mode 1 (CPOL=0, CPHA=1) and LSB-first
transfers, which the driver sets itself.

The watchdog, the VCC2 regulator, the HS-CAN transceiver and the reset cause
(hwinfo) are exposed as child nodes. VCC1 has no software enable, voltage or
mode, so it is not a regulator device: its supervision is configured by the
properties below and its faults are reported through
mfd_tle927x_read_faults() in SUP_STAT (VCC1_UV, VCC1_OV, VCC1_SC).

The fail-safe input (FSI) and the WK pin wake source are not supported. The
driver disables both at init: HW_CTRL.FSI_FO2 is set, so the FSI pin works
as the FO2 output, and WK_CTRL_2.WK_EN is cleared.

The application must install and set up the watchdog early. The long open
window starts when RO is released, not when the first SPI command is sent
(datasheet 5.1.1), so the deadline covers the whole boot: startup software,
clock init, driver init and the first watchdog feed together must fit inside
the minimum 240 ms. A boot that takes longer causes a watchdog reset.

Properties

Properties not inherited from the base binding file.

Name

Type

Details

reset-threshold

string

VCC1 undervoltage reset threshold, M_S_CTRL.VCC1_RT. VCC1 is the buck
output supplying the microcontroller. "vrt1" is the highest threshold and
matches the power-on-reset value. "disabled" turns off the VCC1 undervoltage
reset entirely, in which case undervoltage detection must be done outside the SBC.

Default value: vrt1

Legal values: vrt1, vrt2, vrt3, disabled

overvoltage-reset

boolean

Set M_S_CTRL.VCC1_OV_RST so a VCC1 overvoltage triggers a reset and the
SBC enters Restart mode. Off by default, matching the power-on-reset
value.

spi-max-frequency

int

Maximum clock frequency of device's SPI interface in Hz

This property is required.

duplex

int

Duplex mode, full or half. By default it's always full duplex thus 0
as this is, by far, the most common mode.
Use the macros not the actual enum value, here is the concordance
list (see dt-bindings/spi/spi.h)
  0    SPI_FULL_DUPLEX
  2048 SPI_HALF_DUPLEX

Default value: 0

Legal values: 0, 2048

frame-format

int

Motorola or TI frame format. By default it's always Motorola's,
thus 0 as this is, by far, the most common format.
Use the macros not the actual enum value, here is the concordance
list (see dt-bindings/spi/spi.h)
  0     SPI_FRAME_FORMAT_MOTOROLA
  32768 SPI_FRAME_FORMAT_TI

Default value: 0

Legal values: 0, 32768

spi-cpol

boolean

SPI clock polarity which indicates the clock idle state.
If it is used, the clock idle state is logic high; otherwise, low.

spi-cpha

boolean

SPI clock phase that indicates on which edge data is sampled.
If it is used, data is sampled on the second edge; otherwise, on the first edge.

spi-lsb-first

boolean

The device requires least significant bit first data mode.

spi-hold-cs

boolean

In some cases, it is necessary for the controller to manage SPI chip select
under software control, so that multiple spi transactions can be performed
without releasing it. A typical use case is variable length SPI packets
where the first spi transaction reads the length and the second spi transaction
reads length bytes.

spi-cs-high

boolean

The device requires the chip select to be active high.

spi-interframe-delay-ns

int

Delay in nanoseconds between SPI words.
Default of 0 is special value which will assume to mean half of the SCK period.

Default value: 0

spi-cs-setup-delay-ns

int

Delay in nanoseconds to be introduced by the controller after CS is asserted.
Also known as enable lead time.

spi-cs-hold-delay-ns

int

Delay in nanoseconds to be introduced by the controller before the CS is de-asserted.
 Also known as enable lag time.

supply-gpios

phandle-array

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.

vin-supply

phandle

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.