On Mon, Apr 23, 2018 at 04:10:29PM +0800, Shawn Lin wrote: > power-delay-ms woule be used to substitute the hard-coded 10ms > delay waiting for power supply to be stable, specificed by individual > platform/board. Default to 10ms as before, if no available. > > Signed-off-by: Shawn Lin <shawn.lin@xxxxxxxxxxxxxx> > --- > > Changes in v2: None > > Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt > index 467cd7b..8db2ba0 100644 > --- a/Documentation/devicetree/bindings/mmc/mmc.txt > +++ b/Documentation/devicetree/bindings/mmc/mmc.txt > @@ -56,6 +56,8 @@ Optional properties: > - fixed-emmc-driver-type: for non-removable eMMC, enforce this driver type. > The value <n> is the driver type as specified in the eMMC specification > (table 206 in spec version 5.1). > +- power-delay-ms: Tunable delay waiting for I/O signalling and card power supply > + to be stable. Default to 10ms if no available. How long do you need? Would changing the default to say 20ms work and still be short enough others don't care? Can we use the same property as the mmc pwrseq binding defines: post-power-on-delay-ms Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
