From: David Daney
libfdt is part of the device tree support in scripts/dtc/libfdt. For
some platforms that use the Device Tree, we want to be able to edit
the flattened device tree form.
We don't want to burden kernel builds that do not require it, so we
gate compilation of libfdt files with CO
On Fri, Mar 23, 2012 at 12:58 PM, Yinghai Lu wrote:
>
> There are some merge conflicts. Hope attached patch could help Linus a
> little bit.
Hmm. My merge does not agree with yours at all in the MIPS
pcibios_fixup_bus() area.
Your patch re-introduces the device resource fixup that Bjorn removed,
Hi Marek,
On Fri, Mar 23, 2012 at 10:43 PM, Marek Vasut wrote:
> Dear Dong Aisheng,
>
>> From: Dong Aisheng
>>
>> This patch includes basic dt support which can boot via nfs rootfs.
>>
>> Signed-off-by: Dong Aisheng
>> ---
>> ChangeLog v1->v2:
>> * Some fixes addressed Rob's review comments.
>
On 03/23/2012 01:49 AM, Viresh Kumar wrote:
> Few platforms define there own struct of_device_id[] for GIC. They don't
> do anything specific in init_irq() other than of_irq_init().
>
> This patch creates this struct array in gic.c and make other platforms use it.
>
> Signed-off-by: Viresh Kumar
During pinctrl_get(), if the client device has a device tree node, look
for the common pinctrl properties there. If found, parse the referenced
device tree nodes, with the help of the pinctrl drivers, and generate
mapping table entries from them.
During pinctrl_put(), free any results of device tr
Dear Dong Aisheng,
> From: Dong Aisheng
>
> This patch includes basic dt support which can boot via nfs rootfs.
>
> Signed-off-by: Dong Aisheng
> ---
> ChangeLog v1->v2:
> * Some fixes addressed Rob's review comments.
>Remove using of OF_DEV_AUXDATA.
> * Remove mac address from dts file
From: Dong Aisheng
This patch includes basic dt support which can boot via nfs rootfs.
Signed-off-by: Dong Aisheng
---
ChangeLog v1->v2:
* Some fixes addressed Rob's review comments.
Remove using of OF_DEV_AUXDATA.
* Remove mac address from dts file
Currently we use the mac address got
On 03/23/2012 03:07 AM, Viresh Kumar wrote:
> On 3/23/2012 1:30 PM, Stefan Roese wrote:
>> There could be differences between the IP cores integrated into the SoCs. I
>> only tested on spear600, so thats what I integrated into the drivers. While
>> supporting more SoCs (SPEAr300 etc) to those dri
On 03/23/2012 03:48 AM, Viresh Kumar wrote:
> SPEAr SMI controller version is same for all SPEAr machines. Thus we don't
> need
> per machine compatible property in driver.
Until the next chip...
> Thus this patch updates compatible entry to: "st,spear-smi", so that it
> works for all SPEAr mach
On 03/23/2012 02:49 AM, Viresh Kumar wrote:
> Few platforms define there own struct of_device_id[] for vic pl19*. They don't
> do anything specific in init_irq() other than of_irq_init().
>
> This patch creates this struct array in vic.c and make other platforms use it.
>
> Signed-off-by: Viresh
On 18.03.2012 19:24, Grant Likely wrote:
> On Fri, 16 Mar 2012 16:42:12 +0100, Karol Lewandowski
> wrote:
>> Make it possible to instantiate driver from device tree description.
>>
>> Signed-off-by: Karol Lewandowski
>> Signed-off-by: Kyungmin Park
>> Reviewed-by: Thomas Abraham
>> ---
>> dr
Hi Grant,
On 21 March 2012 20:43, Grant Likely wrote:
> Okay, so you're saying there are three important aspects to this
> device:
> 1) it terminates interrupts from other devices (therefore needs an
> interrupt controller driver)
> 2) it passes some interrupts through untouched (interrupt cont
SPEAr SMI controller version is same for all SPEAr machines. Thus we don't need
per machine compatible property in driver.
Thus this patch updates compatible entry to: "st,spear-smi", so that it
works for all SPEAr machines.
Signed-off-by: Viresh Kumar
---
.../devicetree/bindings/mtd/spear_smi.
FSMC NAND driver can verify device version by itself and so we wouldn't be
required to have separate .compatible entries for different SPEAr SoCs.
Thus this patch updates compatible entry to: "st,spear-fsmc-nand", so that it
works for all SPEAr machines.
Signed-off-by: Viresh Kumar
---
.../devi
On 3/23/2012 1:30 PM, Stefan Roese wrote:
> There could be differences between the IP cores integrated into the SoCs. I
> only tested on spear600, so thats what I integrated into the drivers. While
> supporting more SoCs (SPEAr300 etc) to those drivers, you should add the
> specific compatible p
Few platforms define there own struct of_device_id[] for GIC. They don't
do anything specific in init_irq() other than of_irq_init().
This patch creates this struct array in gic.c and make other platforms use it.
Signed-off-by: Viresh Kumar
---
arch/arm/common/gic.c | 10 +++
Few platforms define there own struct of_device_id[] for vic pl19*. They don't
do anything specific in init_irq() other than of_irq_init().
This patch creates this struct array in vic.c and make other platforms use it.
Signed-off-by: Viresh Kumar
---
arch/arm/common/vic.c | 14 +
Hi Viresh,
On Friday 23 March 2012 04:48:05 Viresh Kumar wrote:
> On 3/22/2012 9:20 PM, Stefan Roese wrote:
> > +static struct of_device_id spear_ohci_id_table[] __devinitdata = {
> > + { .compatible = "st,spear600-ohci", },
>
> Hi Stefan,
>
> I have this question for other drivers (fsmc, stmm
On Fri, Mar 23, 2012 at 02:27:22AM +0800, Stephen Warren wrote:
> Implement pinctrl_ops dt_node_to_map() and dt_free_map(). These allow
> complete specification of the desired pinmux configuration using device
> tree.
>
> Signed-off-by: Stephen Warren
> ---
> v3: Rebase on of_property_for_each_st
19 matches
Mail list logo
