All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Oliver Graute <oliver.graute@gmail.com>
Cc: devicetree@vger.kernel.org, s.hauer@pengutronix.de,
	linux-imx@nxp.com, Fabio Estevam <fabio.estevam@nxp.com>,
	Anson Huang <Anson.Huang@nxp.com>
Subject: Re: Can't set MX6UL_PAD_LCD_DATA10 register with devicetree
Date: Mon, 8 Oct 2018 14:21:05 +0800	[thread overview]
Message-ID: <20181008062102.GJ3587@dragon> (raw)
In-Reply-To: <20181005124519.GA7699@graute-opti>

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?
> 
> Best Regards,
> 
> Oliver

  reply	other threads:[~2018-10-08 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 12:45 Can't set MX6UL_PAD_LCD_DATA10 register with devicetree Oliver Graute
2018-10-08  6:21 ` Shawn Guo [this message]
2018-10-09  2:55   ` A.s. Dong
2018-10-09  3:27   ` A.s. Dong
2018-10-09  9:15     ` Oliver Graute
2018-10-08 20:22 ` Fabio Estevam
2018-10-09  6:28   ` Oliver Graute
2018-10-09  7:48     ` Vokáč Michal
2018-10-09  9:20       ` Oliver Graute
2018-10-09 11:00         ` Fabio Estevam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181008062102.GJ3587@dragon \
    --to=shawnguo@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=oliver.graute@gmail.com \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.