On Thu, Jan 16, 2020 at 6:00 AM Johan Jonker <jbx6244@xxxxxxxxx> wrote: > > See below. > > On 1/15/20 4:18 PM, Rob Herring wrote: > > On Tue, Jan 14, 2020 at 3:38 PM Johan Jonker <jbx6244@xxxxxxxxx> wrote: > >> > > > [...] > > > >> diff --git a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml > >> new file mode 100644 > >> index 000000000..6f85a21d0 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml > >> @@ -0,0 +1,88 @@ > >> +# SPDX-License-Identifier: GPL-2.0 > >> +%YAML 1.2 > >> +--- > >> +$id: http://devicetree.org/schemas/mmc/synopsys-dw-mshc.yaml# > >> +$schema: http://devicetree.org/meta-schemas/core.yaml# > >> + > >> +title: Synopsys Designware Mobile Storage Host Controller Binding > > [..] > > >> +examples: > >> + # The MSHC controller node can be split into two portions, SoC specific and > >> + # board specific portions as listed below. > > > > > > This split doesn't work because the examples are built and validated > > now. It may happen to because all the props are optional, but the > > board hunk goes unchecked. So please combine. > > > > Hi, > > I have no knowledge about this particular hardware to give a realistic > example. Could someone advise here? Or should I just use the first > example for now? Just combine the first part and one of the the 2 board hunks. I don't think having 2 board examples with the only diff being the dma properties adds much value. Rob
