From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/5] cmd: remoteproc: Allow list command to print the probed devices
Date: Sun, 28 Jul 2019 17:46:40 -0400 [thread overview]
Message-ID: <20190728214640.GO20116@bill-the-cat> (raw)
In-Reply-To: <20190607135559.3671-3-lokeshvutla@ti.com>
On Fri, Jun 07, 2019 at 07:25:56PM +0530, Lokesh Vutla wrote:
> 'rproc list' is currently allowed only after probing all the
> available remoteproc devices. Given that 'rproc init' is updated
> to probe and initialize devices individually, allow the 'rproc list'
> command to print all probed devices at any point.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190728/58e5b171/attachment.sig>
next prev parent reply other threads:[~2019-07-28 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 13:55 [U-Boot] [PATCH v2 0/5] remoteproc: cleanup k3_rpoc driver Lokesh Vutla
2019-06-07 13:55 ` [U-Boot] [PATCH v2 1/5] cmd: remoteproc: Add support for initializing devices individually Lokesh Vutla
2019-07-28 21:46 ` Tom Rini
2019-06-07 13:55 ` [U-Boot] [PATCH v2 2/5] cmd: remoteproc: Allow list command to print the probed devices Lokesh Vutla
2019-07-28 21:46 ` Tom Rini [this message]
2019-06-07 13:55 ` [U-Boot] [PATCH v2 3/5] remoteproc: tisci: add TI-SCI processor control helper functions Lokesh Vutla
2019-07-28 21:46 ` Tom Rini
2019-06-07 13:55 ` [U-Boot] [PATCH v2 4/5] remoteproc: k3_rproc: Update the driver to use ti_sci_proc helpers Lokesh Vutla
2019-07-28 21:46 ` Tom Rini
2019-06-07 13:55 ` [U-Boot] [PATCH v2 5/5] remoteproc: k3_rproc: Rename to ti_k3_arm64_rproc Lokesh Vutla
2019-07-28 21:46 ` Tom Rini
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=20190728214640.GO20116@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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