Home
last modified time | relevance | path

Searched +full:rt1718s +full:- +full:gpio +full:- +full:port (Results 1 – 7 of 7) sorted by relevance

/Zephyr-Core-3.5.0/dts/bindings/gpio/
Drichtek,rt1718s-gpio-port.yaml2 # SPDX-License-Identifier: Apache-2.0
5 Richtek RT1718S TCPC chip GPIO port
7 "richtek,rt1718s-gpio-port" node handles GPIO feature of the RT1718S TCPC
12 rt1718s_port0: rt1718s@40 {
13 compatible = "richtek,rt1718s";
17 compatible = "richtek,rt1718s-gpio-port";
19 gpio-controller;
20 #gpio-cells = <2>;
26 include: [gpio-controller.yaml, base.yaml]
28 compatible: "richtek,rt1718s-gpio-port"
Drichtek,rt1718s.yaml2 # SPDX-License-Identifier: Apache-2.0
5 Richtek RT1718S TCPC chip
7 The Richtek RT1718S chip is TCPC, but also has 3 pins, which can be used as
8 a usual GPIO. This node collects common proprties for RT1718S chip e.g. I2C
9 address. Feature-specific(GPIO, TCPC) properties should be placed in a child
14 rt1718s_port0: rt1718s@40 {
15 compatible = "richtek,rt1718s";
17 irq-gpios = <&gpioe 1 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
20 compatible = "richtek,rt1718s-gpio-port";
22 gpio-controller;
[all …]
/Zephyr-Core-3.5.0/drivers/gpio/
DKconfig.rt1718s1 # RT1718S driver configuration options
4 # SPDX-License-Identifier: Apache-2.0
7 bool "RT1718S I2C-based TCPC chip with GPIOs"
11 Enable driver GPIO for RT1718S I2C-based TCPC chip.
16 int "RT1718S GPIO init priority"
19 RT1718S device driver initialization priority. The priority should be
23 int "RT1718S GPIO port init priority"
26 RT1718S GPIO driver initialization priority. The priority should be lower
30 bool "RT1718S alert handler"
32 Enable support for handling RT1718S Alert with a GPIO interrupt connected
Dgpio_rt1718s.h4 * SPDX-License-Identifier: Apache-2.0
11 #include <zephyr/drivers/gpio.h>
55 /* RT1718S chip driver config */
59 /* Alert GPIO pin */
61 /* GPIO port device */
65 /* RT1718S chip driver data */
67 /* RT1718S device */
78 * @brief Read a RT1718S register
80 * @param dev RT1718S device
88 const struct rt1718s_config *const config = (const struct rt1718s_config *)dev->config; in rt1718s_reg_read_byte()
[all …]
Dgpio_rt1718s_port.c4 * SPDX-License-Identifier: Apache-2.0
15 #include <zephyr/drivers/gpio.h>
16 #include <zephyr/drivers/gpio/gpio_utils.h>
24 /* RT1718S chip device */
32 /* GPIO callback list */
34 /* lock GPIO registers access */
38 /* GPIO api functions */
41 const struct gpio_rt1718s_port_config *const config = dev->config; in gpio_rt1718s_pin_config()
42 struct gpio_rt1718s_port_data *const data = dev->data; in gpio_rt1718s_pin_config()
48 return -ENOTSUP; in gpio_rt1718s_pin_config()
[all …]
Dgpio_rt1718s.c4 * SPDX-License-Identifier: Apache-2.0
9 * doesn't provide any API itself. The feature-specific API should be provided
10 * in separated files e.g. GPIO API.
12 * This file is placed in drivers/gpio directory, because GPIO is only one
21 #include <zephyr/drivers/gpio.h>
33 k_work_submit(&data->alert_worker); in rt1718s_alert_callback()
39 const struct device *const dev = data->dev; in rt1718s_alert_worker()
40 const struct rt1718s_config *const config = dev->config; in rt1718s_alert_worker()
45 k_sem_take(&data->lock_tcpci, K_FOREVER); in rt1718s_alert_worker()
50 k_sem_give(&data->lock_tcpci); in rt1718s_alert_worker()
[all …]
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.3.rst14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
129 This may cause out-of-tree scripts or commands to fail if they have relied
[all …]