From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: mxs: Add SchulerControl SPS1 DTS file
Date: Sat, 25 Aug 2012 14:35:52 +0200 [thread overview]
Message-ID: <201208251435.52411.marex@denx.de> (raw)
In-Reply-To: <20120825083042.GM31998@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> Please base it on my mxs/dt-for-3.7 branch.
>
> On Sat, Aug 25, 2012 at 01:51:40AM +0200, Marek Vasut wrote:
> > Add DTS file for this custom board.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > ---
> >
> > arch/arm/boot/dts/imx28-sps1.dts | 168
> > ++++++++++++++++++++++++++++++++++++++ arch/arm/mach-mxs/mach-mxs.c
> > | 3 +
> > 2 files changed, 171 insertions(+)
> > create mode 100644 arch/arm/boot/dts/imx28-sps1.dts
> >
> > diff --git a/arch/arm/boot/dts/imx28-sps1.dts
> > b/arch/arm/boot/dts/imx28-sps1.dts new file mode 100644
> > index 0000000..d05b1cb
> > --- /dev/null
> > +++ b/arch/arm/boot/dts/imx28-sps1.dts
> > @@ -0,0 +1,168 @@
> > +/*
> > + * Copyright (C) 2012 Marek Vasut <marex@denx.de>
> > + *
> > + * The code contained herein is licensed under the GNU General Public
> > + * License. You may obtain a copy of the GNU General Public License
> > + * Version 2 or later at the following locations:
> > + *
> > + * http://www.opensource.org/licenses/gpl-license.html
> > + * http://www.gnu.org/copyleft/gpl.html
> > + */
> > +
> > +/dts-v1/;
> > +/include/ "imx28.dtsi"
> > +
> > +/ {
> > + model = "SchulerControl GmbH, SC SPS 1";
> > + compatible = "schulercontrol,imx28-sps1", "fsl,imx28";
>
> We should use the short name as prefix if it has one.
>
> > +
> > + memory {
> > + reg = <0x40000000 0x08000000>;
> > + };
> > +
> > + apb at 80000000 {
> > + apbh at 80000000 {
> > + pinctrl at 80018000 {
> > + led_pins_sps1: leds at 0 {
>
> It should be referenced by the pinctrl state directly under node
> pinctrl at 80018000, otherwise the pins will not be set up.
>
> Also we usually use a generic name here something like
>
> hog_pins_a: hog at 0 {
>
> so that we do not need to create new node every time we add pins
> for a new module.
So I'll ignore this comment and add pinctrl call into leds-gpio ... can we agree
on that ?
[...]
next prev parent reply other threads:[~2012-08-25 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:51 [PATCH 1/4 V2] ARM: mx28: Add SPI 2 pinmux into imx28.dtsi Marek Vasut
2012-08-24 23:51 ` [PATCH 2/4 V2] ARM: mx28: Add USB PHY overcurrent pinmux Marek Vasut
2012-08-25 7:57 ` Shawn Guo
2013-11-22 15:49 ` Michael Grzeschik
2013-11-23 14:48 ` Peter Chen
2013-11-24 16:05 ` Michael Grzeschik
2013-11-24 23:58 ` Marek Vasut
2013-11-25 13:42 ` Michael Grzeschik
2013-11-26 12:08 ` Peter Chen
2013-12-06 15:17 ` Michael Grzeschik
2013-12-09 5:12 ` Peter Chen
2012-08-24 23:51 ` [PATCH 3/4 V2] ARM: mxs: Update DENX M28 machine and dts file Marek Vasut
2012-08-25 8:05 ` Shawn Guo
2012-08-26 11:42 ` Marek Vasut
2012-08-24 23:51 ` [PATCH 4/4] ARM: mxs: Add SchulerControl SPS1 DTS file Marek Vasut
2012-08-25 8:30 ` Shawn Guo
2012-08-25 12:35 ` Marek Vasut [this message]
2012-08-25 13:03 ` Shawn Guo
2012-08-28 0:28 ` Shawn Guo
2012-08-28 0:44 ` Marek Vasut
2012-08-25 7:56 ` [PATCH 1/4 V2] ARM: mx28: Add SPI 2 pinmux into imx28.dtsi Shawn Guo
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=201208251435.52411.marex@denx.de \
--to=marek.vasut@gmail.com \
--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).