Zephyr new device binding

RE: Zephyr new device binding

MPDeveloper89 — Tue, 13 Dec 2022 12:52:50 GMT

Hello,

Issue can be considered closed.

Your suggestion has been very useful and functional.

Thank you.

RE: Zephyr new device binding

MPDeveloper89 — Tue, 09 Aug 2022 15:03:55 GMT

Thank you.

So, in my .yaml file the include file was missing and I had the following "issue":

Let me say, It's no an issue because building was ok and I device was reachable using I2C scan.

Anyway, adding the include field the red underline disappear. Thank you.

For the interrupt, I will try with your advice and I will back.

RE: Zephyr new device binding

Øivind — Tue, 09 Aug 2022 14:51:00 GMT

Hi,

What does your .yaml file look like? I would expect it to have a compatible field with "renesas,mydevice" and an include field with i2c-device.yaml.

If that is the case, just add a property for the interrupt gpio:

compatible: "renesas,mydevice"

include: i2c-device.yaml

properties:
    int-gpios:
      type: phandle-array
      required: true

Then you can assign a gpio pin to your mydevice node in the dts file:

&i2c1 {
	compatible = "nordic,nrf-twim";
	status = "okay";
	sda-pin = <34>;
	scl-pin = <35>;

	mydevice@53{
		compatible = "renesas,mydevice";
		label = "MYDEVICE";
		reg = <0x53>;
		int-gpios = <&gpio1 4 0>;
	};
};

For implementation, you can try looking at the driver for the adt7420, which seems to make use of an interrupt pin.

https://github.com/nrfconnect/sdk-zephyr/blob/v2.7.99-ncs1-1/drivers/sensor/adt7420/adt7420.c#L223-L231