Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux