From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Fri, 21 Jun 2013 14:07:26 -0500
Subject: [U-Boot] Modifying the Device tree fields
In-Reply-To: <CAG8PAaon8OjseJAkTJFZvTYtwV4H_KHHUy0=o+qUtuzTNE68Zw@mail.gmail.com>
	(from pkamaraj@gmail.com on Fri Jun 21 12:26:33 2013)
References: <CAG8PAaon8OjseJAkTJFZvTYtwV4H_KHHUy0=o+qUtuzTNE68Zw@mail.gmail.com>
Message-ID: <1371841646.11064.27@snotra>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 06/21/2013 12:26:33 PM, Kamaraj P wrote:
> Hello All,
> 
> In my device tree blob, i would like to add some interrupt to the
> protected-source list dynamically in the u-boot before launching the  
> linux
> kernel.
> 
>  mpic: pic at 40000 {
>             interrupt-controller;
>             #address-cells = <0>;
>             #interrupt-cells = <2>;
>             reg = <0x40000 0x40000>;
>             compatible = "chrp,open-pic";
>             device_type = "open-pic";
>             protected-sources = <
>             16
>              >
> 
> In the above DTS file,  i would like to add the other interrupts to  
> the
>  protected-sources dynamically.

If you use the pic-no-reset property, you don't need protected-sources  
at all, unless you specifically want the error checking aspect of it.

> I hope we need to use the device fdt APIs.  Could you please any  
> pointers
> or  reference for how to use those APIs in the u-boot ?

fdt_appendprop looks like a good choice if you still want to do this.

-Scott