<?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>Other NXP ProductsのトピックRe: LS1043a IRQ00 IRQ01 IRQ02 interruption handler</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1200589#M10067</link>
    <description>&lt;P&gt;IRQ00 and IRQ01 are dedicated interrupt request inputs. In theory, the software&lt;BR /&gt;can read their status as if they were GP inputs, however, there are no provisions&lt;BR /&gt;for that in Linux.&lt;/P&gt;
&lt;P&gt;If you have an external peripheral connected to these pins, the best strategy&lt;BR /&gt;is to use the existing driver for it. You may need to slightly modify the &lt;BR /&gt;driver if it does not support Device Tree.&lt;/P&gt;
&lt;P&gt;If you are to implement such driver by yourself (note, drivers are for peripherals,&lt;BR /&gt;not for interrupts), familiarize with the concept of &lt;A href="https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3" target="_self"&gt;Device Trees&lt;/A&gt; and the structure&lt;BR /&gt;of the 'interrupts' property for peripherals connected to &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt" target="_self"&gt;GIC-400&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Any on-chip interrupt-enabled peripheral driver can be used as an example.&lt;BR /&gt;You can take a look at &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/i2c/busses/i2c-imx.c" target="_self"&gt;I2C&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/spi/spi-fsl-dspi.c" target="_self"&gt;SPI&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/crypto/caam/jr.c" target="_self"&gt;CAAM&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/dma/fsl-edma.c" target="_self"&gt;eDMA&lt;/A&gt;, etc. There is no difference&lt;BR /&gt;between on-chip and external peripheral driver from the interrupt handling &lt;BR /&gt;standpoint.&lt;/P&gt;
&lt;P&gt;No modifications to RCW are necessary to use IRQ00 or IRQ01 pins.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;BR /&gt;Platon&lt;/P&gt;</description>
    <pubDate>Wed, 16 Dec 2020 18:27:20 GMT</pubDate>
    <dc:creator>bpe</dc:creator>
    <dc:date>2020-12-16T18:27:20Z</dc:date>
    <item>
      <title>LS1043a IRQ00 IRQ01 IRQ02 interruption handler</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1198040#M10035</link>
      <description>&lt;P&gt;IRQ00 , IRQ01 and IRQ IRQ02 are signals input.&lt;/P&gt;&lt;P&gt;A level on these input cause a processor interrupt.&lt;/P&gt;&lt;P&gt;If if want to catch these interruption did i need to do:&lt;/P&gt;&lt;P&gt;-&amp;nbsp;add these interrupts in the rcw configuration ?&lt;BR /&gt;- implement a linux module to catch these interrupt ?&lt;/P&gt;&lt;P&gt;- do you have an example of interrupt handler for the ls1043a ?&lt;/P&gt;&lt;P&gt;Thank you for your help&lt;/P&gt;&lt;P&gt;Bahi&lt;/P&gt;</description>
      <pubDate>Fri, 11 Dec 2020 10:38:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1198040#M10035</guid>
      <dc:creator>bahi</dc:creator>
      <dc:date>2020-12-11T10:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a IRQ00 IRQ01 IRQ02 interruption handler</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1198112#M10037</link>
      <description>&lt;P&gt;&lt;SPAN&gt;is it possible to configure the ls1043a soc so that the gpio driver considers the IRQ00 IRQ01 and IRQ02 inputs as GPIO inputs, in order to be able to read these inputs in polling and not with an interrupt handler?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Bahi&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Dec 2020 13:45:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1198112#M10037</guid>
      <dc:creator>bahi</dc:creator>
      <dc:date>2020-12-11T13:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043a IRQ00 IRQ01 IRQ02 interruption handler</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1200589#M10067</link>
      <description>&lt;P&gt;IRQ00 and IRQ01 are dedicated interrupt request inputs. In theory, the software&lt;BR /&gt;can read their status as if they were GP inputs, however, there are no provisions&lt;BR /&gt;for that in Linux.&lt;/P&gt;
&lt;P&gt;If you have an external peripheral connected to these pins, the best strategy&lt;BR /&gt;is to use the existing driver for it. You may need to slightly modify the &lt;BR /&gt;driver if it does not support Device Tree.&lt;/P&gt;
&lt;P&gt;If you are to implement such driver by yourself (note, drivers are for peripherals,&lt;BR /&gt;not for interrupts), familiarize with the concept of &lt;A href="https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3" target="_self"&gt;Device Trees&lt;/A&gt; and the structure&lt;BR /&gt;of the 'interrupts' property for peripherals connected to &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt" target="_self"&gt;GIC-400&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Any on-chip interrupt-enabled peripheral driver can be used as an example.&lt;BR /&gt;You can take a look at &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/i2c/busses/i2c-imx.c" target="_self"&gt;I2C&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/spi/spi-fsl-dspi.c" target="_self"&gt;SPI&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/crypto/caam/jr.c" target="_self"&gt;CAAM&lt;/A&gt;, &lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/dma/fsl-edma.c" target="_self"&gt;eDMA&lt;/A&gt;, etc. There is no difference&lt;BR /&gt;between on-chip and external peripheral driver from the interrupt handling &lt;BR /&gt;standpoint.&lt;/P&gt;
&lt;P&gt;No modifications to RCW are necessary to use IRQ00 or IRQ01 pins.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;BR /&gt;Platon&lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2020 18:27:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/LS1043a-IRQ00-IRQ01-IRQ02-interruption-handler/m-p/1200589#M10067</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2020-12-16T18:27:20Z</dc:date>
    </item>
  </channel>
</rss>

