<?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>i.MX RT Crossover MCUsのトピックIMX6ULL RGB LCD Pinmux Linux kernel device tree and PCB layout</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMX6ULL-RGB-LCD-Pinmux-Linux-kernel-device-tree-and-PCB-layout/m-p/1604969#M23884</link>
    <description>&lt;P&gt;A custom board in development as little space. The LCD is off the shelf. 24 bit. Board uses an SOM with RGB LCD. The pins on the connector and SOM don't match up nicely, it would means lot of vias. For example the colors pins are on each of the other ends and b0-b7 are on the SOM as b7-0, the worst case of matching up. if the pins could be remapped, for example reverse everything by swapping red and blue and their bits b0-b7 the board layout would be much easier. In the kernel, found&lt;/P&gt;&lt;P&gt;pinctrl_lcdif_dat_24bits: lcdifdatgrp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;MX6UL_PAD_LCD_DATA00__LCDIF_DATA00 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA01__LCDIF_DATA01 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA02__LCDIF_DATA02 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA03__LCDIF_DATA03 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA04__LCDIF_DATA04 0x79&lt;/P&gt;&lt;P&gt;Can these be remapped to anything desired. How is this table interpreted ? for example for an 24 bits list, the entries are R0-R7 , G0-G7 and B0-7, This for example DATA23 could be mapped to R0 etc.. as&lt;/P&gt;&lt;P&gt;pinctrl_lcdif_dat_24bits: lcdifdatgrp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;MX6UL_PAD_LCD_DATA00__LCDIF_DATA23 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA01__LCDIF_DATA22 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA02__LCDIF_DATA21 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA03__LCDIF_DATA20 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA04__LCDIF_DATA19 0x79&lt;/P&gt;</description>
    <pubDate>Fri, 24 Feb 2023 04:29:40 GMT</pubDate>
    <dc:creator>debug</dc:creator>
    <dc:date>2023-02-24T04:29:40Z</dc:date>
    <item>
      <title>IMX6ULL RGB LCD Pinmux Linux kernel device tree and PCB layout</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMX6ULL-RGB-LCD-Pinmux-Linux-kernel-device-tree-and-PCB-layout/m-p/1604969#M23884</link>
      <description>&lt;P&gt;A custom board in development as little space. The LCD is off the shelf. 24 bit. Board uses an SOM with RGB LCD. The pins on the connector and SOM don't match up nicely, it would means lot of vias. For example the colors pins are on each of the other ends and b0-b7 are on the SOM as b7-0, the worst case of matching up. if the pins could be remapped, for example reverse everything by swapping red and blue and their bits b0-b7 the board layout would be much easier. In the kernel, found&lt;/P&gt;&lt;P&gt;pinctrl_lcdif_dat_24bits: lcdifdatgrp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;MX6UL_PAD_LCD_DATA00__LCDIF_DATA00 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA01__LCDIF_DATA01 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA02__LCDIF_DATA02 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA03__LCDIF_DATA03 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA04__LCDIF_DATA04 0x79&lt;/P&gt;&lt;P&gt;Can these be remapped to anything desired. How is this table interpreted ? for example for an 24 bits list, the entries are R0-R7 , G0-G7 and B0-7, This for example DATA23 could be mapped to R0 etc.. as&lt;/P&gt;&lt;P&gt;pinctrl_lcdif_dat_24bits: lcdifdatgrp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;MX6UL_PAD_LCD_DATA00__LCDIF_DATA23 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA01__LCDIF_DATA22 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA02__LCDIF_DATA21 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA03__LCDIF_DATA20 0x79&lt;BR /&gt;MX6UL_PAD_LCD_DATA04__LCDIF_DATA19 0x79&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2023 04:29:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMX6ULL-RGB-LCD-Pinmux-Linux-kernel-device-tree-and-PCB-layout/m-p/1604969#M23884</guid>
      <dc:creator>debug</dc:creator>
      <dc:date>2023-02-24T04:29:40Z</dc:date>
    </item>
  </channel>
</rss>

