From: Jolly Shah <JOLLYS@xilinx.com>
To: Stephen Boyd <sboyd@kernel.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>,
Michal Simek <michals@xilinx.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>
Cc: Rajan Vaja <RAJANV@xilinx.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH v9 07/10] firmware: xilinx: Add debugfs for IOCTL API
Date: Tue, 17 Jul 2018 20:01:40 +0000 [thread overview]
Message-ID: <SN1PR02MB3758432C38CC9580BC96182DB85C0@SN1PR02MB3758.namprd02.prod.outlook.com> (raw)
In-Reply-To: <153111415833.143105.8701882244160397855@swboyd.mtv.corp.google.com>
Hi Stephen,
Thanks for the review,
> -----Original Message-----
> From: Stephen Boyd [mailto:sboyd@kernel.org]
> Sent: Sunday, July 08, 2018 10:29 PM
> To: Jolly Shah <JOLLYS@xilinx.com>; ard.biesheuvel@linaro.org;
> dmitry.torokhov@gmail.com; gregkh@linuxfoundation.org;
> hkallweit1@gmail.com; keescook@chromium.org; linux-clk@vger.kernel.org;
> mark.rutland@arm.com; matt@codeblueprint.co.uk; Michal Simek
> <michals@xilinx.com>; mingo@kernel.org; mturquette@baylibre.com;
> robh+dt@kernel.org; sboyd@codeaurora.org; sudeep.holla@arm.com
> Cc: Rajan Vaja <RAJANV@xilinx.com>; linux-arm-kernel@lists.infradead.org;
> linux-kernel@vger.kernel.org; devicetree@vger.kernel.org; Jolly Shah
> <JOLLYS@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 <rajanv@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
next prev parent reply other threads:[~2018-07-17 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 17:40 [PATCH v9 00/10] drivers: Introduce firmware dnd clock river for ZynqMP core Jolly Shah
2018-06-20 17:40 ` [PATCH v9 01/10] dt-bindings: firmware: Add bindings for ZynqMP firmware Jolly Shah
2018-06-20 17:40 ` [PATCH v9 02/10] firmware: xilinx: Add Zynqmp firmware driver Jolly Shah
2018-06-20 17:40 ` [PATCH v9 03/10] firmware: xilinx: Add zynqmp IOCTL API for device control Jolly Shah
2018-06-20 17:40 ` [PATCH v9 04/10] firmware: xilinx: Add query data API Jolly Shah
2018-06-20 17:40 ` [PATCH v9 05/10] firmware: xilinx: Add clock APIs Jolly Shah
2018-07-09 5:31 ` Stephen Boyd
2018-06-20 17:40 ` [PATCH v9 06/10] firmware: xilinx: Add debugfs interface Jolly Shah
2018-06-20 17:40 ` [PATCH v9 07/10] firmware: xilinx: Add debugfs for IOCTL API Jolly Shah
2018-07-09 5:29 ` Stephen Boyd
2018-07-17 20:01 ` Jolly Shah [this message]
2018-06-20 17:40 ` [PATCH v9 08/10] firmware: xilinx: Add debugfs for query data API Jolly Shah
2018-06-20 17:40 ` [PATCH v9 09/10] dt-bindings: clock: Add bindings for ZynqMP clock driver Jolly Shah
2018-07-09 5:27 ` Stephen Boyd
2018-06-20 17:40 ` [PATCH v9 10/10] drivers: clk: Add " Jolly Shah
2018-07-09 5:26 ` Stephen Boyd
2018-07-17 20:09 ` Jolly Shah
2018-07-25 19:48 ` Stephen Boyd
2018-08-03 17:57 ` Jolly Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN1PR02MB3758432C38CC9580BC96182DB85C0@SN1PR02MB3758.namprd02.prod.outlook.com \
--to=jollys@xilinx.com \
--cc=RAJANV@xilinx.com \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=michals@xilinx.com \
--cc=mingo@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®