> -----Original Message----- > From: Shawn Guo [mailto:shawnguo@xxxxxxxxxx] > Sent: Monday, October 8, 2018 2:21 PM > To: Oliver Graute <oliver.graute@xxxxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx; s.hauer@xxxxxxxxxxxxxx; dl-linux-imx > <linux-imx@xxxxxxx>; Fabio Estevam <fabio.estevam@xxxxxxx>; Anson > Huang <anson.huang@xxxxxxx> > Subject: Re: Can't set MX6UL_PAD_LCD_DATA10 register with devicetree > > Copy NXP folks and list. > > On Fri, Oct 05, 2018 at 02:45:19PM +0200, Oliver Graute wrote: > > Hello list, > > > > I try to set the following PAD in my imx6ul devicetree (derived from > > imx6ul-14x14-evk.dts) > > > > MX6UL_PAD_LCD_DATA10__GPIO3_IO15 0x100b0 > > > > but after kernel compiling and booting the register value is not > > changed. A readout with devmem2 show me the wrong value. > > > > devmem2 0x020E03CC > > /dev/mem opened. > > Memory mapped at address 0x76fc4000. > > Read at address 0x020E03CC (0x76fc43cc): 0x000010B0 > > > > Setting the register manually with devmem2 just works fine. > > > > /usr/bin/devmem2 0x020E03CC w 0x000100B0 > > > > other PADs like MX6UL_PAD_GPIO1_IO07__ENET1_MDC I could configure via > > the imx6ul devicetree. > > > > ideas what I'm doing wrong here? > > I tested imx6ul evk with Shawn's for next tree by manual change LCD_DATA10 Pad set to 0x100b0, but did not reproduced your issue. As I don't have devme2 tool in my rootfs, so I tried memtool in NXP released rootfs. root@imx6ul7d:~# /unit_tests/memtool -32 0x20e03cc 1 E Reading 0x1 count starting at address 0x020E03CC 0x020E03CC: 000100B0 I guess you can debug the issue with below approaches: 1) use below cmd to dump pad setting via pinctrl sysfs cat /sys/kernel/debug/pinctrl/20e0000.iomuxc/pinconf-pins | grep LCD_DATA10 2) Enable CONFIG_DEBUG_PINCTRL will make the booting dump all pad settings in register value. Then you may find some clue on it. (May need add 'debug' in kernel boot param) Regards Dong Aisheng > > Best Regards, > > > > Oliver
