From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757104AbbIYQPw (ORCPT ); Fri, 25 Sep 2015 12:15:52 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:32879 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756818AbbIYQPu (ORCPT ); Fri, 25 Sep 2015 12:15:50 -0400 Subject: Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags To: Nishanth Menon , Murali Karicheri , Santosh Shilimkar References: <1442938118-4718-1-git-send-email-nm@ti.com> <1442938118-4718-2-git-send-email-nm@ti.com> <5602ED34.9010108@oracle.com> <56040323.1080409@ti.com> <560406C2.6090200@ti.com> <56041CA4.40208@ti.com> <56055F1F.4060401@ti.com> <560565AF.2010701@oracle.com> <56056FD9.5060000@ti.com> Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org From: santosh shilimkar Organization: Oracle Corporation Message-ID: <56057319.9080104@oracle.com> Date: Fri, 25 Sep 2015 09:15:21 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <56056FD9.5060000@ti.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 9/25/2015 9:01 AM, Nishanth Menon wrote: > On 09/25/2015 10:18 AM, santosh shilimkar wrote: >> On 9/25/2015 7:50 AM, Nishanth Menon wrote: > [...] >>> But, how about userspace >>> needing to know which SoC they are on, without needing to depend on >>> board->soc mapping? How do we help resolve that? >>> >> Why the user space should care about exact SOC ? > > examples vary - trivial one is: debug tools like omapconf[1] or testing > tools like opentest[2] need some standard way to ensure Linux kernel is > functional - trusting the least set of parameters is usually what we > would prefer. while building a generic distro such as debian or yocto, > one prefers NOT to need to do a package build per SoC/perboard - that > never scales. instead, you'd like the same application run on different > systems dynamically. > I guessed omapconf example is coming though Keystone has no such tool yet ;-). Opentest shouldn't need that info either. I do agree that having a soc along with board is useful in longer run to accommodation more boards and variants. And only on that merit, I am willing to take these patches. Please refresh the series commit messages based on the discussion so far and repost. Will pick it up then. Regards, Santosh