[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160307185805.GV55664@google.com>
Date: Mon, 7 Mar 2016 10:58:05 -0800
From: Brian Norris <computersforpeace@...il.com>
To: Roger Quadros <rogerq@...com>
Cc: tony@...mide.com, dwmw2@...radead.org,
ezequiel@...guardiasur.com.ar, javier@...hile0.org, fcooper@...com,
nsekhar@...com, linux-mtd@...ts.infradead.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Boris Brezillon <boris.brezillon@...e-electrons.com>
Subject: Re: [PATCH v5 10/26] mtd: nand: omap: Update DT binding documentation
On Mon, Mar 07, 2016 at 11:46:24AM +0200, Roger Quadros wrote:
> On 05/03/16 04:04, Brian Norris wrote:
> > Is it normal to mix types of addressing in a single 'reg' property? Is
> > your code working for anything besides CS==0?
>
> Yes we're using non zero CS on different omap platforms.
> I haven't changed the behaviour of the reg property in this series. Just updated the documentation.
>
> I didn't understand what you meant by mixing type of addressing.
>
> This usage is exactly as mentioned here
> http://devicetree.org/Device_Tree_Usage#Ranges_.28Address_Translation.29
I think I was just misunderstanding the use of the reg, *-cells, and
ranges properties here. Thanks for the pointer.
Brian
Powered by blists - more mailing lists