Shubhrajyoti Datta
c0178b8e24
dt-bindings: gpio: Add pmc gpio node to gpio-zynq
...
Add the pmc gpio node to the device tree.
Versal devices are the industry's first adaptive compute
acceleration platforms.
https://www.xilinx.com/support/documentation/data_sheets/ds950-versal-overview.pdf
On the Versal platform, we are using two customized GPIO controllers(IP)
which were used in Zynq/ZynqMp platform.
One of them present in the Platform Management Controller(PMC) block and
other in Processing System(PS) block.
In PMC_GPIO only Bank0,1,3 & 4 are enabled and in PS_GPIO only
Bank 0 & 3 are enabled.
You can find more details of GPIO IP in ZynqMP TRM General Purpose
I/O(Chapter-27).
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com >
Signed-off-by: Michal Simek <michal.simek@xilinx.com >
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com >
2020-06-24 12:11:31 +02:00
Shubhrajyoti Datta
3e1ad2b858
dt-bindings: gpio: Add binding for Versal gpio
...
Add binding for Versal binding.
Versal devices are the industry's first adaptive compute
acceleration platforms.
https://www.xilinx.com/support/documentation/data_sheets/ds950-versal-overview.pdf
On the Versal platform, we are using two customized GPIO controllers(IP)
which were used in Zynq/ZynqMp platform.
One of them present in the Platform Management Controller(PMC) block and
other in Processing System(PS) block.
In PMC_GPIO only Bank0,1,3 & 4 are enabled and in PS_GPIO only
Bank 0 & 3 are enabled.
You can find more details of GPIO IP in ZynqMP TRM General Purpose
I/O(Chapter-27).
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com >
Signed-off-by: Michal Simek <michal.simek@xilinx.com >
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com >
2020-06-24 12:10:37 +02:00
Rob Herring
791d3ef2e1
dt-bindings: remove 'interrupt-parent' from bindings
...
'interrupt-parent' is often documented as part of define bindings, but
it is really outside the scope of a device binding. It's never required
in a given node as it is often inherited from a parent node. Or it can
be implicit if a parent node is an 'interrupt-controller' node. So
remove it from all the binding files.
Cc: Mark Rutland <mark.rutland@arm.com >
Cc: devicetree@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org >
2018-07-25 14:09:39 -06:00
Soren Brinkmann
787dfbb294
gpio: zynq: Document interrupt-controller DT binding
...
HW and driver support the GPIO as interrupt-controller.
Document that in the DT binding.
Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com >
Signed-off-by: Linus Walleij <linus.walleij@linaro.org >
2015-10-27 17:01:28 +01:00
Anurag Kumar Vulisha
bdf7a4ae37
gpio: Added support to Zynq Ultrascale+ MPSoC
...
Added support to Zynq Ultrascale+ MPSoC on the existing zynq
gpio driver.
Signed-off-by: Anurag Kumar Vulisha <anuragku@xilinx.com >
Acked-by: Michal Simek <michal.simek@xilinx.com >
Signed-off-by: Linus Walleij <linus.walleij@linaro.org >
2015-06-10 09:44:17 +02:00
Harini Katakam
38ed0187d2
devicetree: Add Zynq GPIO devicetree bindings documentation
...
Add gpio-zynq bindings documentation.
Signed-off-by: Harini Katakam <harinik@xilinx.com >
Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com >
Signed-off-by: Linus Walleij <linus.walleij@linaro.org >
2014-07-10 11:13:44 +02:00
