From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Bug in devicetree_for_each_node() in xen/arch/arm/bootfdt.c ? Date: Tue, 23 Jun 2015 11:32:13 +0100 Message-ID: <558935AD.3030606@citrix.com> References: <4EE5B48738DDED408878C97C8E050A8B1D7ABBB3@SJEXCHMB05.corp.ad.broadcom.com> <5589300B.1020108@citrix.com> <1435055228.28264.198.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z7LVR-0000TL-1Y for xen-devel@lists.xenproject.org; Tue, 23 Jun 2015 10:32:41 +0000 In-Reply-To: <1435055228.28264.198.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xenproject.org" , David Vrabel , "Chris (Christopher) Brand" List-Id: xen-devel@lists.xenproject.org On 23/06/2015 11:27, Ian Campbell wrote: > On Tue, 2015-06-23 at 11:08 +0100, Julien Grall wrote: > >>> reg = <0x0 0x0 0x0 0x40000000 0x0 0x40000000 0x0 0x40000000>; >> >> Although, what the rest of the node used for? Do we expect to parse it? >> I wasn't able to find a suitable bindings in the docs... > > A reg can encode multiple regions, by just listing them one after the > other. It'll be in the generic docs about reg properties I expect, > there's nothing special about a reg property in a memory node in this > regard. > > Xen parses these just fine, via the loop and use of device_tree_get_reg > in process_memory_node I know that a "reg" can encode multiple regions... My question was related to the "rest of the node" and not the rest of the property... i.e region@10000000 { contiguous-region; reg = <0x10000000 0x1f800000>; linux,phandle = <0x2>; phandle = <0x2>; }; AFAICT we don't parse it. Regards, -- Julien Grall