Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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 Cheers, ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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, ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
On Fri, 2014-11-07 at 03:38 -0600, Emil Medve wrote: 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 Thanks, I'm not sure how I missed that. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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? -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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? Cheers, ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan
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 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
