On Mon, 16 Aug 2021 at 15:00, <haibo.chen@xxxxxxx> wrote: > > From: Haibo Chen <haibo.chen@xxxxxxx> > > Add a new fsl,sdio-async-interrupt-enabled binding for sdio devices > which enable the async interrupt function. When get this property, > driver will avoid to use DAT[1] for hardware auto tuning check. > > Signed-off-by: Haibo Chen <haibo.chen@xxxxxxx> > --- > .../devicetree/bindings/mmc/fsl-imx-esdhc.yaml | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml > index b5baf439fbac..8a9f1775b0e2 100644 > --- a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml > +++ b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml > @@ -122,6 +122,16 @@ properties: > - const: state_200mhz > - const: sleep > > + fsl,sdio-async-interrupt-enabled: > + description: | > + Recommend for SDIO cards that enables SDIO async interrupt for SDR104 and SDR50 > + operating modes. SDIO async interrupt uses DAT[1] to signal the card's interrupt. > + uSDHC tuning mechanism must use DAT[0] and CMD signals to avoid a possible > + conflict and incorrect delay line calculated by the uSDHC auto tuning mechanism. > + Enabling this device tree property is only recommended for layouts that are > + matching the SD interface length. > + type: boolean We already have a common mmc property, "cap-sdio-irq", that tells whether the controller supports SDIO irqs (which is delivered on DAT1). Can't you use this instead? > + > required: > - compatible > - reg > -- > 2.17.1 > Kind regards Uffe
