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
| ||
|
Date: Tue, 30 Sep 2014 13:00:53 -0700 From: Bjorn Andersson <bjorn.andersson@...ymobile.com> To: Stephen Boyd <sboyd@...eaurora.org> CC: Kumar Gala <galak@...eaurora.org>, Andy Gross <agross@...eaurora.org>, Arnd Bergmann <arnd@...db.de>, Grant Likely <grant.likely@...aro.org>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Mark Rutland <mark.rutland@....com>, Pawel Moll <pawel.moll@....com>, Rob Herring <robh+dt@...nel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Lee Jones <lee.jones@...aro.org>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Samuel Ortiz <sameo@...ux.intel.com>, Suman Anna <s-anna@...com> Subject: Re: [RFC 1/7] soc: qcom: Add device tree binding for SMEM On Tue 30 Sep 12:03 PDT 2014, Stephen Boyd wrote: > On 09/29/14 17:34, Bjorn Andersson wrote: > > + > > +- reg: > > + Usage: required > > + Value type: <prop-encoded-array> > > + Definition: base address and size pair for each area representing the > > + shared memory. The first pair will must represent the "main" > > + area, where the shared memory header and table-of-content > > + can be found. > > > > + > > += EXAMPLE > > + > > + smem: smem@...0000 { > > + compatible = "qcom,smem"; > > + reg = <0x0fa00000 0x200000>, > > + <0xfc428000 0x4000>; > > Isn't this second entry rpm message ram? That isn't the same as smem. > Plus smem is part of ram (and rpm message ram is not) so we need to do > memory reservations or something. > Correct they are different, but smem covers both of those and allocations are only supposed to be done in the first of these. And I forgot to mention that I have the following in my dt: / { reserved-memory { #address-cells = <1>; #size-cells = <1>; ranges; smem@...0000 { #memory-region-cells = <0>; reg = <0x0fa00000 0x200000>; no-map; }; }; }; 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/
Powered by blists - more mailing lists