<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LayerscapeのトピックRe: LS1046A RDB: GPIOs for testing gpio interrupt handling performance of linux</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2259666#M16332</link>
    <description>&lt;P&gt;You could use the&amp;nbsp;&lt;STRONG&gt;GPIO&lt;/STRONG&gt;&amp;nbsp;muxed with SPI signals.&lt;BR /&gt;GPIO_2[1], GPIO_2[2], GPIO_2[3] SPI interface is unused on RDB and terminated to test points.&lt;/P&gt;
&lt;P&gt;Please refer to "Table 3-8. SPI Signal configuration" in LS1046ARM for details.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Dec 2025 06:28:30 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2025-12-11T06:28:30Z</dc:date>
    <item>
      <title>LS1046A RDB: GPIOs for testing gpio interrupt handling performance of linux</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2257006#M16321</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am working with an LS1046ARDB and want to measure interrupt latency. My goal is to trigger an interrupt via an external signal generator (Input GPIO) and toggle another pin (Output GPIO) in response, measuring the delay with an oscilloscope.&lt;/P&gt;&lt;P&gt;I am looking for accessible pins on the board headers that can be muxed as GPIOs.&lt;BR /&gt;&lt;BR /&gt;My idea is to use the&amp;nbsp;IEEE-1588 Header (J11) but not sure if this will work and what I have to do.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The Reference Manual states that EC2 pins can be configured as GPIO3 via the RCW (EC2=1).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If I set EC2=1 in the RCW, will these signals be routed to J11?&lt;BR /&gt;Are there other easily accessible Pins on the LS1046A RDB I can use for this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks for your help&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 09:01:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2257006#M16321</guid>
      <dc:creator>srechermann</dc:creator>
      <dc:date>2025-12-08T09:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A RDB: GPIOs for testing gpio interrupt handling performance of linux</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2259666#M16332</link>
      <description>&lt;P&gt;You could use the&amp;nbsp;&lt;STRONG&gt;GPIO&lt;/STRONG&gt;&amp;nbsp;muxed with SPI signals.&lt;BR /&gt;GPIO_2[1], GPIO_2[2], GPIO_2[3] SPI interface is unused on RDB and terminated to test points.&lt;/P&gt;
&lt;P&gt;Please refer to "Table 3-8. SPI Signal configuration" in LS1046ARM for details.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2025 06:28:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2259666#M16332</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2025-12-11T06:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A RDB: GPIOs for testing gpio interrupt handling performance of linux</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2259784#M16334</link>
      <description>&lt;P&gt;Thanks for your help! This should work. I found out the&amp;nbsp;&lt;SPAN&gt;GPIO_2[1], GPIO_2[2], GPIO_2[3] correspond to TP14, TP13 and TP11&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2025 08:29:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-RDB-GPIOs-for-testing-gpio-interrupt-handling/m-p/2259784#M16334</guid>
      <dc:creator>srechermann</dc:creator>
      <dc:date>2025-12-11T08:29:31Z</dc:date>
    </item>
  </channel>
</rss>

