From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 2/3] Documentation: DT: Add entry for DPAA2 console Date: Thu, 3 Jan 2019 14:32:50 -0600 Message-ID: <20190103203250.GA18731@bogus> References: <1545406240-3061-1-git-send-email-ioana.ciornei@nxp.com> <1545406240-3061-3-git-send-email-ioana.ciornei@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1545406240-3061-3-git-send-email-ioana.ciornei@nxp.com> Sender: linux-kernel-owner@vger.kernel.org To: Ioana Ciornei Cc: Leo Li , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , "shawnguo@kernel.org" , Roy Pledge , Ioana Ciocoi Radulescu , "linux-kernel@vger.kernel.org" List-Id: devicetree@vger.kernel.org On Fri, Dec 21, 2018 at 03:31:11PM +0000, Ioana Ciornei wrote: > This patch adds a devicetree binding documentation for > FSL's DPAA2 console. > > Signed-off-by: Ioana Ciornei > --- > Documentation/devicetree/bindings/misc/dpaa2-console.txt | 11 +++++++++++ > MAINTAINERS | 1 + > 2 files changed, 12 insertions(+) > create mode 100644 Documentation/devicetree/bindings/misc/dpaa2-console.txt > > diff --git a/Documentation/devicetree/bindings/misc/dpaa2-console.txt b/Documentation/devicetree/bindings/misc/dpaa2-console.txt > new file mode 100644 > index 0000000..f4e16b1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/misc/dpaa2-console.txt > @@ -0,0 +1,11 @@ > +DPAA2 console support > + > +Required properties: > + > + - compatible > + Value type: > + Definition: Must be "dpaa2-console". > + - reg > + Value type: > + Definition: A standard property. Specifies the region where the MCFBA > + (MC firmware base address) register can be found. What's the relationship between MCFBA and the console? The binding should describe the h/w block or firmware interface not the feature you want to implement. Are there other functions provided by the MC firmware? Rob