On Thu, 10 Sep 2020 at 12:54, Andrew Jeffery <[email protected]> wrote: > > Add properties to control the phase delay for input and output data > sampling. > > Signed-off-by: Andrew Jeffery <[email protected]> > --- > Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > index 987b287f3bff..75effd411554 100644 > --- a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > +++ b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > @@ -61,6 +61,14 @@ patternProperties: > sdhci,auto-cmd12: > type: boolean > description: Specifies that controller should use auto CMD12 > + "aspeed,input-phase": > + $ref: '/schemas/types.yaml#/definitions/uint32' > + description: > + The input clock phase delay value. > + "aspeed,output-phase": > + $ref: '/schemas/types.yaml#/definitions/uint32' > + description: > + The output clock phase delay value.
We already have a common mmc clk-phase* binding, see mmc-controller.yaml. As matter of fact, there is one binding per speed mode. Could that work for this case as well? Kind regards Uffe
