| 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
| ||
|
Message-ID: <20150724145027.GY2531@xsjsorenbubuntu> Date: Fri, 24 Jul 2015 07:50:27 -0700 From: Sören Brinkmann <soren.brinkmann@...inx.com> To: Michal Simek <michal.simek@...inx.com> CC: Moritz Fischer <moritz.fischer@...us.com>, <p.zabel@...gutronix.de>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org> Subject: Re: [RFC 1/3] docs: dts: Added documentation for Xilinx Zynq PL Reset bindings. On Fri, 2015-07-24 at 06:40AM +0200, Michal Simek wrote: > On 07/24/2015 12:51 AM, Moritz Fischer wrote: > > Signed-off-by: Moritz Fischer <moritz.fischer@...us.com> > > --- > > Documentation/devicetree/bindings/reset/zynq-reset-pl.txt | 13 +++++++++++++ > > 1 file changed, 13 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset-pl.txt > > > > diff --git a/Documentation/devicetree/bindings/reset/zynq-reset-pl.txt b/Documentation/devicetree/bindings/reset/zynq-reset-pl.txt > > new file mode 100644 > > index 0000000..ac4499e > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/reset/zynq-reset-pl.txt > > @@ -0,0 +1,13 @@ > > +Xilinx Zynq PL Reset Manager > > I think there is no reason to be just PL specific. That was my first thought too. Why not model all the resets in the SLCR? Sören -- 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