Hi Rob, On Mon, May 13, 2019 at 01:02:46PM -0500, Rob Herring wrote: > On Mon, May 06, 2019 at 03:35:32PM +0530, Manivannan Sadhasivam wrote: > > Document devicetree binding for Avenger96 board. > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx> > > --- > > Documentation/devicetree/bindings/arm/stm32/stm32.txt | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.txt b/Documentation/devicetree/bindings/arm/stm32/stm32.txt > > index 6808ed9ddfd5..eba363a4b514 100644 > > --- a/Documentation/devicetree/bindings/arm/stm32/stm32.txt > > +++ b/Documentation/devicetree/bindings/arm/stm32/stm32.txt > > @@ -8,3 +8,9 @@ using one of the following compatible strings: > > st,stm32f746 > > st,stm32h743 > > st,stm32mp157 > > + > > +Boards: > > + > > +Root node property compatible must contain one of below depending on board: > > + > > + - Avenger96: "arrow,stm32mp157a-avenger96" > > With which SoC compatible? > I referred some other platform bindings (non YAML) and they don't mention the SoC compatible with boards. Shall I just put it like below? Avenger96: "arrow,stm32mp157a-avenger96", "st,stm32mp157" Thanks, Mani Thanks, Mani > > -- > > 2.17.1 > >
