[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <340a1433-6899-a9bb-3fc0-79b731049843@codeaurora.org>
Date: Wed, 3 May 2017 18:21:42 +0530
From: Imran Khan <kimran@...eaurora.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Stephen Boyd <sboyd@...eaurora.org>,
Andy Gross <agross@...eaurora.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-soc@...r.kernel.org>
Subject: Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM
socinfo driver
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
>>>> <bjorn.andersson@...aro.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?
>
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@...r.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
Powered by blists - more mailing lists