From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755841Ab3AVUqy (ORCPT ); Tue, 22 Jan 2013 15:46:54 -0500 Received: from mail-ob0-f169.google.com ([209.85.214.169]:62580 "EHLO mail-ob0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751567Ab3AVUqx (ORCPT ); Tue, 22 Jan 2013 15:46:53 -0500 Message-ID: <50FEFAB9.4030503@gmail.com> Date: Tue, 22 Jan 2013 14:46:49 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Arnd Bergmann CC: Matt Sealey , Lior Amsalem , Andrew Lunn , Ike Pan , John Stultz , David Marlin , Yehuda Yitschak , Jani Monoses , Russell King , Tawfik Bayouk , Dan Frazier , Eran Ben-Avi , Leif Lindholm , Sebastian Hesselbarth , Jason Cooper , Nadav Haklai , Jon Masters , "devicetree-discuss@lists.ozlabs.org" , Rob Herring , Thomas Gleixner , Linux ARM Kernel ML , Chris Van Hoof , LKML , Maen Suleiman , Shadi Ammouri Subject: Re: [PATCH 3/6] arm: kconfig: don't select TWD with local timer for Armada 370/XP References: <1358790842-2986-1-git-send-email-gregory.clement@free-electrons.com> <201301211831.45947.arnd@arndb.de> <201301212044.41865.arnd@arndb.de> In-Reply-To: <201301212044.41865.arnd@arndb.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/21/2013 02:44 PM, Arnd Bergmann wrote: >> On multiplatform kernels where at least one arch has TWD support, it >> will be included, and where not, it will not. >> >> It doesn't seem logical for a feature descriptor (HAVE_ARM_TWD) to >> rely on greater knowledge of what platforms may or may not support it. >> If we had to include every platform in that list it would be unwieldy. > > I would expect that all future platforms have ARM_TWD, so the list > of the platforms that don't is not going to grow much, but the list > of platforms that do will keep growing. No, I expect all future platforms will have architected timers. TWD is pretty much A9 and A5 only I believe. Same with SCU. I've probably missed some in my list. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 3/6] arm: kconfig: don't select TWD with local timer for Armada 370/XP Date: Tue, 22 Jan 2013 14:46:49 -0600 Message-ID: <50FEFAB9.4030503@gmail.com> References: <1358790842-2986-1-git-send-email-gregory.clement@free-electrons.com> <201301211831.45947.arnd@arndb.de> <201301212044.41865.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201301212044.41865.arnd@arndb.de> Sender: linux-kernel-owner@vger.kernel.org To: Arnd Bergmann Cc: Matt Sealey , Lior Amsalem , Andrew Lunn , Ike Pan , John Stultz , David Marlin , Yehuda Yitschak , Jani Monoses , Russell King , Tawfik Bayouk , Dan Frazier , Eran Ben-Avi , Leif Lindholm , Sebastian Hesselbarth , Jason Cooper , Nadav Haklai , Jon Masters , "devicetree-discuss@lists.ozlabs.org" , Rob Herring , Thomas Gleixner , Linux ARM Kernel ML , Chris Van Hoof List-Id: devicetree@vger.kernel.org On 01/21/2013 02:44 PM, Arnd Bergmann wrote: >> On multiplatform kernels where at least one arch has TWD support, it >> will be included, and where not, it will not. >> >> It doesn't seem logical for a feature descriptor (HAVE_ARM_TWD) to >> rely on greater knowledge of what platforms may or may not support it. >> If we had to include every platform in that list it would be unwieldy. > > I would expect that all future platforms have ARM_TWD, so the list > of the platforms that don't is not going to grow much, but the list > of platforms that do will keep growing. No, I expect all future platforms will have architected timers. TWD is pretty much A9 and A5 only I believe. Same with SCU. I've probably missed some in my list. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: robherring2@gmail.com (Rob Herring) Date: Tue, 22 Jan 2013 14:46:49 -0600 Subject: [PATCH 3/6] arm: kconfig: don't select TWD with local timer for Armada 370/XP In-Reply-To: <201301212044.41865.arnd@arndb.de> References: <1358790842-2986-1-git-send-email-gregory.clement@free-electrons.com> <201301211831.45947.arnd@arndb.de> <201301212044.41865.arnd@arndb.de> Message-ID: <50FEFAB9.4030503@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 01/21/2013 02:44 PM, Arnd Bergmann wrote: >> On multiplatform kernels where at least one arch has TWD support, it >> will be included, and where not, it will not. >> >> It doesn't seem logical for a feature descriptor (HAVE_ARM_TWD) to >> rely on greater knowledge of what platforms may or may not support it. >> If we had to include every platform in that list it would be unwieldy. > > I would expect that all future platforms have ARM_TWD, so the list > of the platforms that don't is not going to grow much, but the list > of platforms that do will keep growing. No, I expect all future platforms will have architected timers. TWD is pretty much A9 and A5 only I believe. Same with SCU. I've probably missed some in my list. Rob