devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	John Williams
	<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Remoteproc device-tree node description proposal
Date: Wed, 27 Jun 2012 07:17:03 +0200	[thread overview]
Message-ID: <4FEA974F.9050908@monstr.eu> (raw)

Hi,

I would like to start discussion about remoteproc DTS node description.
Currently we have 2 remoteproc drivers for ARM zynq xilinx platform.
One is for the second ARM and one is for Microblaze in programmable logic
on the same device.

Below is current DTS node description which we are using for ARM and microblaze remoteproc.

ARM remoteproc
		test_zynq: zynq-remoteproc-test@0 {
			compatible = "xlnx,zynq_remoteproc";
			reg = < 0x0 0x8000000 >;
			interrupt-parent = <&ps7_scugic_0>;
			interrupts = < 0 37 0 0 38 0 0 39 0>;
			firmware = "test";
			ipino = <5>;
			vring0 = <2>;
			vring1 = <3>;
		} ;
NOTE:
"reg" - firmware allocates the part of ram - this is specification of that range
"interrupts" - which interrupts are used by firmware - static allocation
              - dynamic allocation via rpmsg won't be describe in DTS node
"firmware" - default firmware name which is loaded by request_firmware().
"ipino"(firmware to Linux), "vring0 vring1"(Linux to firmware) are IPI which are
used for rpmsg communication between Linux and firmware.


Microblaze remoteproc - rpmsg communication is not done yet.
		test_mb: mb-remoteproc-test@0 {
			compatible = "xlnx,mb_remoteproc";
			reg = < 0x0 0x10000000 >;
			firmware = "image.elf";
			reset-gpio = <&axi_gpio_0>;
			reset-gpio-pin = <0>;
		} ;

NOTE:
"reset-gpio" is link to IP which is able to start/stop/reset microblaze + pin number
             Ohad: what reset logic do you use?

Ohad: What properties are required by TI to describe firmware?
I would like to add together all requirements and create any formal remoteproc description.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

             reply	other threads:[~2012-06-27  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  5:17 Michal Simek [this message]
     [not found] ` <4FEA974F.9050908-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2012-06-28  7:54   ` Remoteproc device-tree node description proposal Ohad Ben-Cohen
     [not found]     ` <CAK=WgbbA2+oJARCEAgChct8rQ+s5=-cbR1esMPNekun3=ReGEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-29  5:01       ` Michal Simek

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=4FEA974F.9050908@monstr.eu \
    --to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
    --cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
    /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).