linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx28: Add LCD pinmux
Date: Tue, 26 Jun 2012 14:17:58 +0200	[thread overview]
Message-ID: <201206261417.58300.marex@denx.de> (raw)
In-Reply-To: <20120626025216.GK2342@S2101-09.ap.freescale.net>

Dear Shawn Guo,

> On Sat, Jun 23, 2012 at 08:45:18PM +0200, Marek Vasut wrote:
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Detlev Zundel <dzu@denx.de>
> > CC: Dong Aisheng <b29396@freescale.com>
> > CC: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Linux ARM kernel <linux-arm-kernel@lists.infradead.org>
> > CC: Shawn Guo <shawn.guo@linaro.org>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Wolfgang Denk <wd@denx.de>
> > ---
> > 
> >  arch/arm/boot/dts/imx28.dtsi |   45
> >  ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45
> >  insertions(+)
> > 
> > diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> > index 464303c..ab29cbe 100644
> > --- a/arch/arm/boot/dts/imx28.dtsi
> > +++ b/arch/arm/boot/dts/imx28.dtsi
> > @@ -221,6 +221,51 @@
> > 
> >  					fsl,pull-up = <0>;
> >  				
> >  				};
> > 
> > +				lcd_data_pins_8bpp_a: lcd at 0 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <0x1000 0x1010 0x1020 
0x1030
> > +						0x1040 0x1050 0x1060 0x1070>;
> > +					fsl,drive-strength = <0>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> > +				lcd_data_pins_16bpp_a: lcd at 1 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <0x1000 0x1010 0x1020 
0x1030
> > +						0x1040 0x1050 0x1060 0x1070
> > +						0x1080 0x1090 0x10a0 0x10b0
> > +						0x10c0 0x10d0 0x10e0 0x10f0>;
> > +					fsl,drive-strength = <0>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> > +				lcd_data_pins_18bpp_a: lcd at 2 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <0x1000 0x1010 0x1020 
0x1030
> > +						0x1040 0x1050 0x1060 0x1070
> > +						0x1080 0x1090 0x10a0 0x10b0
> > +						0x10c0 0x10d0 0x10e0 0x10f0
> > +						0x1100 0x1110>;
> > +					fsl,drive-strength = <0>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> > +				lcd_data_pins_24bpp_a: lcd at 3 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <0x1000 0x1010 0x1020 
0x1030
> > +						0x1040 0x1050 0x1060 0x1070
> > +						0x1080 0x1090 0x10a0 0x10b0
> > +						0x10c0 0x10d0 0x10e0 0x10f0
> > +						0x1100 0x1110 0x1120 0x1130
> > +						0x1140 0x1150 0x1160 0x1170>;
> > +					fsl,drive-strength = <0>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> 
> We do not want to enumerate all the possible mux options.  Instead,
> please add mux setting when there is indeed a user for it.

Well, I'd prefer to have it ready to be used, instead of having partial slabs of 
muxes. But whatever.

Is anyone converting the LCD driver over to DT or not?

Best regards,
Marek Vasut

      reply	other threads:[~2012-06-26 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 18:45 [PATCH] ARM: mx28: Add LCD pinmux Marek Vasut
2012-06-24  6:28 ` Fabio Estevam
2012-06-24 13:05   ` Marek Vasut
2012-06-24 13:15     ` Fabio Estevam
2012-06-24 13:43       ` Marek Vasut
2012-06-26  2:52 ` Shawn Guo
2012-06-26 12:17   ` Marek Vasut [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=201206261417.58300.marex@denx.de \
    --to=marex@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).