How to declare a single GPIO-Pin which is not an LED in boards dts file?

RE: How to declare a single GPIO-Pin which is not an LED in boards dts file?

zsn — Wed, 05 Apr 2023 11:23:31 GMT

I would create a yaml file call, for example, gpio-outputs.yaml. and copy gpio-leds.yaml context into it and modify

# Copyright (c) 2018, Linaro Limited
# SPDX-License-Identifier: Apache-2.0

compatible: "gpio-outputs"

child-binding:
    description: GPIO output child node
    properties:
       gpios:
          type: phandle-array
          required: true
       label:
          required: false
          type: string
          description: |
            Human readable string describing the pin. It can be used by an
            application to identify this pin or to retrieve its number/index
            (i.e. child node number) on the parent device.

and you can copy this file either into your project/boards/bindings or zephyr/dts/bindings/gpio. Both will work.

if you copy into your project it will be valid for only that project, but if you copy into zephyr/dts then you can use it for all your project

RE: How to declare a single GPIO-Pin which is not an LED in boards dts file?

longo92 — Wed, 04 Jan 2023 16:29:06 GMT

I resuming this post in order to know if someone know a method. I get bored seeing that I have to use something led-retaled to control a mosfet.

RE: How to declare a single GPIO-Pin which is not an LED in boards dts file?

xmoex — Mon, 17 Oct 2022 11:02:39 GMT

No issue here, controlling the pins works fine. I just wasn't sure if accessing the Pins via gpio-leds was the "right" way to do it...

RE: How to declare a single GPIO-Pin which is not an LED in boards dts file?

Øivind — Fri, 14 Oct 2022 14:29:00 GMT

Hi,

You should be able to control a gpio with gpio-leds by using the gpio API.

Look at how the led is handled in zephyr/samples/basic/button. It is just an output GPIO that happens to be connected to an LED.

Are you having any issues replicating that with the gpio-leds node you posted?