From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
Cc: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Artem Bityutskiy
<dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCHv3] mtd: gpio-nand: add device tree bindings
Date: Mon, 1 Aug 2011 15:39:50 -0500 [thread overview]
Message-ID: <20110801153950.634eb432@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <20110801202536.GB2648-apL1N+EY0C9YtYNIL7UdTEEOCMrvLtNR@public.gmane.org>
On Mon, 1 Aug 2011 21:25:36 +0100
Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org> wrote:
> On Mon, Aug 01, 2011 at 03:12:09PM -0500, Scott Wood wrote:
> > It looks like the code uses a little-endian accessor (readw) in a couple
> > places. The instance in gpio_nand_readbuf16() should never be reached
> > since the NAND layer should never do an unaligned buffer read, but the one
> > in gpio_nand_verifybuf16() could cause problems.
[snip]
>
> OK, so for this should I just document that all accesses are
> little-endian? We can then add properties later if we need something
> different.
Right now, the driver is using a mix of native and little endian accesses.
That's not something the binding can fix. :-)
Native endian is what it should be.
> > Or perhaps the io sync address should just be a physical address, not a reg
> > that gets translated.
>
> OK, I like the sound of that. I'm a bit new to the world of device tree
> so I'm not sure of the best way to do this. Would reading the
> #address-cells property then use of_read_number() be the right way?
I'd just unconditionally define it as a 64-bit physical address.
-Scott
next prev parent reply other threads:[~2011-08-01 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 14:02 [PATCHv3] mtd: gpio-nand: add device tree bindings Jamie Iles
[not found] ` <1312207374-14760-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-08-01 18:38 ` Scott Wood
[not found] ` <20110801133825.0b4fff24-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2011-08-01 19:33 ` Jamie Iles
2011-08-01 20:12 ` Scott Wood
[not found] ` <20110801151209.7b904320-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2011-08-01 20:25 ` Jamie Iles
[not found] ` <20110801202536.GB2648-apL1N+EY0C9YtYNIL7UdTEEOCMrvLtNR@public.gmane.org>
2011-08-01 20:39 ` Scott Wood [this message]
2011-08-01 20:43 ` Scott Wood
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=20110801153950.634eb432@schlenkerla.am.freescale.net \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).