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.fisc...@ettus.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/