<?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>topic Re: NXP iMX95: ARM SMMU problem with PCIe in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2372262#M245387</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/60868"&gt;@pierluigi_p&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It looks like that the PCIe-USB bridge you are using is accessing SMMU IDs other than the SID and RID allowed by the i.MX95 PCI node.&lt;/P&gt;
&lt;P&gt;Below are the SMMU settings for the i.mx95 PCIe. i think you should figure out the actual SID and RID mapping used by the PCI11400.&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;			iommu-map = &amp;lt;0x000 &amp;amp;smmu 0x10 0x1&amp;gt;,
				    &amp;lt;0x100 &amp;amp;smmu 0x11 0x7&amp;gt;;
			iommu-map-mask = &amp;lt;0x1ff&amp;gt;;&lt;/LI-CODE&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Zhiming&lt;/P&gt;</description>
    <pubDate>Thu, 28 May 2026 06:59:45 GMT</pubDate>
    <dc:creator>Zhiming_Liu</dc:creator>
    <dc:date>2026-05-28T06:59:45Z</dc:date>
    <item>
      <title>NXP iMX95: ARM SMMU problem with PCIe</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2372049#M245379</link>
      <description>&lt;P&gt;Dear NXP support,&lt;/P&gt;&lt;P&gt;we are trying to integrate a PCIe-USB bridge eval kit (&lt;A href="https://www.microchip.com/en-us/development-tool/ev96n38a" target="_blank"&gt;https://www.microchip.com/en-us/development-tool/ev96n38a&lt;/A&gt;) with NXP iMX95 using kernel 6.12.49.&lt;/P&gt;&lt;P&gt;The PCIe bridge successfully completes PCIe enumeration and all endpoints (xHCI controller, i2c controller, etc.) show up when running "lspci".&lt;/P&gt;&lt;P&gt;When plugging in a USB device (flash drive, keyboard, etc.) to a USB port on the PCI11400 eval kit, the following messages are listed&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;[ 1631.912942] arm-smmu-v3 490d0000.iommu: event 0x10 received:&lt;/P&gt;&lt;P&gt;[ 1631.918618] arm-smmu-v3 490d0000.iommu: 0x0000001000000010&lt;/P&gt;&lt;P&gt;[ 1631.924188] arm-smmu-v3 490d0000.iommu: 0x0000020200000000&lt;/P&gt;&lt;P&gt;[ 1631.929760] arm-smmu-v3 490d0000.iommu: 0x0000000000000000&lt;/P&gt;&lt;P&gt;[ 1631.935326] arm-smmu-v3 490d0000.iommu: 0x0000000000000000&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;but no USB device is actually enumerated.&lt;/P&gt;&lt;P&gt;Suspecting some kind of problem with ARM SMMU translation we added "iommu.passthrough=1" to the kernel command line: with this change, the USB devices are correctly enumerated.&lt;/P&gt;&lt;P&gt;However, "iommu.passthrough=1" allows accessing to protected memory regions (i.e. encryption keys) and cannot be considered a valid workaround from a security perspective.&lt;/P&gt;&lt;P&gt;Could you propose any alternative solution ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Pier&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2026 21:22:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2372049#M245379</guid>
      <dc:creator>pierluigi_p</dc:creator>
      <dc:date>2026-05-27T21:22:02Z</dc:date>
    </item>
    <item>
      <title>Re: NXP iMX95: ARM SMMU problem with PCIe</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2372262#M245387</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/60868"&gt;@pierluigi_p&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It looks like that the PCIe-USB bridge you are using is accessing SMMU IDs other than the SID and RID allowed by the i.MX95 PCI node.&lt;/P&gt;
&lt;P&gt;Below are the SMMU settings for the i.mx95 PCIe. i think you should figure out the actual SID and RID mapping used by the PCI11400.&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;			iommu-map = &amp;lt;0x000 &amp;amp;smmu 0x10 0x1&amp;gt;,
				    &amp;lt;0x100 &amp;amp;smmu 0x11 0x7&amp;gt;;
			iommu-map-mask = &amp;lt;0x1ff&amp;gt;;&lt;/LI-CODE&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Zhiming&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2026 06:59:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2372262#M245387</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2026-05-28T06:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: NXP iMX95: ARM SMMU problem with PCIe</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2376769#M245496</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/151788"&gt;@Zhiming_Liu&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;thanks for the suggestion.&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Pier&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2026 10:20:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NXP-iMX95-ARM-SMMU-problem-with-PCIe/m-p/2376769#M245496</guid>
      <dc:creator>pierluigi_p</dc:creator>
      <dc:date>2026-06-04T10:20:58Z</dc:date>
    </item>
  </channel>
</rss>

