From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Wed, 10 Apr 2013 07:19:57 -0300 [thread overview]
Message-ID: <20130410101956.GA2250@localhost> (raw)
In-Reply-To: <20130409203855.GA27797@obsidianresearch.com>
Hi Jason,
On Tue, Apr 09, 2013 at 02:38:55PM -0600, Jason Gunthorpe wrote:
> 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));
>
> 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));
>
Thanks for giving me these hints!
Following your suggestion, here's a working piece of the ranges parsing code,
how does this look?
const __be32 *ranges;
int addr_cells, p_addr_cells, size_cells;
int ranges_len, tuple_len;
u32 base, size;
p_addr_cells = of_n_addr_cells(node->parent);
addr_cells = of_n_addr_cells(node);
size_cells = of_n_size_cells(node);
tuple_len = (p_addr_cells + addr_cells + size_cells) * sizeof(__be32);
ranges = of_get_property(node, "ranges", &ranges_len);
if (ranges == NULL || ranges_len != tuple_len)
return -EINVAL;
base = of_translate_address(node, ranges + addr_cells);
if (base == 0 || base == OF_BAD_ADDR)
return -EINVAL;
size = of_read_number(ranges + addr_cells + p_addr_cells, size_cells);
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-04-10 10:19 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
2013-04-09 20:49 ` Ezequiel Garcia
2013-04-10 10:19 ` Ezequiel Garcia [this message]
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=20130410101956.GA2250@localhost \
--to=ezequiel.garcia@free-electrons.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