| Message ID | BYAPR20MB2472E8B10BFEF75E7950BBC0BCF79@BYAPR20MB2472.namprd20.prod.outlook.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Allwinner R329 SPI support | expand |
On 4/22/22 10:56 AM, icenowy@outlook.com wrote: > From: Icenowy Zheng <icenowy@aosc.io> > > Allwinner R329 SPI has two controllers, and the second one has helper > functions for MIPI-DBI Type C. > > Add compatible strings for these controllers > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io> > --- > .../devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml > index ca4c95345a49..6354635241fc 100644 > --- a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml > +++ b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml > @@ -21,6 +21,8 @@ properties: > oneOf: > - const: allwinner,sun6i-a31-spi > - const: allwinner,sun8i-h3-spi > + - const: allwinner,sun50i-r329-spi > + - const: allwinner,sun50i-r329-spi-dbi As far as I'm aware, the SPI portion of the DBI controller is register-compatible with the regular SPI controller. So I would expect using that as a fallback compatible for the DBI variant. Regards, Samuel > - items: > - enum: > - allwinner,sun8i-r40-spi >
在 2022-04-22星期五的 18:49 -0500，Samuel Holland写道： > On 4/22/22 10:56 AM, icenowy@outlook.com wrote: > > From: Icenowy Zheng <icenowy@aosc.io> > > > > Allwinner R329 SPI has two controllers, and the second one has > > helper > > functions for MIPI-DBI Type C. > > > > Add compatible strings for these controllers > > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io> > > --- > > .../devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml | > > 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/spi/allwinner,sun6i- > > a31-spi.yaml > > b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31- > > spi.yaml > > index ca4c95345a49..6354635241fc 100644 > > --- a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31- > > spi.yaml > > +++ b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31- > > spi.yaml > > @@ -21,6 +21,8 @@ properties: > > oneOf: > > - const: allwinner,sun6i-a31-spi > > - const: allwinner,sun8i-h3-spi > > + - const: allwinner,sun50i-r329-spi > > + - const: allwinner,sun50i-r329-spi-dbi > > As far as I'm aware, the SPI portion of the DBI controller is > register-compatible with the regular SPI controller. So I would > expect using > that as a fallback compatible for the DBI variant. This sounds reasonable. > > Regards, > Samuel > > > - items: > > - enum: > > - allwinner,sun8i-r40-spi > > >
diff --git a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml index ca4c95345a49..6354635241fc 100644 --- a/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml +++ b/Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml @@ -21,6 +21,8 @@ properties: oneOf: - const: allwinner,sun6i-a31-spi - const: allwinner,sun8i-h3-spi + - const: allwinner,sun50i-r329-spi + - const: allwinner,sun50i-r329-spi-dbi - items: - enum: - allwinner,sun8i-r40-spi