From: Randy Dunlap <rdunlap@infradead.org>
To: Jolly Shah <jolly.shah@xilinx.com>,
ard.biesheuvel@linaro.org, mingo@kernel.org,
gregkh@linuxfoundation.org, matt@codeblueprint.co.uk,
sudeep.holla@arm.com, hkallweit1@gmail.com,
keescook@chromium.org, dmitry.torokhov@gmail.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
michal.simek@xilinx.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux-clk@vger.kernel.org
Cc: 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 v8 03/10] firmware: xilinx: Add zynqmp IOCTL API for device control
Date: Thu, 14 Jun 2018 13:45:20 -0700 [thread overview]
Message-ID: <3044c2b9-2268-dfcb-2d45-0117c6f91a8d@infradead.org> (raw)
In-Reply-To: <1529000862-11510-4-git-send-email-jollys@xilinx.com>
On 06/14/2018 11:27 AM, Jolly Shah wrote:
> From: Rajan Vaja <rajanv@xilinx.com>
>
> Add ZynqMP firmware IOCTL API to control and configure
> devices like PLLs, SD, Gem, etc.
>
> Signed-off-by: Rajan Vaja <rajanv@xilinx.com>
> Signed-off-by: Jolly Shah <jollys@xilinx.com>
> ---
> drivers/firmware/xilinx/zynqmp.c | 20 ++++++++++++++++++++
> include/linux/firmware/xlnx-zynqmp.h | 2 ++
> 2 files changed, 22 insertions(+)
Hi,
Does this driver claim (implement) some specific ioctl code or ID?
If so, its ioctl numbers should be documented in Documentation/ioctl/ioctl-number.txt.
thanks,
--
~Randy
next prev parent reply other threads:[~2018-06-14 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:27 [PATCH v8 00/10] drivers: Introduce firmware dnd clock river for ZynqMP core Jolly Shah
2018-06-14 18:27 ` [PATCH v8 01/10] dt-bindings: firmware: Add bindings for ZynqMP firmware Jolly Shah
2018-06-14 18:27 ` [PATCH v8 02/10] firmware: xilinx: Add Zynqmp firmware driver Jolly Shah
2018-06-14 20:40 ` Randy Dunlap
2018-06-14 18:27 ` [PATCH v8 03/10] firmware: xilinx: Add zynqmp IOCTL API for device control Jolly Shah
2018-06-14 20:45 ` Randy Dunlap [this message]
2018-06-15 16:45 ` Jolly Shah
2018-06-14 18:27 ` [PATCH v8 04/10] firmware: xilinx: Add query data API Jolly Shah
2018-06-14 18:27 ` [PATCH v8 05/10] firmware: xilinx: Add clock APIs Jolly Shah
2018-06-14 18:27 ` [PATCH v8 06/10] firmware: xilinx: Add debugfs interface Jolly Shah
2018-06-14 18:27 ` [PATCH v8 07/10] firmware: xilinx: Add debugfs for IOCTL API Jolly Shah
2018-06-14 18:27 ` [PATCH v8 08/10] firmware: xilinx: Add debugfs for query data API Jolly Shah
2018-06-14 18:27 ` [PATCH v8 09/10] dt-bindings: clock: Add bindings for ZynqMP clock driver Jolly Shah
2018-06-14 18:27 ` [PATCH v8 10/10] drivers: clk: Add " 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=3044c2b9-2268-dfcb-2d45-0117c6f91a8d@infradead.org \
--to=rdunlap@infradead.org \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=jolly.shah@xilinx.com \
--cc=jollys@xilinx.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=michal.simek@xilinx.com \
--cc=mingo@kernel.org \
--cc=mturquette@baylibre.com \
--cc=rajanv@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).