From: Imran Khan <kimran@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.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
Date: Wed, 3 May 2017 18:21:42 +0530 [thread overview]
Message-ID: <340a1433-6899-a9bb-3fc0-79b731049843@codeaurora.org> (raw)
In-Reply-To: <20170501224704.GB12031@Bjorns-MacBook-Pro-2.local>
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@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?
>
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
prev parent reply other threads:[~2017-05-03 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 16:47 [PATCH v10 0/2] soc: qcom: Add SoC info driver Imran Khan
2017-02-20 16:47 ` [PATCH v10 1/2] " Imran Khan
2017-02-20 16:47 ` [PATCH v10 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver Imran Khan
2017-02-22 14:04 ` [v10, " Rob Herring
2017-03-06 6:49 ` Imran Khan
2017-04-18 14:23 ` Imran Khan
2017-04-24 16:00 ` Imran Khan
2017-04-24 16:27 ` Rob Herring
2017-04-24 23:05 ` Bjorn Andersson
2017-04-25 7:35 ` Imran Khan
2017-04-25 17:13 ` Rob Herring
2017-04-25 23:08 ` Bjorn Andersson
2017-05-01 13:07 ` Imran Khan
2017-05-01 22:47 ` Bjorn Andersson
2017-05-03 12:51 ` Imran Khan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=340a1433-6899-a9bb-3fc0-79b731049843@codeaurora.org \
--to=kimran@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).