PN7150 device tree

cancel
Showing results for 
Search instead for 
Did you mean: 

PN7150 device tree

507 Views
alassaneg
Contributor II

Hello, I'm trying to use the PN7120 through the device tree but there is a confusion between what the app note ( https://www.nxp.com/docs/en/application-note/AN11697.pdf ) says and the device tree binding: The device tree binding ( https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/net/nfc/nxp-nci.txt ) says that the device tree should be implemented this way :

&i2c2 { npc100: npc100@29

{

compatible = "nxp,nxp-nci-i2c";

reg = <0x29>; clock-frequency = <100000>;

interrupt-parent = <&gpio1>;

interrupts = <29 IRQ_TYPE_LEVEL_HIGH>;

enable-gpios = <&gpio0 30 GPIO_ACTIVE_HIGH>;

firmware-gpios = <&gpio0 31 GPIO_ACTIVE_HIGH>;

};

};

 

The app note says: &i2c{ status = "okay"; pn547: pn547@28 {

compatible = "nxp,pn547";

reg = <0x28>;

clock-frequency = <400000>;

interrupt-gpios = <&gpio2 17 0>;

enable-gpios = <&gpio4 21 0>;

};

};

 

could someone tell me what's the correct implementation?

I already submitted a ticket to NXP but apparently they're not interested with that kind of issue

Tags (1)
0 Kudos
1 Reply

462 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi @alassaneg :

 

From nfc-reader library source code, the sample device tree is as the application note says 

Example:

&i2c{

status = "okay";

pn547: pn547@29 {

compatible = "nxp,pn547";

reg = <0x29>;
clock-frequency = <400000>;

interrupt-gpios = <&gpio2 17 0>;
enable-gpios = <&gpio4 21 0>;
};
};

 

Regards

Daniel

0 Kudos