https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I3C-zephyr-driver/m-p/1610025#M24008 <P>My question is related to mcux-i3c-driver on zephyr.<BR /><BR />In dtsi, is it necessary to add child node for i3c to test i3c transfer API (<SPAN>mcux_i3c_transfer</SPAN>)?<BR /><BR /></P><DIV><DIV><SPAN>i3c0</SPAN><SPAN>: </SPAN><SPAN>i3c@36000</SPAN><SPAN> {</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; compatible = </SPAN><SPAN>"nxp,mcux-i3c"</SPAN><SPAN>;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; reg = &lt;</SPAN><SPAN>0x36000</SPAN> <SPAN>0x1000</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; interrupts = &lt;</SPAN><SPAN>49</SPAN> <SPAN>0</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clocks = &lt;</SPAN><SPAN>&amp;clkctl1</SPAN> <SPAN>MCUX_I3C_CLK</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider = &lt;</SPAN><SPAN>2</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider-slow = &lt;</SPAN><SPAN>1</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider-'tc = &lt;</SPAN><SPAN>1</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; status = </SPAN><SPAN>"disabled"</SPAN><SPAN>;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; #address-cells = &lt;</SPAN><SPAN>3</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; #size-cells = &lt;</SPAN><SPAN>0</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; };<BR /><BR /></SPAN>Do I need to add a child node also ?<BR />Is it possible to test i3c transfer(<SPAN>mcux_i3c_transfer</SPAN>) just by adding the parent node, not the child node? If yes, then how "bus" member is filled in struct&nbsp;<DIV><SPAN>struct</SPAN><SPAN> i3c_device_desc (i3c.h).<BR /><BR /></SPAN></DIV><DIV><SPAN>#i3c#zephyr#nxp</SPAN></DIV><BR /><BR /></DIV></DIV> Mon, 06 Mar 2023 13:00:34 GMT smtsngh7 2023-03-06T13:00:34Z https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I3C-zephyr-driver/m-p/1610025#M24008 <P>My question is related to mcux-i3c-driver on zephyr.<BR /><BR />In dtsi, is it necessary to add child node for i3c to test i3c transfer API (<SPAN>mcux_i3c_transfer</SPAN>)?<BR /><BR /></P><DIV><DIV><SPAN>i3c0</SPAN><SPAN>: </SPAN><SPAN>i3c@36000</SPAN><SPAN> {</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; compatible = </SPAN><SPAN>"nxp,mcux-i3c"</SPAN><SPAN>;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; reg = &lt;</SPAN><SPAN>0x36000</SPAN> <SPAN>0x1000</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; interrupts = &lt;</SPAN><SPAN>49</SPAN> <SPAN>0</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clocks = &lt;</SPAN><SPAN>&amp;clkctl1</SPAN> <SPAN>MCUX_I3C_CLK</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider = &lt;</SPAN><SPAN>2</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider-slow = &lt;</SPAN><SPAN>1</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; clk-divider-'tc = &lt;</SPAN><SPAN>1</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; status = </SPAN><SPAN>"disabled"</SPAN><SPAN>;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; #address-cells = &lt;</SPAN><SPAN>3</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; &nbsp; &nbsp; #size-cells = &lt;</SPAN><SPAN>0</SPAN><SPAN>&gt;;</SPAN></DIV><DIV><SPAN>&nbsp; &nbsp; };<BR /><BR /></SPAN>Do I need to add a child node also ?<BR />Is it possible to test i3c transfer(<SPAN>mcux_i3c_transfer</SPAN>) just by adding the parent node, not the child node? If yes, then how "bus" member is filled in struct&nbsp;<DIV><SPAN>struct</SPAN><SPAN> i3c_device_desc (i3c.h).<BR /><BR /></SPAN></DIV><DIV><SPAN>#i3c#zephyr#nxp</SPAN></DIV><BR /><BR /></DIV></DIV> Mon, 06 Mar 2023 13:00:34 GMT https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/I3C-zephyr-driver/m-p/1610025#M24008 smtsngh7 2023-03-06T13:00:34Z