Hi Stephen, Thanks for the review,
> -----Original Message----- > From: Stephen Boyd [mailto:sb...@kernel.org] > Sent: Sunday, July 08, 2018 10:29 PM > To: Jolly Shah <jol...@xilinx.com>; ard.biesheu...@linaro.org; > dmitry.torok...@gmail.com; gre...@linuxfoundation.org; > hkallwe...@gmail.com; keesc...@chromium.org; linux-...@vger.kernel.org; > mark.rutl...@arm.com; m...@codeblueprint.co.uk; Michal Simek > <mich...@xilinx.com>; mi...@kernel.org; mturque...@baylibre.com; > robh...@kernel.org; sb...@codeaurora.org; sudeep.ho...@arm.com > Cc: Rajan Vaja <raj...@xilinx.com>; linux-arm-ker...@lists.infradead.org; > linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; Jolly Shah > <jol...@xilinx.com> > Subject: Re: [PATCH v9 07/10] firmware: xilinx: Add debugfs for IOCTL API > > Quoting Jolly Shah (2018-06-20 10:40:32) > > From: Rajan Vaja <raj...@xilinx.com> > > > > Add debugfs file to set/get IOCTL using debugfs interface. > > IOCTLs and debugfs aren't the same thing. Why are the two being mixed > together? Is some sort of userspace ABI being created here to control clks > with > usermode drivers? This is not standard ioctl. This is type of ZynqMP API just like other APIs. This debugfs is created to debug ZynqMP IOCTL API. Thanks, Jolly Shah
