On Tue, Nov 20, 2012 at 15:56:32, Marc Kleine-Budde wrote: > On 11/20/2012 11:23 AM, AnilKumar, Chimata wrote: > > On Tue, Nov 20, 2012 at 15:43:04, Marc Kleine-Budde wrote: > >> On 11/14/2012 07:08 PM, AnilKumar Ch wrote: > >>> Add a new address space/memory resource to d_can device tree node. D_CAN > >>> RAM initialization is achieved through RAMINIT register which is part of > >>> AM33XX control module address space. D_CAN RAM init or de-init should be > >>> done by writing instance corresponding value to control module register. > >>> > >>> Till we have a separate control module driver to write to control module, > >>> d_can driver will handle the register writes to control module by itself. > >>> So a new address space to represent this control module register is added > >>> to d_can driver. > >>> > >>> Signed-off-by: AnilKumar Ch <anilkumar@xxxxxx> > >> > >> This does not apply to net-next/master: > >> > >> Applying: ARM: dts: AM33XX: Add memory resource to d_can node > >> error: patch failed: arch/arm/boot/dts/am33xx.dtsi:227 > >> error: arch/arm/boot/dts/am33xx.dtsi: patch does not apply > >> Patch failed at 0003 ARM: dts: AM33XX: Add memory resource to d_can node > >> > > > > Marc, > > > > Sorry about this DT changes are present in linux-omap. > > > > Could you please take the driver changes only and ACK on remaining will > > help. > > Will do - I'm currently looking at the driver. > Hi Marc, Please ACK this patch as well. Thanks AnilKumar -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
