| Message ID | 20220307143421.1106209-8-andre.przywara@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | None | expand |
On Mon, 07 Mar 2022 14:34:14 +0000, Andre Przywara wrote: > From: Jesse Taube <mr.bossman075@gmail.com> > > The Allwinner F1C100 series contains two MMC controller blocks. From > comparing the data sheets, they seem to be compatible with the one used > in the Allwinner A20: the register layout is the same, and they use the > same separate sample and output clocks design. > The only difference is the missing reset line in the A20 version, but > both the binding and the Linux driver make this optional, so it's still > a fit. > > Add the new SoC specific name and require it to be paired with the A20 > fallback name, as this is all the driver needs to care about. > > Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com> > Signed-off-by: Andre Przywara <andre.przywara@arm.com> > --- > .../devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml | 3 +++ > 1 file changed, 3 insertions(+) > Acked-by: Rob Herring <robh@kernel.org>
On 3/7/22 8:34 AM, Andre Przywara wrote: > From: Jesse Taube <mr.bossman075@gmail.com> > > The Allwinner F1C100 series contains two MMC controller blocks. From > comparing the data sheets, they seem to be compatible with the one used > in the Allwinner A20: the register layout is the same, and they use the > same separate sample and output clocks design. > The only difference is the missing reset line in the A20 version, but > both the binding and the Linux driver make this optional, so it's still > a fit. > > Add the new SoC specific name and require it to be paired with the A20 > fallback name, as this is all the driver needs to care about. > > Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com> > Signed-off-by: Andre Przywara <andre.przywara@arm.com> Acked-by: Samuel Holland <samuel@sholland.org>
On Mon, 7 Mar 2022 at 15:34, Andre Przywara <andre.przywara@arm.com> wrote: > > From: Jesse Taube <mr.bossman075@gmail.com> > > The Allwinner F1C100 series contains two MMC controller blocks. From > comparing the data sheets, they seem to be compatible with the one used > in the Allwinner A20: the register layout is the same, and they use the > same separate sample and output clocks design. > The only difference is the missing reset line in the A20 version, but > both the binding and the Linux driver make this optional, so it's still > a fit. > > Add the new SoC specific name and require it to be paired with the A20 > fallback name, as this is all the driver needs to care about. > > Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com> > Signed-off-by: Andre Przywara <andre.przywara@arm.com> Applied for next, thanks! Kind regards Uffe > --- > .../devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml b/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml > index 4f62ad6ce50c..76137132500d 100644 > --- a/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml > +++ b/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml > @@ -55,6 +55,9 @@ properties: > - items: > - const: allwinner,sun50i-h616-mmc > - const: allwinner,sun50i-a100-mmc > + - items: > + - const: allwinner,suniv-f1c100s-mmc > + - const: allwinner,sun7i-a20-mmc > > reg: > maxItems: 1 > -- > 2.25.1 >
diff --git a/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml b/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml index 4f62ad6ce50c..76137132500d 100644 --- a/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml +++ b/Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml @@ -55,6 +55,9 @@ properties: - items: - const: allwinner,sun50i-h616-mmc - const: allwinner,sun50i-a100-mmc + - items: + - const: allwinner,suniv-f1c100s-mmc + - const: allwinner,sun7i-a20-mmc reg: maxItems: 1