On Thu, May 16, 2019 at 11:23:05AM +0530, Manikanta Maddireddy wrote: > Add DT binding for "reset-gpios" property which supports GPIO based PERST# > signal. > > Signed-off-by: Manikanta Maddireddy <mmaddireddy@xxxxxxxxxx> > Reviewed-by: Rob Herring <robh@xxxxxxxxxx> > Acked-by: Thierry Reding <treding@xxxxxxxxxx> > --- > V4: No change > > V3: Moved to common pci binding doc > > V2: Using standard "reset-gpio" property > > Documentation/devicetree/bindings/pci/pci.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentation/devicetree/bindings/pci/pci.txt > index c77981c5dd18..79124898aa5b 100644 > --- a/Documentation/devicetree/bindings/pci/pci.txt > +++ b/Documentation/devicetree/bindings/pci/pci.txt > @@ -24,3 +24,6 @@ driver implementation may support the following properties: > unsupported link speed, for instance, trying to do training for > unsupported link speed, etc. Must be '4' for gen4, '3' for gen3, '2' > for gen2, and '1' for gen1. Any other values are invalid. > +- reset-gpios: > + If present this property specifies PERST# GPIO. Host drivers can parse the > + GPIO and apply fundamental reset to endpoints. As mentioned in patch 27/28, maybe mention here that this is only a workaround for bad board designs and that it shouldn't be necessary in the majority of cases. Thierry
Attachment:
signature.asc
Description: PGP signature
