From: Emil Medve <Emilian.Medve@Freescale.com>
To: Scott Wood <scottwood@Freescale.com>
Cc: galak@kernel.crashing.org, corbet@lwn.net, robh+dt@kernel.org,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
pawel.moll@arm.com, mark.rutland@arm.com,
grant.likely@linaro.org, Geoff.Thorpe@Freescale.com,
linuxppc-dev@ozlabs.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
Date: Fri, 7 Nov 2014 03:38:10 -0600 [thread overview]
Message-ID: <545C9302.50703@Freescale.com> (raw)
In-Reply-To: <1415348363.23458.432.camel@snotra.buserror.net>
Hello Scott,
On 11/07/2014 02:19 AM, Scott Wood wrote:
> On Fri, 2014-11-07 at 02:14 -0600, Emil Medve wrote:
>> Hello Scott,
>>
>>
>> On 11/07/2014 01:34 AM, Scott Wood wrote:
>>> 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.
>>
>> I get that. As I said, the registers/bits are spread around in the CCSR
>> space of each block and not named excessively friendly. As such I hinted
>> for some search patterns to make it easier to find them. In order to
>> progress the review I'm willing to prepare a list. Just let me know
>
> Could you point me to the section of the manual where this information
> is -- friendly or otherwise? I saw the QMan direct connect portal
> registers. I didn't see how to tell which <i> in DCPi_xxx goes with
> which device.
For QMan look into section '6.3.10 Direct Connect Portals (DCPs)'. The
BMan DCP assignment is the same
Cheers,
next prev parent reply other threads:[~2014-11-07 9:38 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
[not found] ` <545C754C.9080700-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2014-11-07 7:34 ` Scott Wood
2014-11-07 8:14 ` Emil Medve
2014-11-07 8:19 ` Scott Wood
2014-11-07 9:38 ` Emil Medve [this message]
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=545C9302.50703@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=Geoff.Thorpe@Freescale.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=scottwood@Freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).