Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757545Ab3IMCF4 (ORCPT <rfc822;w@1wt.eu>);
	Thu, 12 Sep 2013 22:05:56 -0400
Received: from smtp.codeaurora.org ([198.145.11.231]:59781 "EHLO
	smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757047Ab3IMCFy convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 12 Sep 2013 22:05:54 -0400
Subject: Re: [PATCH] ARM: msm: Move msm devicetrees under a Qualcomm dir
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Kumar Gala <galak@codeaurora.org>
In-Reply-To: <20130912224737.GA24937@codeaurora.org>
Date: Thu, 12 Sep 2013 21:05:52 -0500
Cc: Olof Johansson <olof@lixom.net>, Rob Herring <rob.herring@calxeda.com>,
        Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>,
        Stephen Warren <swarren@wwwdotorg.org>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Russell King <linux@arm.linux.org.uk>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-kernel@vger.kernel.org list" <linux-kernel@vger.kernel.org>,
        Rohit Vaswani <rvaswani@codeaurora.org>, linux-arm-msm@vger.kernel.org,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Content-Transfer-Encoding: 8BIT
Message-Id: <9EA264FE-7621-458D-8333-9340DDBFC4EE@codeaurora.org>
References: <1379003839-16068-1-git-send-email-galak@codeaurora.org> <CAOesGMisWLwYKotGDFPW6PyHJs=_+fohTdC08SGjsv2FXaa7Fg@mail.gmail.com> <25E0B143-658E-4CCC-A88A-0AF70FFF33CE@codeaurora.org> <CAOesGMhfdvyJ_2AA2e8iO_2e=q7KgpyNbcriPKFw-RLormG6bA@mail.gmail.com> <3E38F48E-EE41-4564-84A1-36CF07B08811@codeaurora.org> <20130912224737.GA24937@codeaurora.org>
To: David Brown <davidb@codeaurora.org>
X-Mailer: Apple Mail (2.1283)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2088
Lines: 48


On Sep 12, 2013, at 5:47 PM, David Brown wrote:

> On Thu, Sep 12, 2013 at 12:55:36PM -0500, Kumar Gala wrote:
>> 
>> On Sep 12, 2013, at 12:06 PM, Olof Johansson wrote:
> 
>>> My original request to please use a common prefix for your product
>>> families stands. Please prefix with msm-*, or if you have to, qcom-*
>>> instead, since you guys can't seem to make your mind up on standard
>>> prefixes (msm, apq, etc).
>> 
>> This is silly, I dont see the reason to go with
>> qcom-apq<SOC>-<BOARD>.dts and than in the future drop qcom- when we
>> mostly likely shift to a dir structure.  As engineers we are all too
>> aware of the lack of sanity in marketing names, but its what we have
>> so we have to live with it.
> 
> At least what we'd decided a year or two ago was to call _everything_
> with an msm* prefix.  If marketing comes up with cute prefixes for
> things, we would basically ignore them.  So, under that, it should be
> an msm8074-dragonboard.  Admittedly, it might be a little confusing
> with the name of the product having the apq in it, but as others have
> pointed out, I think there is less confusing than not having a common
> prefix on our MSM products.
> 
> At least so far, there are no chips where apq vs msm actually
> distinguishes anything.  In fact, a simple "decoder ring" would point
> out that the 'apq' usually corresponds with the second digit being a
> zero.  It doesn't help that we've added an 'mpq' prefix as well.
> 
> I don't really see how to satisfy all of this other than qcom-apq*, or
> just continue to use msm*.


I think msm has run out of steam, especially as more SoCs come out of Qualcomm that aren't just targeting phones & tablets.

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/