From: Scott Wood <hidden> Date: 2014-11-07 07:34:25
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
Hello Scott,
On 11/06/2014 03:49 PM, Scott Wood wrote:
quoted
On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
quoted
+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
From: Emil Medve <hidden> Date: 2014-11-07 08:14:47
Hello Scott,
On 11/07/2014 01:34 AM, Scott Wood wrote:
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/06/2014 03:49 PM, Scott Wood wrote:
quoted
On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
quoted
+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
Cheers,
From: Scott Wood <hidden> Date: 2014-11-07 08:19:23
On Fri, 2014-11-07 at 02:14 -0600, Emil Medve wrote:
Hello Scott,
On 11/07/2014 01:34 AM, Scott Wood wrote:
quoted
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/06/2014 03:49 PM, Scott Wood wrote:
quoted
On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
quoted
+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.
-Scott
From: Emil Medve <hidden> Date: 2014-11-07 09:38:10
Hello Scott,
On 11/07/2014 02:19 AM, Scott Wood wrote:
On Fri, 2014-11-07 at 02:14 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/07/2014 01:34 AM, Scott Wood wrote:
quoted
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/06/2014 03:49 PM, Scott Wood wrote:
quoted
On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
quoted
+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,
From: Scott Wood <hidden> Date: 2014-11-07 16:49:54
On Fri, 2014-11-07 at 03:38 -0600, Emil Medve wrote:
Hello Scott,
On 11/07/2014 02:19 AM, Scott Wood wrote:
quoted
On Fri, 2014-11-07 at 02:14 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/07/2014 01:34 AM, Scott Wood wrote:
quoted
On Fri, 2014-11-07 at 01:31 -0600, Emil Medve wrote:
quoted
Hello Scott,
On 11/06/2014 03:49 PM, Scott Wood wrote:
quoted
On Wed, 2014-11-05 at 09:18 -0600, Emil Medve wrote:
quoted
+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