Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Ioana Ciornei <ioana.ciornei@nxp.com>
To:     Rob Herring <robh@kernel.org>
CC:     Leo Li <leoyang.li@nxp.com>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "shawnguo@kernel.org" <shawnguo@kernel.org>,
        Roy Pledge <roy.pledge@nxp.com>,
        Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/3] Documentation: DT: Add entry for DPAA2 console
Thread-Topic: [PATCH 2/3] Documentation: DT: Add entry for DPAA2 console
Thread-Index: AQHUmUIzLDDB55qxuECeWDzF4+LHLKWeFHgAgAFZMBA=
Date:   Fri, 4 Jan 2019 17:50:37 +0000
Message-ID: <VI1PR0402MB280090CC66E990AD6E82F52FE08E0@VI1PR0402MB2800.eurprd04.prod.outlook.com>
References: <1545406240-3061-1-git-send-email-ioana.ciornei@nxp.com>
 <1545406240-3061-3-git-send-email-ioana.ciornei@nxp.com>
 <20190103203250.GA18731@bogus>
In-Reply-To: <20190103203250.GA18731@bogus>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d579e93b-544b-4446-664c-08d6726d2262
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2019 17:50:37.2028
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0402MB3389
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> Subject: Re: [PATCH 2/3] Documentation: DT: Add entry for DPAA2 console
>=20
> 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 <ioana.ciornei@nxp.com>
> > ---
> >  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: <string>
> > +        Definition: Must be "dpaa2-console".
> > +    - reg
> > +        Value type: <prop-encoded-array>
> > +        Definition: A standard property.  Specifies the region where t=
he MCFBA
> > +                    (MC firmware base address) register can be found.
>=20
> What's the relationship between MCFBA and the console?

The console is basically a log buffer of the MC firmware, and is found at a=
 known offset compared to the firmware image's runtime base address.

> The binding should describe the h/w block or firmware interface not the f=
eature you want to
> implement. Are there other functions provided by the MC firmware?

The MC firmware manages all hardware resources related to networking or any=
 other accelerators.
Any interaction with the firmware is made through commands put in memory ma=
pped regions.
The fsl-mc bus driver is the one that already manages this interaction with=
 the MC.

Ioana

>=20
> Rob