From patchwork Mon Feb 23 11:37:25 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michal Simek X-Patchwork-Id: 442424 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id DEC3714012C for ; Mon, 23 Feb 2015 22:38:05 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752318AbbBWLhg (ORCPT ); Mon, 23 Feb 2015 06:37:36 -0500 Received: from mail-ob0-f171.google.com ([209.85.214.171]:36239 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752194AbbBWLhf (ORCPT ); Mon, 23 Feb 2015 06:37:35 -0500 Received: by mail-ob0-f171.google.com with SMTP id gq1so35840049obb.2 for ; Mon, 23 Feb 2015 03:37:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id; bh=FkH5Mqbs7kewz/MroyDlMj4tM6/39FqnE9a0Nox2xBs=; b=OP5qQC3Y7PPO+r5QPKMFgQME3OUQalmuCOKS0fr4MwWzNyeyiUra36zjLSwBelVbGQ KZPMMSTjmkg7eRwElw7bB9faULkL236M86PqO3uGAIcvraPoFyvKPIpKxkaZWHskWkCN 1WmwsOgThXfGvTXYinbDFPGu9AIOz0EgIQKi7Qdtm4n7jQNll2M+dJY3ojtpHQ5phcSE WRAF2pRRfXqsivExcIAnW8BxV1yUKfEE+5B3bx/t93TbZRDeKi6ayOUgG7XlWQeaVHWv Q07Z7fzclVPgk63qItOl8UW1EIfEFUmpJQUkClen6JdzxgipiXgSVStcfucSHwDi0vYv ZAjw== X-Gm-Message-State: ALoCoQmPp3vann76J53Xxuo/f8ms/5akR2GPc5e0ytxgXfjFdQbqWOrwBc+zuJxQPdohE3gyQN2M X-Received: by 10.182.22.137 with SMTP id d9mr7179022obf.67.1424691455110; Mon, 23 Feb 2015 03:37:35 -0800 (PST) Received: from localhost (nat-35.starnet.cz. [178.255.168.35]) by mx.google.com with ESMTPSA id p6sm21392315oib.13.2015.02.23.03.37.33 (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Mon, 23 Feb 2015 03:37:34 -0800 (PST) From: Michal Simek To: linux-kernel@vger.kernel.org, monstr@monstr.eu Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org Subject: [PATCH v2 1/2] remoteproc: microblaze: Document device tree bindings Date: Mon, 23 Feb 2015 12:37:25 +0100 Message-Id: <78fba33b1c38941a03996c8fe5bd3d3613314d56.1424688478.git.michal.simek@xilinx.com> X-Mailer: git-send-email 1.8.2.3 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Add device tree binding documentation for the Microblaze remoteproc on Xilinx Zynq. Signed-off-by: Michal Simek --- Changes in v2: - Applied changed reported by Mark Rutland here https://lkml.org/lkml/2015/1/19/198 .../bindings/remoteproc/mb_remoteproc.txt | 45 ++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/mb_remoteproc.txt diff --git a/Documentation/devicetree/bindings/remoteproc/mb_remoteproc.txt b/Documentation/devicetree/bindings/remoteproc/mb_remoteproc.txt new file mode 100644 index 000000000000..3a454f01f5f0 --- /dev/null +++ b/Documentation/devicetree/bindings/remoteproc/mb_remoteproc.txt @@ -0,0 +1,45 @@ +Xilinx ARM-Microblaze remoteproc driver + +A Microblaze is added to the programmable logic on Xilinx Zynq. +The Microblaze is connected with PS block via axi bus connected to PS HP port +to ensure access to PS DDR. +Communication channels are done via soft GPIO IP connected to PS block +and to Microblaze. There are also 2 gpio control signals reset and debug +which are used for resetting Microblaze. + +Required properties: +- compatible : Should be "xlnx,mb-remoteproc" +- reg : Address and length of the ddr address space +- bram: Phandle to bram controller which can access Microblaze BRAM +- bram-firmware : Microblaze BRAM bootloader name +- firmware : Default firmware name which can be override by + "firmware" module parameter +- reset-gpio : Gpio phandle which reset Microblaze remoteproc +- debug-gpio : Gpio phandle which setup Microblaze to debug state +- ipino-gpio : Gpio phandle for Microblaze to ARM communication +- vring0-gpio : Gpio phandle for ARM to Microblaze communication vring 0 +- vring1-gpio : Gpio phandle for ARM to Microblaze communication vring 1 + +Microblaze SoC can be also connected to the PS block via an axi bus. +That's why there is the option to allocate interrupts for Microblaze use only. +The driver will allocate interrupts to itself and Microblaze sw has to ensure +that interrupts are properly enabled and handled by Microblaze interrupt +controller. + +Optional properties: + - interrupts : Interrupt mapping for remoteproc + - interrupt-parent : Phandle for the interrupt controller + +Example: +mb_remoteproc@800000 { + compatible = "xlnx,mb-remoteproc"; + reg = < 0x8000000 0x8000000 >; + bram = <&axi_bram_ctrl_0>; + bram-firmware = "mb.bin"; + firmware = "image.elf"; + reset-gpio = <&zynq_gpio_reset 1 0>; + debug-gpio = <&zynq_gpio_reset 0 0>; + ipino-gpio = <&zynq_gpio_vring 0 0>; + vring0-gpio = <&zynq_gpio_vring 1 0>; + vring1-gpio = <&zynq_gpio_vring 2 0>; +};