public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch v8 4/5] armv8/fsl-lsch3: Add support to load and start MC Firmware
Date: Fri, 20 Jun 2014 22:33:46 +0200	[thread overview]
Message-ID: <53A49AAA.9050507@myspectrum.nl> (raw)
In-Reply-To: <1403290017-22838-4-git-send-email-yorksun@freescale.com>

Hi York,

On 20-06-14 20:46, York Sun wrote:
> From: "J. German Rivera" <German.Rivera@freescale.com>
>
> Adding support to load and start the Layerscape Management Complex (MC)
> firmware. First, the MC GCR register is set to 0 to reset all cores. MC
> firmware and DPL images are copied from their location in NOR flash to
> DDR. MC registers are updated with the location of these images.
> Deasserting the reset bit of MC GCR register releases core 0 to run.
> Core 1 will be released by MC firmware. Stop bits are not touched for
> this step. U-boot waits for MC until it boots up. In case of a failure,
> device tree is updated accordingly. The MC firmware image uses FIT format.
>
>
> +int parse_mc_firmware_fit_image(const void **raw_image_addr,
> +				size_t *raw_image_size)
> +{
> +	int format;
> +	void *fit_hdr;
> +	int node_offset;
> +	const void *data;
> +	size_t size;
> +	const char *uname = "firmware";
> +
> +	/* Check if the image is in NOR flash*/
> +#ifdef CONFIG_SYS_LS_MC_FW_IN_NOR
> +	fit_hdr = (void *)CONFIG_SYS_LS_MC_FW_ADDR;
> +#else
> +#error "No CONFIG_SYS_LS_MC_FW_IN_xxx defined"
> +#endif
> +
> +	/* Check if Image is in FIT format */
> +	format = genimg_get_format(fit_hdr);
> +
> +	if (format != IMAGE_FORMAT_FIT) {
> +		debug("Not a FIT image\n");
> +		return 1;
> +	}
> +
> +	if (!fit_check_format(fit_hdr)) {
> +		debug("Bad FIT image format\n");
> +		return 1;
> +	}
> +
> +	/* Find node offset of MC Firmware image */
> +	if (uname == NULL) {
> +		debug("FIT subimage unit name not provided");
> +		return 1;
> +	}
> +

I don't see how uname can ever be NULL here, since it is
assigned above.

Regards,
Jeroen

  reply	other threads:[~2014-06-20 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 18:46 [U-Boot] [Patch v8 1/5] Added 64-bit MMIO accessors for ARMv8 York Sun
2014-06-20 18:46 ` [U-Boot] [Patch v8 2/5] ARMv8: Adjust MMU setup York Sun
2014-06-20 18:46 ` [U-Boot] [Patch v8 3/5] ARMv8/FSL_LSCH3: Add FSL_LSCH3 SoC York Sun
2014-06-20 18:46 ` [U-Boot] [Patch v8 4/5] armv8/fsl-lsch3: Add support to load and start MC Firmware York Sun
2014-06-20 20:33   ` Jeroen Hofstee [this message]
2014-06-20 20:38     ` York Sun
2014-06-23 20:50       ` Jose Rivera
2014-06-23 21:18         ` York Sun
2014-06-20 18:46 ` [U-Boot] [Patch v8 5/5] ARMv8/ls2085a_emu: Add LS2085A emulator and simulator board support York Sun

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=53A49AAA.9050507@myspectrum.nl \
    --to=dasuboot@myspectrum.nl \
    --cc=u-boot@lists.denx.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