* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [130405 09:52]: > On Thursday 04 April 2013 10:27 PM, Santosh Shilimkar wrote: > > On Thursday 04 April 2013 10:22 PM, Tony Lindgren wrote: > >> * Santosh Shilimkar <santosh.shilimkar@xxxxxx> [130404 04:15]: > [..] > > >> Can't we already trim the am33xx hwmod data after your patches for > >> v3.10 as am33xx is already DT only? Unfortunately we cannot create > >> negative diffstat in other ways for v3.10 merge window as we cannot > >> make omap4 DT only just quite yet. > >> > > Yes we can and I can take a stab it tomorrow. The only thing is I > > might need some support for testing but thats manageable. Will > > take a stab at it tomorrow and if everything goes well, post a > > patch for smae. > > > Patch for the AM33XX to trim is end of the email. Thanks to > Sricharan and Pekon for patch and testing. Looping both > Vaibhav's if they have any objection on the patch. > > Regards, > Santosh > > From b95dd33fe59b8e77727eb3b1717d763bbf9a2893 Mon Sep 17 00:00:00 2001 > From: Sricharan R <r.sricharan@xxxxxx> > Date: Fri, 5 Apr 2013 20:39:12 +0530 > Subject: [PATCH] ARM: AM33XX: hwmod data: Clean up the data file > > - The IO resource information like dma request lines, irq number and > ocp address space can be populated via dt blob. So such data can be stripped > from SOC hwmod data file. > > - The devices like adc, mailbox, gpmc which are missing the device > tree bindings, hwmod data is not added since AM33XX is DT only build. > When such devices add the dt bindings, respective hwmod data can be > added along with it. > > - The hwmod like firewall etc which are not useful are also dropped. > > This gets us around ~2000 loc of negative diff. Patch is boot tested on > AM335X EVM. Great, that's a nice reduction :) Considering am33xx is DT only, it should be safe.. But can the am33xx guys please test and ack it? Regards, Tony -- 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