From: Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Karl Beldan
<karl.beldan+oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] ARM: dts: da850: Adjust the pinctrl muxing for the NAND on CS3
Date: Thu, 4 Aug 2016 20:53:05 +0000 [thread overview]
Message-ID: <20160804205305.GA15013@gobelin> (raw)
In-Reply-To: <CAJaRCXMBi-UQaXkGNaSaKjb6eqoJwhcc9Py8vFEWpVKSn5g5bQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Aug 04, 2016 at 08:42:19PM +0000, Karl Beldan wrote:
> 2016-08-03 17:06 GMT+00:00 Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>:
>
> > - Adjust the settings to also allow driving EMA_D[8..15] for 16bits
> > NANDs. These are shared with GPIO3[0..7] which have no in-tree user.
> > - Remove the useless CS4 setting
> >
> > Cc: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> > Signed-off-by: Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> > ---
> > arch/arm/boot/dts/da850.dtsi | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
> > index 3a00978..ae5dc18 100644
> > --- a/arch/arm/boot/dts/da850.dtsi
> > +++ b/arch/arm/boot/dts/da850.dtsi
> > @@ -43,16 +43,20 @@
> >
> > nand_cs3_pins: pinmux_nand_pins {
> > pinctrl-single,bits = <
> > - /* EMA_OE, EMA_WE */
> > - 0x1c 0x00110000 0x00ff0000
> > - /* EMA_CS[4],EMA_CS[3]*/
> > - 0x1c 0x00000110 0x00000ff0
> > + /* EMA_OE, EMA_WE, EMA_CS[3] */
> > + 0x1c 0x00110010 0x00ff00f0
> > /*
> > * EMA_D[0], EMA_D[1], EMA_D[2],
> > * EMA_D[3], EMA_D[4], EMA_D[5],
> > * EMA_D[6], EMA_D[7]
> > */
> > 0x24 0x11111111 0xffffffff
> > + /*
> > + * EMA_D[8], EMA_D[9], EMA_D[10],
> > + * EMA_D[11], EMA_D[12], EMA_D[13],
> > + * EMA_D[14], EMA_D[15]
> > + */
> > + 0x20 0x11111111 0xffffffff
> > /* EMA_A[1], EMA_A[2] */
> > 0x30 0x01100000 0x0ff00000
> > >;
> > --
> > 2.9.0.rc1
> >
Please discard this one I think it is better that I make groups for the
NAND.
Karl
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-08-04 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 17:06 [PATCH] ARM: dts: da850: Adjust the pinctrl muxing for the NAND on CS3 Karl Beldan
2016-08-04 8:39 ` Karl Beldan
2016-08-04 20:42 ` Karl Beldan
[not found] ` <CAJaRCXMBi-UQaXkGNaSaKjb6eqoJwhcc9Py8vFEWpVKSn5g5bQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-04 20:53 ` Karl Beldan [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=20160804205305.GA15013@gobelin \
--to=kbeldan-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=karl.beldan+oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).