This is the documentation for the latest (main) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.

richtek,rt1718s (on i2c bus)

Vendor: Richtek Technology Corporation

Description

Richtek RT1718S TCPC chip

The Richtek RT1718S chip is TCPC, but also has 3 pins, which can be used as
a usual GPIO. This node collects common proprties for RT1718S chip e.g. I2C
address. Feature-specific(GPIO, TCPC) properties should be placed in a child
node e.g. a number of GPIOs.

Example:
  &i2c2_0 {
      rt1718s_port0: rt1718s@40 {
          compatible = "richtek,rt1718s";
          reg = <0x40>;
          irq-gpios = <&gpioe 1 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;

          rt1718s_gpio_port0: rt1718s_gpio {
              compatible = "richtek,rt1718s-gpio-port";

              gpio-controller;
              #gpio-cells = <2>;
              ngpios = <3>;
          };
      };
  };

Properties

Properties not inherited from the base binding file.

Name

Type

Details

irq-gpios

phandle-array

Interrupt GPIO pin connected from the chip(IRQB)

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.