[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbYSrzTKW-QME4-r6XhVAQL0b6iWyus632KZOpfpTPgwWg@mail.gmail.com>
Date: Tue, 22 May 2012 11:02:14 +0300
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Michal Simek <monstr@...str.eu>
Cc: linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Brian Swetland <swetland@...gle.com>,
Iliyan Malchev <malchev@...gle.com>,
Arnd Bergmann <arnd@...db.de>,
Grant Likely <grant.likely@...retlab.ca>,
Rusty Russell <rusty@...tcorp.com.au>,
Mark Grosen <mgrosen@...com>,
John Williams <john.williams@...alogix.com>,
Loic PALLARDY <loic.pallardy@...ricsson.com>,
Ludovic BARRE <ludovic.barre@...ricsson.com>,
Omar Ramirez Luna <omar.luna@...aro.org>,
Guzman Lugo Fernando <fernando.lugo@...com>,
Anna Suman <s-anna@...com>, Clark Rob <rob@...com>,
Stephen Boyd <sboyd@...eaurora.org>,
Saravana Kannan <skannan@...eaurora.org>,
David Brown <davidb@...eaurora.org>,
Kieran Bingham <kieranbingham@...il.com>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH 1/7] remoteproc: resource table overhaul
Hi Michal,
On Tue, May 22, 2012 at 8:51 AM, Michal Simek <monstr@...str.eu> wrote:
> Simple enabling RSC_VDEV in rproc_handle_rsc doesn't work.
Sure - you'll need to actually plug the vrings allocation code there,
too (i.e. this requires some coding, it's not a 1-liner).
> BTW: I am using kernel modules and there is no dependency for
> virtio_rpmsg_bus in remoteproc module
> in sense if you load remoteproc module you also need to load
> virtio_rpmsg_bus to get firmware to work.
This is expected: remoteproc only provides means for booting and
controlling remote processors and it doesn't boot them upfront.
To actually boot a remote processor, and do something useful with it,
one needs to load a module which utilizes remoteproc's API (e.g.
virtio_rpmsg_bus, but YMMV).
> ~ # lsmod
> ~ # modprobe zynq_remoteproc
> zynq_remoteproc: Unknown symbol rproc_register (err 0)
> zynq_remoteproc: Unknown symbol rproc_alloc (err 0)
> zynq_remoteproc: Unknown symbol rproc_vq_interrupt (err 0)
> zynq_remoteproc: Unknown symbol rproc_free (err 0)
> zynq_remoteproc: Unknown symbol rproc_unregister (err 0)
We don't have these errors - have you tried looking into them ?
Btw do you plan on submitting the code for zynq_remoteproc ?
> Can you see the same behavior on omap?
Except the "Unknown symbol" errors, everything else looks good.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists