mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: i.MX53: dts: add support for MCIMX53-START-R
Date: Fri, 10 Jan 2014 10:36:56 +0100	[thread overview]
Message-ID: <20140110093656.GC6750@pengutronix.de> (raw)
In-Reply-To: <1389278408-13112-2-git-send-email-s.trumtrar@pengutronix.de>

On Thu, Jan 09, 2014 at 03:40:08PM +0100, Steffen Trumtrar wrote:
> The start-r QSB has a different pmic than the older start QSB.
> Add a new dts for the QSRB and let barebox generate two images when
> LOCO is selected.
> 
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> ---
>  arch/arm/boards/freescale-mx53-loco/lowlevel.c |  13 +++
>  arch/arm/dts/Makefile                          |   3 +-
>  arch/arm/dts/imx53-qsrb.dts                    | 141 +++++++++++++++++++++++++
>  images/Makefile.imx                            |   5 +
>  4 files changed, 161 insertions(+), 1 deletion(-)
>  create mode 100644 arch/arm/dts/imx53-qsrb.dts
> 
> diff --git a/arch/arm/boards/freescale-mx53-loco/lowlevel.c b/arch/arm/boards/freescale-mx53-loco/lowlevel.c
> index 7556a2e..c9e057a 100644
> --- a/arch/arm/boards/freescale-mx53-loco/lowlevel.c
> +++ b/arch/arm/boards/freescale-mx53-loco/lowlevel.c
> @@ -15,3 +15,16 @@ ENTRY_FUNCTION(start_imx53_loco, r0, r1, r2)
>  
>  	imx53_barebox_entry(fdt);
>  }
> +
> +extern char __dtb_imx53_qsrb_start[];
> +
> +ENTRY_FUNCTION(start_imx53_loco_r, r0, r1, r2)
> +{
> +	uint32_t fdt;
> +
> +	arm_cpu_lowlevel_init();
> +
> +	fdt = (uint32_t)__dtb_imx53_qsrb_start - get_runtime_offset();
> +
> +	imx53_barebox_entry(fdt);
> +}

For the record: This introduces a new image for the r board. Should we
want to later we could use the code from arch/ppc/mach-mpc85xx/fsl_i2c.c
to detect the board version and merge both images into one again.

> +	pmic: ripley@8 {
> +		compatible = "fsl,mc34708";
> +		reg = <0x08>;
> +		interrupt-parent = <&gpio5>;
> +		interrupts = <23 0x8>;
> +		regulators {
> +			mc34708__sw1a {
> +				regulator-name = "SW1";
> +				regulator-min-microvolt = <650000>;
> +				regulator-max-microvolt = <1437500>;
> +				regulator-boot-on;
> +				regulator-always-on;
> +			};
> +			mc34708__sw1b {

There should be a blank line between the end of a node and the beginning
of a new one.

Sascha

-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-01-10  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 14:40 [PATCH 1/2] ARM: i.MX53: dts: move QSB pmic to own file Steffen Trumtrar
2014-01-09 14:40 ` [PATCH 2/2] ARM: i.MX53: dts: add support for MCIMX53-START-R Steffen Trumtrar
2014-01-10  9:36   ` Sascha Hauer [this message]
2014-01-10 10:00     ` Steffen Trumtrar

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=20140110093656.GC6750@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.trumtrar@pengutronix.de \
    /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