From: Scott Wood <scottwood@freescale•com>
To: Emil Medve <Emilian.Medve@Freescale•com>
Cc: mark.rutland@arm•com, devicetree@vger•kernel.org,
pawel.moll@arm•com, ijc+devicetree@hellion•org.uk,
Geoff.Thorpe@Freescale•com, corbet@lwn•net,
linux-doc@vger•kernel.org, linuxppc-dev@ozlabs•org,
robh+dt@kernel•org, galak@codeaurora•org,
grant.likely@linaro•org
Subject: Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
Date: Fri, 7 Nov 2014 01:34:25 -0600 [thread overview]
Message-ID: <1415345665.23458.428.camel@snotra.buserror.net> (raw)
In-Reply-To: <545C754C.9080700@Freescale.com>
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
> Hello Scott,
>
>
> On 11/06/2014 03:49 PM, Scott Wood wrote:
> > On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
> >> +Devices connected to a BMan instance via Direct Connect Portals (DCP) must link
> >> +to the respective BMan instance
> >> +
> >> +- fsl,bman
> >> + Usage: Required
> >> + Value type: <prop-encoded-array>
> >> + Description: List of phandle and DCP index pairs, to the BMan instance
> >> + to which this device is connected via the DCP
> >
> > Does software need the DCP index (though for QMan there do seem to be a
> > few registers associated with each DCP)? Where can I find that info in
> > the manual?
>
> The DCP index helps describe the topology of the devices connected to
> the B/QMan. One might be tempted to use some address to reference said
> DCP, unfortunately the pertinent registers/bits for said DCP(s) are not
> into a compact region. Look at the CCSR memory map for B/QMan
>
> In the QMan case things are marginally better. For each hardware portal
> there are a handful of (vaguely named *DCx*, *DCPx* or *DCP*) registers
> (configuration, performance monitoring and debugging). However, still
> registers and bits spread here and there
>
> In the BMan case things are a bit worse as the registers names are less
> friendly and still spread around
>
> Do you need specific names/offsets?
My question about the manual wasn't rhetorical -- I tried to find this
information and couldn't.
-Scott
next prev parent reply other threads:[~2014-11-07 7:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 15:18 [PATCH v3 0/4] dt/bindings: Introduce the FSL QorIQ DPAA B/QMan Emil Medve
2014-11-05 15:18 ` [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan Emil Medve
2014-11-06 21:49 ` Scott Wood
2014-11-07 7:31 ` Emil Medve
2014-11-07 7:34 ` Scott Wood [this message]
2014-11-07 8:14 ` Emil Medve
2014-11-07 8:19 ` Scott Wood
2014-11-07 9:38 ` Emil Medve
2014-11-07 16:49 ` Scott Wood
2014-11-05 15:18 ` [PATCH v3 2/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan portal(s) Emil Medve
2014-11-05 15:18 ` [PATCH v3 3/4] dt/bindings: Introduce the FSL QorIQ DPAA QMan Emil Medve
2014-11-05 15:18 ` [PATCH v3 4/4] dt/bindings: Introduce the FSL QorIQ DPAA QMan portal(s) Emil Medve
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=1415345665.23458.428.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=Emilian.Medve@Freescale$(echo .)com \
--cc=Geoff.Thorpe@Freescale$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=galak@codeaurora$(echo .)org \
--cc=grant.likely@linaro$(echo .)org \
--cc=ijc+devicetree@hellion$(echo .)org.uk \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mark.rutland@arm$(echo .)com \
--cc=pawel.moll@arm$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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