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: Fri, 1 Nov 2013 20:04:19 -0500 From: Rob Herring <robherring2@...il.com> To: Stephen Boyd <sboyd@...eaurora.org> Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, linux-arm-msm <linux-arm-msm@...r.kernel.org>, David Brown <davidb@...eaurora.org>, Rohit Vaswani <rvaswani@...eaurora.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 02/11] devicetree: bindings: Document Qualcomm cpus and enable-method On Fri, Nov 1, 2013 at 5:08 PM, Stephen Boyd <sboyd@...eaurora.org> wrote: > From: Rohit Vaswani <rvaswani@...eaurora.org> > > Scorpion and Krait are Qualcomm cpus. These cpus don't use the > spin-table enable-method. Instead they rely on mmio register > accesses to enable power and clocks to bring CPUs out of reset. > > Cc: <devicetree@...r.kernel.org> > Signed-off-by: Rohit Vaswani <rvaswani@...eaurora.org> > [sboyd: Split off into separate patch, renamed method to > qcom,mmio] > Signed-off-by: Stephen Boyd <sboyd@...eaurora.org> > --- > > This slightly conflicts with my krait EDAC series. > > Documentation/devicetree/bindings/arm/cpus.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt > index 37258f9..e2969fa2 100644 > --- a/Documentation/devicetree/bindings/arm/cpus.txt > +++ b/Documentation/devicetree/bindings/arm/cpus.txt > @@ -44,6 +44,8 @@ For the ARM architecture every CPU node must contain the following properties: > "marvell,mohawk" > "marvell,xsc3" > "marvell,xscale" > + "qcom,scorpion" > + "qcom,krait" > > And the following optional properties: > > @@ -52,6 +54,7 @@ And the following optional properties: > different types of cpus. > This should be one of: > "spin-table" > + "qcom,mmio" Not exactly specific. How would you handle variations in the enable method? The mmio method to enable is tied to the core type or SOC type? Rob -- 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