<?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: read/write reg in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1748208#M214867</link>
    <description>&lt;P&gt;Recommend you use regmap framework to operate regs&lt;/P&gt;</description>
    <pubDate>Mon, 30 Oct 2023 02:39:20 GMT</pubDate>
    <dc:creator>Zhiming_Liu</dc:creator>
    <dc:date>2023-10-30T02:39:20Z</dc:date>
    <item>
      <title>read/write reg</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1747492#M214790</link>
      <description>&lt;P&gt;I wrote the device driver code for the SPI slave device mounted under the spi device tree node, and it works normally. But now I have a requirement for fast communication. I do not use APIs such as kernel spi_sync during transmission, and choose to directly operate the SPI register. I found that it will cause the kernel to hang directly. When matching the device driver, I used ioremap again to obtain the starting virtual address of the hardware SPI, and then directly operated the offset (register) of the starting address in the device driver file, but the kernel hung. What is this? The reason? Is it because Ioremap uses the same SPI memory twice? Or is there a conflict with spi_imx.c when using functions such as readl?&lt;BR /&gt;Please answer it. Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 03:09:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1747492#M214790</guid>
      <dc:creator>rainho</dc:creator>
      <dc:date>2023-10-27T03:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: read/write reg</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1748208#M214867</link>
      <description>&lt;P&gt;Recommend you use regmap framework to operate regs&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2023 02:39:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1748208#M214867</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2023-10-30T02:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: read/write reg</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1748256#M214872</link>
      <description>&lt;P&gt;thanks for the reply!&lt;BR /&gt;I probably know about the regmap operation, but I'm not sure whether it is a safe operation, or whether it can be used directly in interrupts?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2023 03:56:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1748256#M214872</guid>
      <dc:creator>rainho</dc:creator>
      <dc:date>2023-10-30T03:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: read/write reg</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1749848#M215010</link>
      <description>&lt;P&gt;Avoid using ioremap,&amp;nbsp; regmap is more safety.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 00:27:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/read-write-reg/m-p/1749848#M215010</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2023-11-01T00:27:30Z</dc:date>
    </item>
  </channel>
</rss>

