From: Grant Likely <grant.likely@secretlab.ca>
To: Timur Tabi <timur@freescale.com>
Cc: wmb@firmworks.com, linuxppc-dev@ozlabs.org,
devicetree-discuss@lists.ozlabs.org, scottwood@freescale.com
Subject: Re: [PATCH] [v2] powerpc/fsl: add device tree binding for QE firmware
Date: Fri, 26 Mar 2010 13:45:38 -0600 [thread overview]
Message-ID: <fa686aa41003261245h52e151ceoa4f85e38055ae6a7@mail.gmail.com> (raw)
In-Reply-To: <1269632145-28462-1-git-send-email-timur@freescale.com>
On Fri, Mar 26, 2010 at 1:35 PM, Timur Tabi <timur@freescale.com> wrote:
> Define a binding for embedding a QE firmware blob into the device tree. =
=A0Also
> define a new property for the QE node that links to a firmware node.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> =A0.../powerpc/dts-bindings/fsl/cpm_qe/qe.txt =A0 =A0 =A0 =A0 | =A0 54 ++=
++++++++++++++++++
> =A01 files changed, 54 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt b/Docum=
entation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> index 6e37be1..865a2ef 100644
> --- a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> +++ b/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> @@ -21,6 +21,15 @@ Required properties:
> =A0- fsl,qe-num-snums: define how many serial number(SNUM) the QE can use=
for the
> =A0 threads.
>
> +Optional properties:
> +- fsl,firmware-phandle:
> + =A0 =A0Usage: required only if there is no fsl,qe-firmware child node
> + =A0 =A0Value type: <phandle>
> + =A0 =A0Definition: Points to a firmware node (see "QE Firmware Node" be=
low)
> + =A0 =A0 =A0 =A0that contains the firmware that should be uploaded for t=
his QE.
> + =A0 =A0 =A0 =A0The compatible property for the firmware node should say=
,
> + =A0 =A0 =A0 =A0"fsl,qe-firmware".
> +
> =A0Recommended properties
> =A0- brg-frequency : the internal clock source frequency for baud-rate
> =A0 generators in Hz.
> @@ -59,3 +68,48 @@ Example:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D <0 c000>;
> =A0 =A0 =A0 =A0};
> =A0 =A0 =A0};
> +
> +* QE Firmware Node
> +
> +This node defines a firmware binary that is embedded in the device tree,=
for
> +the purpose of passing the firmware from bootloader to the kernel, or fr=
om
> +the hypervisor to the guest.
> +
> +The firmware node itself contains the firmware binary contents, a compat=
ible
> +property, and any firmware-specific properties. =A0The node itself can b=
e located
> +anywhere, but should probably be placed inside a QE node.
The node must be a child of a QE node. A QE node can reference the
firmware from another QE node by using the fsl,firmware-phandle
property.
With that change; Acked-by: Grant Likely <grant.likely@secretlab.ca>
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Timur Tabi <timur@freescale.com>
Cc: wmb@firmworks.com, linuxppc-dev@ozlabs.org,
devicetree-discuss@lists.ozlabs.org, scottwood@freescale.com
Subject: Re: [PATCH] [v2] powerpc/fsl: add device tree binding for QE firmware
Date: Fri, 26 Mar 2010 13:45:38 -0600 [thread overview]
Message-ID: <fa686aa41003261245h52e151ceoa4f85e38055ae6a7@mail.gmail.com> (raw)
In-Reply-To: <1269632145-28462-1-git-send-email-timur@freescale.com>
On Fri, Mar 26, 2010 at 1:35 PM, Timur Tabi <timur@freescale.com> wrote:
> Define a binding for embedding a QE firmware blob into the device tree. Also
> define a new property for the QE node that links to a firmware node.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> .../powerpc/dts-bindings/fsl/cpm_qe/qe.txt | 54 ++++++++++++++++++++
> 1 files changed, 54 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt b/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> index 6e37be1..865a2ef 100644
> --- a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> +++ b/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
> @@ -21,6 +21,15 @@ Required properties:
> - fsl,qe-num-snums: define how many serial number(SNUM) the QE can use for the
> threads.
>
> +Optional properties:
> +- fsl,firmware-phandle:
> + Usage: required only if there is no fsl,qe-firmware child node
> + Value type: <phandle>
> + Definition: Points to a firmware node (see "QE Firmware Node" below)
> + that contains the firmware that should be uploaded for this QE.
> + The compatible property for the firmware node should say,
> + "fsl,qe-firmware".
> +
> Recommended properties
> - brg-frequency : the internal clock source frequency for baud-rate
> generators in Hz.
> @@ -59,3 +68,48 @@ Example:
> reg = <0 c000>;
> };
> };
> +
> +* QE Firmware Node
> +
> +This node defines a firmware binary that is embedded in the device tree, for
> +the purpose of passing the firmware from bootloader to the kernel, or from
> +the hypervisor to the guest.
> +
> +The firmware node itself contains the firmware binary contents, a compatible
> +property, and any firmware-specific properties. The node itself can be located
> +anywhere, but should probably be placed inside a QE node.
The node must be a child of a QE node. A QE node can reference the
firmware from another QE node by using the fsl,firmware-phandle
property.
With that change; Acked-by: Grant Likely <grant.likely@secretlab.ca>
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2010-03-26 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 19:35 [PATCH] [v2] powerpc/fsl: add device tree binding for QE firmware Timur Tabi
2010-03-26 19:35 ` Timur Tabi
2010-03-26 19:45 ` Grant Likely [this message]
2010-03-26 19:45 ` Grant Likely
2010-03-26 19:50 ` Timur Tabi
2010-03-26 19:53 ` Grant Likely
2010-03-26 19:53 ` Grant Likely
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=fa686aa41003261245h52e151ceoa4f85e38055ae6a7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=timur@freescale.com \
--cc=wmb@firmworks.com \
/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.