From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: imx6qdl, weim ranges and gpr1
Date: Mon, 10 Feb 2014 23:10:30 +0800 [thread overview]
Message-ID: <20140210151027.GP9628@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <20140210001547.GA28084@frolo.macqel>
On Mon, Feb 10, 2014 at 01:15:47AM +0100, Philippe De Muyter wrote:
> Hello linux on i.mx6 experts,
>
> on our i.mx6q/dl-based custom hardware we have used the weim interface to
> connect some peripherals. Our weim dts description looks like that:
>
> &weim {
> compatible = "fsl,imx6q-weim";
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_weim_sram_1>;
> clocks = <&clks 196>;
> reg = <0x021b8000 0x4000>;
> #address-cells = <2>;
> #size-cells = <1>;
> ranges = <0 0 0x08000000 0x04000000>, /* 64Mb for CS0 */
> <1 0 0x0c000000 0x04000000>; /* 64Mb for CS1 */
> status = "okay";
>
> ...
> };
>
> Actually, to achieve this mapping, I must configure some bits in IOMUXC_GPR1,
> like that:
> regmap_update_bits(gpr, IOMUXC_GPR1, 0xfff, 0x1b);
>
> Would it be possible to set the IOMUXC_GPR1 bits automagically, based on the
> dts description ?
It's possible, I think.
> Where should that go, in drivers/bus/imx-weim.c or in
> arch/arm/mach-imx/mach-imx6q.c ?
I prefer to drivers/bus/imx-weim.c.
> Also, I do not know how to retrieve
> the 'ranges' property of the weim description.
Just read it as an array of integers. I will post a patch for it
tomorrow. And please help test it.
Shawn
prev parent reply other threads:[~2014-02-10 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 0:15 imx6qdl, weim ranges and gpr1 Philippe De Muyter
2014-02-10 15:10 ` Shawn Guo [this message]
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=20140210151027.GP9628@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox