From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: OMAP baseline test results for v3.10-rc6 Date: Wed, 26 Jun 2013 16:57:38 -0700 Message-ID: <87ehboqvbh.fsf@linaro.org> References: <20130625160243.GE22312@arwen.pp.htv.fi> <51C9F0A8.1050607@ti.com> <87fvw6t136.fsf@linaro.org> <79CD15C6BA57404B839C016229A409A83ECC952D@DBDE04.ent.ti.com> <51CAEB33.5010101@ti.com> <51CAEBF3.1010507@ti.com> <51CB28BD.2020105@ti.com> <51CB48BA.7020401@ti.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mail-pb0-f42.google.com ([209.85.160.42]:39372 "EHLO mail-pb0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843Ab3FZX5m (ORCPT ); Wed, 26 Jun 2013 19:57:42 -0400 Received: by mail-pb0-f42.google.com with SMTP id un1so106806pbc.15 for ; Wed, 26 Jun 2013 16:57:41 -0700 (PDT) In-Reply-To: <51CB48BA.7020401@ti.com> (Tom Rini's message of "Wed, 26 Jun 2013 16:02:02 -0400") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tom Rini Cc: Paul Walmsley , Rajendra Nayak , "Hiremath, Vaibhav" , "linux-omap@vger.kernel.org" , "Balbi, Felipe" , "linux-arm-kernel@lists.infradead.org" Tom Rini writes: > On 06/26/2013 01:58 PM, Paul Walmsley wrote: >> On Wed, 26 Jun 2013, Tom Rini wrote: >> >>> OK, is there a reason to not be using omap2plus_defconfig? My pass/fail >>> here is based on that config and enabling, or not, dtb append. Seems >>> like it would be one less thing to maintain on your end and it would be >>> on TIs end (roughly speaking) to make sure our platforms that ought to >>> be working upstream have what they need enabled in the defconfig(s) in >>> question. >> >> That would be convenient for me, but part of the goal is to verify that a >> Kconfig that deselects all OMAPs other than AM33xx continues to work. >> >> So the build process for am33xx_only here goes something like: >> >> 1. Start with omap2plus_defconfig >> >> 2. Turn off support for everything other than AM33xx in the SoC target >> selection menus >> >> 3. Turn on the appended DTB and compat ATAGs options >> >> You might consider adding something like this to your pass/fail tests. > > Adding more and different build+boot tests is on the list. I guess you > could automate this with a fraagment of everything am33xx must have to > boot+root and alldefconfig for the rest? Since I recently discovered scripts/kconfig/merge_config.sh, I thought I'd share a very convenient way of automating the variations on a kconfig theme, just in case I'm not the last one to discover this useful tool. For example, I have the following in am335x_only.config: CONFIG_ARCH_OMAP2=n CONFIG_ARCH_OMAP3=n CONFIG_ARCH_OMAP4=n CONFIG_SOC_OMAP5=n CONFIG_SOC_AM33XX=y Then I run: scripts/kconfig/merge_config.sh arch/arm/configs/omap2plus_defconfig /path/to/am335x_only.config This gives me omap2plus_defconfig with overrides from my fragment. Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@linaro.org (Kevin Hilman) Date: Wed, 26 Jun 2013 16:57:38 -0700 Subject: OMAP baseline test results for v3.10-rc6 In-Reply-To: <51CB48BA.7020401@ti.com> (Tom Rini's message of "Wed, 26 Jun 2013 16:02:02 -0400") References: <20130625160243.GE22312@arwen.pp.htv.fi> <51C9F0A8.1050607@ti.com> <87fvw6t136.fsf@linaro.org> <79CD15C6BA57404B839C016229A409A83ECC952D@DBDE04.ent.ti.com> <51CAEB33.5010101@ti.com> <51CAEBF3.1010507@ti.com> <51CB28BD.2020105@ti.com> <51CB48BA.7020401@ti.com> Message-ID: <87ehboqvbh.fsf@linaro.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Tom Rini writes: > On 06/26/2013 01:58 PM, Paul Walmsley wrote: >> On Wed, 26 Jun 2013, Tom Rini wrote: >> >>> OK, is there a reason to not be using omap2plus_defconfig? My pass/fail >>> here is based on that config and enabling, or not, dtb append. Seems >>> like it would be one less thing to maintain on your end and it would be >>> on TIs end (roughly speaking) to make sure our platforms that ought to >>> be working upstream have what they need enabled in the defconfig(s) in >>> question. >> >> That would be convenient for me, but part of the goal is to verify that a >> Kconfig that deselects all OMAPs other than AM33xx continues to work. >> >> So the build process for am33xx_only here goes something like: >> >> 1. Start with omap2plus_defconfig >> >> 2. Turn off support for everything other than AM33xx in the SoC target >> selection menus >> >> 3. Turn on the appended DTB and compat ATAGs options >> >> You might consider adding something like this to your pass/fail tests. > > Adding more and different build+boot tests is on the list. I guess you > could automate this with a fraagment of everything am33xx must have to > boot+root and alldefconfig for the rest? Since I recently discovered scripts/kconfig/merge_config.sh, I thought I'd share a very convenient way of automating the variations on a kconfig theme, just in case I'm not the last one to discover this useful tool. For example, I have the following in am335x_only.config: CONFIG_ARCH_OMAP2=n CONFIG_ARCH_OMAP3=n CONFIG_ARCH_OMAP4=n CONFIG_SOC_OMAP5=n CONFIG_SOC_AM33XX=y Then I run: scripts/kconfig/merge_config.sh arch/arm/configs/omap2plus_defconfig /path/to/am335x_only.config This gives me omap2plus_defconfig with overrides from my fragment. Kevin