From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] remoteproc: dt: Provide bindings for ST's Remote Processor Controller driver
Date: Wed, 26 Aug 2015 10:59:22 -0500 [thread overview]
Message-ID: <55DDE25A.2050000@mentor.com> (raw)
In-Reply-To: <1440594483-29601-2-git-send-email-lee.jones@linaro.org>
On 08/26/2015 08:08 AM, Lee Jones wrote:
> diff --git a/Documentation/devicetree/bindings/remoteproc/st-rproc.txt b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> new file mode 100644
> index 0000000..6a933c1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> @@ -0,0 +1,38 @@
> +STMicroelectronics Remote Processor
> +-----------------------------------
> +
> +This binding provides support for adjunct processors found on ST SoCs.
> +
> +The remote processors can be controlled from the bootloader or the primary OS.
> +If the bootloader starts a remote processor processor the primary OS must detect
> +its state and act accordingly.
> +
> +The node name is significant, as it defines the name of the CPU and the name
> +of the firmware to load: "rproc-<name>-fw".
This business about the firmware name describes a behavior of Linux's
core remoteproc code and seems out of place in a binding document.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: ohad@wizery.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@stlinux.com
Subject: Re: [PATCH 1/4] remoteproc: dt: Provide bindings for ST's Remote Processor Controller driver
Date: Wed, 26 Aug 2015 10:59:22 -0500 [thread overview]
Message-ID: <55DDE25A.2050000@mentor.com> (raw)
In-Reply-To: <1440594483-29601-2-git-send-email-lee.jones@linaro.org>
On 08/26/2015 08:08 AM, Lee Jones wrote:
> diff --git a/Documentation/devicetree/bindings/remoteproc/st-rproc.txt b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> new file mode 100644
> index 0000000..6a933c1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> @@ -0,0 +1,38 @@
> +STMicroelectronics Remote Processor
> +-----------------------------------
> +
> +This binding provides support for adjunct processors found on ST SoCs.
> +
> +The remote processors can be controlled from the bootloader or the primary OS.
> +If the bootloader starts a remote processor processor the primary OS must detect
> +its state and act accordingly.
> +
> +The node name is significant, as it defines the name of the CPU and the name
> +of the firmware to load: "rproc-<name>-fw".
This business about the firmware name describes a behavior of Linux's
core remoteproc code and seems out of place in a binding document.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <ohad@wizery.com>,
<devicetree@vger.kernel.org>, <kernel@stlinux.com>
Subject: Re: [PATCH 1/4] remoteproc: dt: Provide bindings for ST's Remote Processor Controller driver
Date: Wed, 26 Aug 2015 10:59:22 -0500 [thread overview]
Message-ID: <55DDE25A.2050000@mentor.com> (raw)
In-Reply-To: <1440594483-29601-2-git-send-email-lee.jones@linaro.org>
On 08/26/2015 08:08 AM, Lee Jones wrote:
> diff --git a/Documentation/devicetree/bindings/remoteproc/st-rproc.txt b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> new file mode 100644
> index 0000000..6a933c1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/remoteproc/st-rproc.txt
> @@ -0,0 +1,38 @@
> +STMicroelectronics Remote Processor
> +-----------------------------------
> +
> +This binding provides support for adjunct processors found on ST SoCs.
> +
> +The remote processors can be controlled from the bootloader or the primary OS.
> +If the bootloader starts a remote processor processor the primary OS must detect
> +its state and act accordingly.
> +
> +The node name is significant, as it defines the name of the CPU and the name
> +of the firmware to load: "rproc-<name>-fw".
This business about the firmware name describes a behavior of Linux's
core remoteproc code and seems out of place in a binding document.
next prev parent reply other threads:[~2015-08-26 15:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 13:07 [PATCH 0/4] remoteproc: Add driver for STMicroelectronics platforms Lee Jones
2015-08-26 13:07 ` Lee Jones
2015-08-26 13:08 ` [PATCH 1/4] remoteproc: dt: Provide bindings for ST's Remote Processor Controller driver Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 15:59 ` Nathan Lynch [this message]
2015-08-26 15:59 ` Nathan Lynch
2015-08-26 15:59 ` Nathan Lynch
2015-08-26 16:40 ` Lee Jones
2015-08-26 16:40 ` Lee Jones
2015-08-26 16:40 ` Lee Jones
2015-08-26 13:08 ` [PATCH 2/4] remoteproc: Supply controller driver for ST's Remote Processors Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 17:07 ` Nathan Lynch
2015-08-26 17:07 ` Nathan Lynch
2015-08-26 17:07 ` Nathan Lynch
2015-08-27 6:45 ` Lee Jones
2015-08-27 6:45 ` Lee Jones
2015-08-27 6:45 ` Lee Jones
2015-08-26 13:08 ` [PATCH 3/4] ARM: STiH407: Add nodes for RemoteProc Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 13:08 ` [PATCH 4/4] remoteproc: debugfs: Add ability to boot remote processor using debugfs Lee Jones
2015-08-26 13:08 ` Lee Jones
2015-08-26 17:08 ` Nathan Lynch
2015-08-26 17:08 ` Nathan Lynch
2015-08-26 17:08 ` Nathan Lynch
2015-08-27 6:44 ` Lee Jones
2015-08-27 6:44 ` Lee Jones
2015-08-27 6:44 ` Lee Jones
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=55DDE25A.2050000@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.