linux-kernel - Re: [PATCH v2 1/2] soc: qcom: Add device tree binding for SMEM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Apr 2015 20:28:19 -0700
From:	Bjorn Andersson <bjorn@...o.se>
To:	Jeffrey Hugo <jhugo@...eaurora.org>
Cc:	Bjorn Andersson <bjorn.andersson@...ymobile.com>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Andry Gross <agross@...eaurora.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	linux-arm-msm <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] soc: qcom: Add device tree binding for SMEM

On Thu, Apr 23, 2015 at 1:01 PM, Jeffrey Hugo <jhugo@...eaurora.org> wrote:
> On 4/11/2015 5:32 PM, Bjorn Andersson wrote:
>>
>> Add device tree binding documentation for the Qualcom Shared Memory
>> manager.
>>
[..]
>
> For my information, is there any intention to support the relocatable
> smem_region by looking it up at init time?  It does not seem like it would
> be possible to support that with this binding.
>

I haven't been able to grasp the purpose of making the smem addresses
completely dynamic. As far as I can see there might be use cases where
certain devices needs to move the smem region from the default area.
But even so, it's not dynamically choosen so it's in essence static -
so we can just encode it in the individual dts files.

Regards,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/