[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJMfUyi06jMZOyQX956HjBvyHbKHEcBGt+GTZrj3Da5DA@mail.gmail.com>
Date: Thu, 1 Feb 2018 09:11:36 -0600
From: Rob Herring <robh@...nel.org>
To: Jolly Shah <JOLLYS@...inx.com>
Cc: "mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"keescook@...omium.org" <keescook@...omium.org>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"matt@...eblueprint.co.uk" <matt@...eblueprint.co.uk>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>,
"michal.simek@...inx.com" <michal.simek@...inx.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rajan Vaja <RAJANV@...inx.com>,
"sudeep.holla@....com" <sudeep.holla@....com>,
"mingo@...nel.org" <mingo@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"hkallweit1@...il.com" <hkallweit1@...il.com>
Subject: Re: [PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware
On Wed, Jan 31, 2018 at 12:03 PM, Jolly Shah <JOLLYS@...inx.com> wrote:
> Hi Rob,
> Thanks for the review,
>
>> -----Original Message-----
>> From: Rob Herring [mailto:robh@...nel.org]
>> Sent: Tuesday, January 30, 2018 9:08 AM
>> To: Jolly Shah <JOLLYS@...inx.com>
>> Cc: ard.biesheuvel@...aro.org; mingo@...nel.org;
>> gregkh@...uxfoundation.org; matt@...eblueprint.co.uk;
>> sudeep.holla@....com; hkallweit1@...il.com; keescook@...omium.org;
>> dmitry.torokhov@...il.com; michal.simek@...inx.com;
>> mark.rutland@....com; linux-arm-kernel@...ts.infradead.org; linux-
>> kernel@...r.kernel.org; devicetree@...r.kernel.org; Jolly Shah
>> <JOLLYS@...inx.com>; Rajan Vaja <RAJANV@...inx.com>
>> Subject: Re: [PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP
>> firmware
>>
>> On Wed, Jan 24, 2018 at 03:21:11PM -0800, Jolly Shah wrote:
>> > Add documentation to describe Xilinx ZynqMP firmware driver bindings.
>> > Firmware driver provides an interface to firmware APIs. Interface APIs
>> > can be used by any driver to communicate to PMUFW (Platform Management
>> > Unit).
>> >
>> > Signed-off-by: Jolly Shah <jollys@...inx.com>
>> > Signed-off-by: Rajan Vaja <rajanv@...inx.com>
>> > ---
>> > .../bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt | 16
>> ++++++++++++++++
>> > 1 file changed, 16 insertions(+)
>> > create mode 100644
>> > Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware
>> > .txt
>> >
>> > diff --git
>> > a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmwa
>> > re.txt
>> > b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmwa
>> > re.txt
>> > new file mode 100644
>> > index 0000000..a7aaf56
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi
>> > +++ rmware.txt
>> > @@ -0,0 +1,16 @@
>> > +Xilinx Zynq MPSoC Firmware Device Tree Bindings
>> > +
>> > +The zynqmp-firmware node describes the interface to platform firmware.
>>
>> Please define this a is child of /firmware.
>>
> I dint get you. It is already under firmware/xilinx.
Put it under a "firmware" node in DT. See other firmware bindings for examples.
Rob
Powered by blists - more mailing lists