From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Madalin Bucur <madalin.bucur-3arQi8VN3Tc@public.gmane.org>
Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org,
oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] dt-bindings: qman: Remove pool channel node
Date: Wed, 4 Jan 2017 08:52:21 -0600 [thread overview]
Message-ID: <20170104145221.dl472qqys6bz3jfa@rob-hp-laptop> (raw)
In-Reply-To: <1483527829-8369-1-git-send-email-madalin.bucur-3arQi8VN3Tc@public.gmane.org>
On Wed, Jan 04, 2017 at 01:03:49PM +0200, Madalin Bucur wrote:
> From: Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
>
> No device tree has these, nor does any driver look for them.
>
> Signed-off-by: Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
> ---
> .../devicetree/bindings/soc/fsl/qman-portals.txt | 20 --------------------
> 1 file changed, 20 deletions(-)
Applied, thanks.
Rob
>
> diff --git a/Documentation/devicetree/bindings/soc/fsl/qman-portals.txt b/Documentation/devicetree/bindings/soc/fsl/qman-portals.txt
> index 47e46cc..5a34f3a 100644
> --- a/Documentation/devicetree/bindings/soc/fsl/qman-portals.txt
> +++ b/Documentation/devicetree/bindings/soc/fsl/qman-portals.txt
> @@ -5,7 +5,6 @@ Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
> CONTENTS
>
> - QMan Portal
> - - QMan Pool Channel
> - Example
>
> QMan Portal Node
> @@ -82,25 +81,6 @@ These subnodes should have the following properties:
> Definition: The phandle to the particular hardware device that this
> portal is connected to.
>
> -DPAA QMan Pool Channel Nodes
> -
> -Pool Channels are defined with the following properties.
> -
> -PROPERTIES
> -
> -- compatible
> - Usage: Required
> - Value type: <stringlist>
> - Definition: Must include "fsl,qman-pool-channel"
> - May include "fsl,<SoC>-qman-pool-channel"
> -
> -- fsl,qman-channel-id
> - Usage: Required
> - Value type: <u32>
> - Definition: The hardware index of the channel. This can also be
> - determined by dividing any of the channel's 8 work queue
> - IDs by 8
> -
> EXAMPLE
>
> The example below shows a (P4080) QMan portals container/bus node with two portals
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-04 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 11:03 [PATCH] dt-bindings: qman: Remove pool channel node Madalin Bucur
[not found] ` <1483527829-8369-1-git-send-email-madalin.bucur-3arQi8VN3Tc@public.gmane.org>
2017-01-04 14:52 ` Rob Herring [this message]
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=20170104145221.dl472qqys6bz3jfa@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=madalin.bucur-3arQi8VN3Tc@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=oss-fOR+EgIDQEHk1uMJSBkQmQ@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