linux-dev/drivers/soc/xilinx/Kconfig, branch masterLinux kernel development work - see feature brancheshttps://git.zx2c4.com/linux-dev/atom/drivers/soc/xilinx/Kconfig?h=master2021-12-03T15:08:46Zdrivers: soc: xilinx: add xilinx event management driver2021-12-03T15:08:46ZAbhyuday Godhasaraabhyuday.godhasara@xilinx.com2021-11-29T07:02:14Zurn:sha1:c7fdb2404f66131bc9c22e06f712717288826487
Xilinx event management driver provides an interface to subscribe or
unsubscribe for the event/callback supported by firmware. An agent can use
this driver to register for Error Event, Device Event and Suspend callback.
This driver only allows one agent per event to do registration. Driver will
return an error in case of multiple registration for the same event.
This driver gets notification from firmware through TF-A as SGI. During
initialization, event manager driver register handler for SGI used for
notification. It also provides SGI number info to TF-A by using
IOCTL_REGISTER_SGI call to TF-A.
After receiving notification from firmware, the driver makes an SMC call to
TF-A to get IPI data. From the IPI data provided by TF-A, event manager
identified the cause of event and forward that event/callback notification
to the respective subscribed driver. After this, in case of Error Event,
driver performs unregistration as firmware expecting from agent to do
re-registration if the agent wants to get notified on the second occurrence
of an error event.
Add new IOCTL id IOCTL_REGISTER_SGI = 25 which is used to register SGI on
TF-A.
Older firmware doesn't have all required support for event handling which
is required by the event manager driver. So add check for the register
notifier version in the event manager driver.
Xilinx event management driver provides support to subscribe for multiple
error events with the use of Event Mask in a single call of
xlnx_register_event(). Agent driver can provide 'Event' parameter value as
ORed of multiple event masks to register single callback for multiple
events. For example, to register callback for event=0x1 and event=0x2 for
the given node, agent can provide event=0x3 (0x1 | 0x2). It is not possible
to register multiple events for different nodes in a single registration
call.
Also provide support to receive multiple error events as in single
notification from firmware and then forward it to subscribed drivers via
registered callback one by one.
Acked-by: Michal Simek <michal.simek@xilinx.com>
Signed-off-by: Tejas Patel <tejas.patel@xilinx.com>
Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
Signed-off-by: Abhyuday Godhasara <abhyuday.godhasara@xilinx.com>
Link: https://lore.kernel.org/r/20211129070216.30253-2-abhyuday.godhasara@xilinx.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
clk: xilinx: move xlnx_vcu clock driver from soc2021-02-09T02:31:25ZMichael Tretterm.tretter@pengutronix.de2021-01-21T07:16:59Zurn:sha1:a2fe7baa27a46533005bdf3580ca04f0276c175f
The xlnx_vcu driver is actually a clock controller driver which provides
clocks that can be used by a driver for the encoder/decoder units. There
is no reason to keep this driver in soc. Move the driver to clk.
NOTE: The register mapping actually contains registers for AXI
performance monitoring, but these are not used by the driver.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
Acked-by: Michal Simek <michal.simek@xilinx.com>
Link: https://lore.kernel.org/r/20210121071659.1226489-16-m.tretter@pengutronix.de
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
soc: xilinx: vcu: register PLL as fixed rate clock2021-02-09T02:31:25ZMichael Tretterm.tretter@pengutronix.de2021-01-21T07:16:51Zurn:sha1:5a2b2e1341870df89bebc36caca52c00c5e808cf
Currently, xvcu_pll_set_rate configures the PLL to a clock rate that is
pre-calculated when probing the driver. To still make the clock
framework aware of the PLL and to allow to configure other clocks based
on the PLL rate, register the PLL as a fixed rate clock.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
Acked-by: Michal Simek <michal.simek@xilinx.com>
Link: https://lore.kernel.org/r/20210121071659.1226489-8-m.tretter@pengutronix.de
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
soc: xilinx: vcu: use vcu-settings syscon registers2020-12-09T18:36:33ZMichael Tretterm.tretter@pengutronix.de2020-11-09T13:48:17Zurn:sha1:30b79eb1f92ed5974885d374a4107c94e2dd3e03
Switch the "logicoreip" registers to the new xlnx,vcu-settings binding
to be able to read the settings if the settings are specified in a
separate device tree node that is shared with other drivers.
If the driver is not able to find a node with the new binding, fall back
to check for the logicore register bank to be backwards compatible.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Link: https://lore.kernel.org/r/20201109134818.4159342-4-m.tretter@pengutronix.de
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
drivers: soc: xilinx: fix firmware driver Kconfig dependency2020-04-15T06:15:55ZArnd Bergmannarnd@arndb.de2020-04-08T15:52:15Zurn:sha1:d0384eedcde21276ac51f57c641f875605024b32
The firmware driver is optional, but the power driver depends on it,
which needs to be reflected in Kconfig to avoid link errors:
aarch64-linux-ld: drivers/soc/xilinx/zynqmp_power.o: in function `zynqmp_pm_isr':
zynqmp_power.c:(.text+0x284): undefined reference to `zynqmp_pm_invoke_fn'
The firmware driver can probably be allowed for compile-testing as
well, so it's best to drop the dependency on the ZYNQ platform
here and allow building as long as the firmware code is built-in.
Fixes: ab272643d723 ("drivers: soc: xilinx: Add ZynqMP PM driver")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Link: https://lore.kernel.org/r/20200408155224.2070880-1-arnd@arndb.de
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
drivers: soc: xilinx: Use mailbox IPI callback2020-01-21T09:43:27ZTejas Pateltejas.patel@xilinx.com2019-12-02T10:38:51Zurn:sha1:ffdbae28d9d1af70b7d63ffd7827e9795cd8d0df
Add support for init suspend callback through mailbox IPI callback.
Signed-off-by: Tejas Patel <tejas.patel@xilinx.com>
Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
drivers: soc: xilinx: Add ZynqMP power domain driver2019-02-12T12:38:16ZJolly Shahjolly.shah@xilinx.com2019-02-01T22:08:50Zurn:sha1:e23d9c6d0d4912fab12cd2d56070b0a8199772f0
The zynqmp-genpd driver communicates the usage requirements
for logical power domains / devices to the platform FW.
FW is responsible for choosing appropriate power states,
taking Linux' usage information into account.
Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
Signed-off-by: Jolly Shah <jolly.shah@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
drivers: soc: xilinx: Add ZynqMP PM driver2019-02-12T12:36:24ZRajan Vajarajan.vaja@xilinx.com2019-01-29T20:38:21Zurn:sha1:ab272643d723f531b9caa8a4ac5f85fcd26840d2
Add ZynqMP PM driver. PM driver provides power management
support for ZynqMP.
Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
Signed-off-by: Jolly Shah <jolly.shah@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
soc: xilinx: Fix Kconfig alignment2018-01-16T14:50:21ZMichal Simekmichal.simek@xilinx.com2018-01-16T07:36:09Zurn:sha1:056b54eeaebbe567076fe9e824643fc330cba4d5
Tabs should be used for alignment instead of spaces.
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
soc: xilinx: xlnx_vcu: Depends on HAS_IOMEM for xlnx_vcu2018-01-16T07:34:30ZDhaval Shahdhaval.shah@xilinx.com2018-01-16T06:34:48Zurn:sha1:05015061222d10a3cb87e6046940abfe42114927
xlnx_vcu driver uses devm_ioremap_nocache, which is included
only when HAS_IOMEM is enabled.
drivers/soc/xilinx/xlnx_vcu.o: In function `xvcu_probe':
xlnx_vcu.c:(.text+0x116): undefined reference to `devm_ioremap_nocache'
xlnx_vcu.c:(.text+0x1ae): undefined reference to `devm_ioremap_nocache'
Signed-off-by: Dhaval Shah <dshah@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>