From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751903AbdECMwE (ORCPT ); Wed, 3 May 2017 08:52:04 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:32996 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751177AbdECMv4 (ORCPT ); Wed, 3 May 2017 08:51:56 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org D58A56034D Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=kimran@codeaurora.org Subject: Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver To: Bjorn Andersson Cc: Rob Herring , Stephen Boyd , Andy Gross , linux-arm-msm , "linux-kernel@vger.kernel.org" , "open list:ARM/QUALCOMM SUPPORT" References: <1487609235-19458-3-git-send-email-kimran@codeaurora.org> <20170222140448.qo677wamcd44tgkw@rob-hp-laptop> <0bf24858-33b2-8d08-ddc3-df83a2bd696d@codeaurora.org> <4b85e85b-8c2a-a226-d3b2-67fde0820ada@codeaurora.org> <0d59bc31-7d35-06c8-68d1-13790a512c23@codeaurora.org> <20170424230530.GN15143@minitux> <20170425230837.GO15143@minitux> <217ee635-ae48-db8b-b8d8-74dfded11f8a@codeaurora.org> <20170501224704.GB12031@Bjorns-MacBook-Pro-2.local> From: Imran Khan Message-ID: <340a1433-6899-a9bb-3fc0-79b731049843@codeaurora.org> Date: Wed, 3 May 2017 18:21:42 +0530 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170501224704.GB12031@Bjorns-MacBook-Pro-2.local> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/2/2017 4:17 AM, Bjorn Andersson wrote: > On Mon 01 May 06:07 PDT 2017, Imran Khan wrote: > >> On 4/26/2017 4:38 AM, Bjorn Andersson wrote: >>> On Tue 25 Apr 10:13 PDT 2017, Rob Herring wrote: >>> >>>> On Mon, Apr 24, 2017 at 6:05 PM, Bjorn Andersson >>>> wrote: >>>>> On Mon 24 Apr 09:27 PDT 2017, Rob Herring wrote: > [..] >>>>>>>>>>> +What: /sys/devices/soc0/build_id > [..] >>>> Why does the kernel need to provide it? >>>> >>> >>> Imran, can you elaborate on how this information is travels from the >>> build system to the SMEM item? >>> >> >> This information, along with other SMEM items for this SMEM-id is >> written by the bootloader (SBL). Please let me know if this much >> information suffices in this regard. > > But where does the SBL find this information? Per my previous argument > it doesn't make sense to store this information compiled into one of the > components. Is it the CDT perhaps? > Yes SBL is getting this information from CDT. Thanks and Regards, Imran > Regards, > Bjorn > -- > To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a\nmember of the Code Aurora Forum, hosted by The Linux Foundation