linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Tue, 9 Apr 2013 14:38:55 -0600	[thread overview]
Message-ID: <20130409203855.GA27797@obsidianresearch.com> (raw)
In-Reply-To: <1365539181-29242-2-git-send-email-ezequiel.garcia@free-electrons.com>

On Tue, Apr 09, 2013 at 05:26:17PM -0300, Ezequiel Garcia wrote:
> +	/*
> +	 * Since this is only part of the workaround,
> +	 * we can do this dirty 'ranges' property parsing.
> +	 * Of course, this will be removed once the address windows
> +	 * are declared in the device tree.
> +	 */
> +	err = of_property_read_u32_array(node, "ranges", addr_region,
> +					 ARRAY_SIZE(addr_region));
> +	if (err < 0) {
> +		dev_err(dev, "%s has a malformed 'range' property\n",
> +			node->full_name);
> +		return err;
> +	}

> +	/*
> +	 * Create an mbus address windows.
> +	 * FIXME: Remove this, together with the above code, once the
> +	 * address windows are declared in the device tree.
> +	 */
> +	err = mvebu_mbus_add_window(devbus_wins[cs],
> +				    addr_region[1], addr_region[2]);

Oh, this is a dangerous way to parse ranges.. 

Try something like:

const __be32 *prop;
u64 base;
u64 size;

prop = of_get_property("ranges",&psize);
if (prop == NULL || psize != of_n_addr_cells(node) + of_n_size_cells(node))
   err;
base = of_translate_address(node,prop);
if (base == OF_BAD_ADDR)
   err;
size = of_read_number(prop + of_n_addr_cells(node),of_n_size_cells(node));

err = mvebu_mbus_add_window(devbus_wins[cs],base,size);

I omitted some error checking.

Jason

  reply	other threads:[~2013-04-09 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 20:26 [PATCH v6 0/5] Device Bus support for Marvell EBU SoC Ezequiel Garcia
2013-04-09 20:26 ` [PATCH v6 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-09 20:38   ` Jason Gunthorpe [this message]
2013-04-09 20:49     ` Ezequiel Garcia
2013-04-10 10:19     ` Ezequiel Garcia
2013-04-10 16:57       ` Jason Gunthorpe
2013-04-10 17:37         ` Ezequiel Garcia
2013-04-09 20:26 ` [PATCH v6 2/5] ARM: mvebu: Add Device Bus support for Armada 370/XP SoC Ezequiel Garcia
2013-04-09 20:26 ` [PATCH v6 3/5] ARM: mvebu: Add support for NOR flash device on Armada XP-GP board Ezequiel Garcia
2013-04-09 20:26 ` [PATCH v6 4/5] ARM: mvebu: Add support for NOR flash device on Openblocks AX3 board Ezequiel Garcia
2013-04-09 20:26 ` [PATCH v6 5/5] ARM: mvebu: Add Device Bus and CFI flash memory support to defconfig Ezequiel Garcia

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=20130409203855.GA27797@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.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).