From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751973AbdEAWrM (ORCPT <rfc822;w@1wt.eu>);
        Mon, 1 May 2017 18:47:12 -0400
Received: from mail-pg0-f45.google.com ([74.125.83.45]:35776 "EHLO
        mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751944AbdEAWrI (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 1 May 2017 18:47:08 -0400
Date: Mon, 1 May 2017 15:47:04 -0700
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Imran Khan <kimran@codeaurora.org>
Cc: Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@codeaurora.org>,
        Andy Gross <agross@codeaurora.org>,
        linux-arm-msm <linux-arm-msm@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>
Subject: Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM
 socinfo driver
Message-ID: <20170501224704.GB12031@Bjorns-MacBook-Pro-2.local>
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>
 <CAL_JsqJta+S7d6zC3KYiqm7BDY-WtV+HmCKh5kdfSSE5WFv57w@mail.gmail.com>
 <20170424230530.GN15143@minitux>
 <CAL_Jsq+qiSvD3ozvaVu+BbZi5gW8oQG3LDJfFggG2UnYgfbQYA@mail.gmail.com>
 <20170425230837.GO15143@minitux>
 <217ee635-ae48-db8b-b8d8-74dfded11f8a@codeaurora.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <217ee635-ae48-db8b-b8d8-74dfded11f8a@codeaurora.org>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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
> >> <bjorn.andersson@linaro.org> 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?

Regards,
Bjorn