From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752636AbbKYWkn (ORCPT ); Wed, 25 Nov 2015 17:40:43 -0500 Received: from mout.kundenserver.de ([212.227.126.134]:52672 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751422AbbKYWkk (ORCPT ); Wed, 25 Nov 2015 17:40:40 -0500 From: Arnd Bergmann To: Stephen Boyd Cc: Andy Gross , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Daniel Lezcano Subject: Re: [PATCH v2 1/3] ARM: qcom: Make an option for qcom clocksource platforms Date: Wed, 25 Nov 2015 23:40:07 +0100 Message-ID: <3228474.gifZbHXqvC@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <5656349D.70103@codeaurora.org> References: <1448485478-21699-1-git-send-email-sboyd@codeaurora.org> <6140735.DAZiajTbh1@wuerfel> <5656349D.70103@codeaurora.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:AmRIjQ4vr/CnQv27dzY8wtHh53MKlnv2ltQwzQrmpl5OM62uiV/ D1CkhwBufD1SsPjdXouHWCDFhRL41uEa8QsK9E2evNJqVEiX/+aRlqlCHfTNp3vfYo3wTGQ jIReYmOzbzB0wq6jS5bzEAIEu1fYbeQZ/38D1VLM01pZal4TvnEISHn5GPRRWZesHwxEyIr oZODQepY/SE82ILOVIoBg== X-UI-Out-Filterresults: notjunk:1;V01:K0:CX23XbcyRGw=:F/88V/OtseVTRqikQUHNWL V0WpJB2gP9Q21andqozsHRfZKnhIqqos9BQWpA8PzHVslYE5YZv1MLETizYSvIN/pnETTXhjY gmlKLZ/g4Csg/U1tVG6u0bpuZdEkFJQrai0qEy7+1ttmMoB56r1wu6q2bAQlu6piE3uZ8hM9l nUFqY/xvtUt8/3s9R5peXK+PeaTl1cwWSmUMRdASdxYRsnmVGhYggyVvQ4nAnFYNn9RanXp4a b0BBoK7gLyJ2Z/yo5466asa7nU+78Ox4rGLZ6urv4I9AWXAncC0S2P7ZHHu1kqChhKiKxTZsk K/xm7Cx9IVHCbhN9ZAjaOIZEbHS3iH//JRO8FYit2Vizm8iaEqZY9zUpZkmeGOYtfmipQwTVu u4423e/6YZijjwwHvJycwIAWgn8YC9x5sQH1BFyDP+UUG+CJyvsNuym5ULJ1KK/H6+OLiSfWP K1hQuU2g+bpb/zziDc986rUuK98qzdRe45oBg2xaVFXzf3FNS3MZpXNmv1+1BpvTVaG6OI1x2 C4JMJrGd9wxb6VE3zbhE3IDwIGqM9q1o1540Uccs1Iqgca5cXmHemX+wFnCFKA/mp0G2mUjcv 0w4Zob+BOQWvop+6BM6lpYd/DciRErnYgCfAKkhoXsB1RAQOx+4tjA9hMHYnmnslgKlj9JVSY le1Bycjx8spq/FtgoIYsMwN787+w4Q96Oq0orNsxQ4mhAR0NxNJtAMvHYyzhatMIGmBsCs7EF BfaOnW7q9yJ3ris4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 25 November 2015 14:22:21 Stephen Boyd wrote: > > > > > Is there any common way to classify these, e.g. calling them > > 'pre-2013 models' or 'Snapdragon S4' as a way to identify them? > > I was thinking I could leave it as ARCH_MSM_8X60 because that covers the > 6 and the 9, but that doesn't make me feel great. I have no idea what > Snapdragon S4 is, and that didn't exist when 8660 was first released. > pre-2013 models seems alright. Or perhaps ARCH_QCOM_PRE_8974? > > Internally (and sort of leaked externally now) we called MSM8960 and its > variants A-family, and the generation after B-family, so perhaps > ARCH_QCOM_A_FAMILY would be appropriate? The problem there is no end > user knows about this distinction. I think using internal code names like ARCH_QCOM_A_FAMILY here is fine, a lot of other platforms do similar things. Regarding end users, it's probably enough to explain the distinction in the help text, something like: The A-family includes all Snapdragon S1/S2/S3/S4 chips before 2013, up to the MSM8x60 and APQ8064 models. The B-family includes all Snapdragon 2xx/4xx/6xx/8xx models starting in 2013 with the MSM8x74. https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_device has a good overview that translates the marketing names into the model numbers but it doesn't have internal code names, so I'm not sure where the APQ8064 fits it, as it was marketed as both the "S4 Pro" and the "600", depending on the revision. Arnd