linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] arm/mx5: add device tree support for imx53 boards
Date: Tue, 2 Aug 2011 08:58:14 +0200	[thread overview]
Message-ID: <20110802065814.GM31404@pengutronix.de> (raw)
In-Reply-To: <1312226252-8566-2-git-send-email-shawn.guo@linaro.org>

On Tue, Aug 02, 2011 at 03:17:31AM +0800, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@freescale.com>
> 
> It adds device tree support for imx53 boards.
> 
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  .../devicetree/bindings/arm/fsl/boards.txt         |   15 ++
>  arch/arm/boot/dts/imx53-ard.dts                    |  158 +++++++++++++
>  arch/arm/boot/dts/imx53-evk.dts                    |  144 ++++++++++++
>  arch/arm/boot/dts/imx53-qsb.dts                    |  148 ++++++++++++
>  arch/arm/boot/dts/imx53-smd.dts                    |  169 ++++++++++++++
>  arch/arm/boot/dts/imx53.dtsi                       |  244 ++++++++++++++++++++
>  arch/arm/mach-mx5/Kconfig                          |   12 +
>  arch/arm/mach-mx5/Makefile                         |    2 +
>  arch/arm/mach-mx5/board-mx53_ard.c                 |    9 +-
>  arch/arm/mach-mx5/board-mx53_evk.c                 |    5 +
>  arch/arm/mach-mx5/board-mx53_loco.c                |    5 +
>  arch/arm/mach-mx5/board-mx53_smd.c                 |    5 +
>  arch/arm/mach-mx5/imx53-dt.c                       |  143 ++++++++++++
>  arch/arm/plat-mxc/include/mach/common.h            |    2 +
>  arch/arm/plat-mxc/include/mach/iomux-mx53.h        |    5 +
>  arch/arm/plat-mxc/include/mach/iomux-v3.h          |    5 +
>  16 files changed, 1069 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/fsl/boards.txt
>  create mode 100644 arch/arm/boot/dts/imx53-ard.dts
>  create mode 100644 arch/arm/boot/dts/imx53-evk.dts
>  create mode 100644 arch/arm/boot/dts/imx53-qsb.dts
>  create mode 100644 arch/arm/boot/dts/imx53-smd.dts
>  create mode 100644 arch/arm/boot/dts/imx53.dtsi
>  create mode 100644 arch/arm/mach-mx5/imx53-dt.c

I noticed that the iomux setup is gone for now which makes me very
happy :) I didn't have a good feeling about this.

> 
> diff --git a/arch/arm/boot/dts/imx53-ard.dts b/arch/arm/boot/dts/imx53-ard.dts
> new file mode 100644
> index 0000000..fd0cf2c
> --- /dev/null
> +++ b/arch/arm/boot/dts/imx53-ard.dts
> @@ -0,0 +1,158 @@
> +/*
> + * Copyright 2011 Freescale Semiconductor, Inc.
> + * Copyright 2011 Linaro Ltd.
> + *
> + * 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/ "imx53.dtsi"
> +
> +/ {
> +	model = "Freescale i.MX53 Automotive Reference Design Board";
> +	compatible = "fsl,imx53-ard", "fsl,imx53";
> +
> +	chosen {
> +		bootargs = "console=ttymxc0,115200 root=/dev/mmcblk0p3 rootwait";
> +	};
> +
> +	memory {
> +		reg = <0x70000000 0x40000000>;
> +	};
> +
> +	aips at 50000000 { /* AIPS1 */
> +		spba at 50000000 {
> +			esdhc at 50004000 { /* ESDHC1 */
> +				cd-gpios = <&gpio0 1 0>; /* GPIO1_1 */
> +				wp-gpios = <&gpio0 9 0>; /* GPIO1_9 */
> +			};
> +
> +			esdhc at 50008000 { /* ESDHC2 */
> +				status = "disabled";
> +			};

I know the decision is that all devices are enabled by default and must
be explicitely disabled like this. I really hope we can change this in
the future for the following reasons:

- The imx53 device tree is not complete, several devices like nand, ipu
  and rtc are missing. Now when imx53.dtsi gets the nand device, all
  board devicetrees have to be changed to keep the old behaviour.
- Most enabled device entries like the esdhc1 above have additional
  nodes like cd-gpios anyway, so they must appear in the board tree
  whereas the disabled devices just add additional churn.

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2011-08-02  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 19:17 [PATCH v3 0/3] Add device tree support for i.mx51/53 boards Shawn Guo
2011-08-01 19:17 ` [PATCH v3 1/2] arm/mx5: add device tree support for imx53 boards Shawn Guo
2011-08-01 22:01   ` Grant Likely
2011-08-02  6:09     ` Shawn Guo
2011-08-02 13:40       ` Grant Likely
2011-08-02  6:58   ` Sascha Hauer [this message]
2011-08-02  1:22     ` Shawn Guo
2011-08-02  7:53     ` Shawn Guo
2011-08-02 11:43     ` Grant Likely
2011-08-01 19:17 ` [PATCH v3 2/2] arm/mx5: add device tree support for imx51 babbage 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=20110802065814.GM31404@pengutronix.de \
    --to=s.hauer@pengutronix.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).