Thread (26 messages) 26 messages, 6 authors, 2018-09-24

[PATCH v11 03/11] firmware: xilinx: Add zynqmp IOCTL API for device control

From: Jolly Shah <hidden>
Date: 2018-09-10 19:17:59
Also in: linux-clk, linux-devicetree, lkml

Hi All,

Adding more clarification on top of what Michal said:
Here ioctl is not a system ioctl and just a eemi API like other interface APIs. It cannot be called from userspace. Only Linux drivers can use this API for defined ioctl operations. This API is meant for any platform specific operations which needs to be managed by firmware. Firmware will always validate the request for action being performed.
Debugfs interface is just for debugging during development. We can remove debugfs support for ioctl API if you suggest.

Thanks,
Jolly Shah

-----Original Message-----
From: Olof Johansson [mailto:olof at lixom.net]
Sent: Saturday, September 08, 2018 6:19 PM
To: Jolly Shah <redacted>
Cc: ard.biesheuvel at linaro.org; Ingo Molnar <mingo@kernel.org>; Greg Kroah-
Hartman [off-list ref]; matt at codeblueprint.co.uk; Sudeep
Holla [off-list ref]; hkallweit1 at gmail.com; Kees Cook
[off-list ref]; Dmitry Torokhov [off-list ref];
Michael Turquette [off-list ref]; Stephen Boyd
[off-list ref]; Michal Simek [off-list ref]; Rob Herring
[off-list ref]; Mark Rutland [off-list ref]; linux-clk
[off-list ref]; Rajan Vaja [off-list ref]; Linux ARM
Mailing List [off-list ref]; Linux Kernel Mailing List
[off-list ref]; DTML [off-list ref]; Jolly
Shah [off-list ref]
Subject: Re: [PATCH v11 03/11] firmware: xilinx: Add zynqmp IOCTL API for
device control

Hi,

On Fri, Aug 3, 2018 at 10:53 AM, Jolly Shah [off-list ref] wrote:
quoted
From: Rajan Vaja <redacted>

Add ZynqMP firmware IOCTL API to control and configure devices like
PLLs, SD, Gem, etc.

Signed-off-by: Rajan Vaja <redacted>
Signed-off-by: Jolly Shah <redacted>
This patch worries me somewhat. It's a transparent pass-through ioctl driver. Is
there a spec available for what the implemented IOCTLs are?

Should some of them be proper drivers instead of an opaque pass-through like
this? Could some of them have stability impact on the platform such that there
are security concerns and the list of arguments should somehow be sanitized?

What's the intended usecase anyway? Just a debug tool during development, or
something that you expect heavy use of by some userspace middleware?


-Olof
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help