<fsl,qman-channel-id> in dts file

<fsl,qman-channel-id> in dts file

[Tony]

[-- Attachment #1: Type: text/plain, Size: 159 bytes --]

How's the fsl,qman-channel-id value different for different targets ?
Is there any document on how this value is achieved ?

Or can it be any value ???

Alan.

[-- Attachment #2: Type: text/html, Size: 226 bytes --]

Re: <fsl,qman-channel-id> in dts file

[Emil Medve]

Hello Tony,


On 06/09/2014 06:43 AM, Tony wrote:
> How's the fsl,qman-channel-id value different for different targets ?

Channel ids are assigned in hardware

> Is there any document on how this value is achieved ?

They are described in the RM of each SoC and in the DPAA RM

> Or can it be any value ???

Nope. It must be the right value or frames will end up in the wrong
portal or worse


Cheers,

Re: <fsl,qman-channel-id> in dts file

[Tony]

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Thank Emil.

Where can i find the details about a 'diff' of qman revisions ? The code i
ported doesnt support latest qman revision (REV3). Can i still work on qman
REV1.1 for all the latest targets ? (read t-series)

Regards


On Mon, Jun 9, 2014 at 8:32 PM, Emil Medve <Emilian.Medve@freescale.com>
wrote:

> Hello Tony,
>
>
> On 06/09/2014 06:43 AM, Tony wrote:
> > How's the fsl,qman-channel-id value different for different targets ?
>
> Channel ids are assigned in hardware
>
> > Is there any document on how this value is achieved ?
>
> They are described in the RM of each SoC and in the DPAA RM
>
> > Or can it be any value ???
>
> Nope. It must be the right value or frames will end up in the wrong
> portal or worse
>
>
> Cheers,
>

[-- Attachment #2: Type: text/html, Size: 1247 bytes --]

Re: <fsl,qman-channel-id> in dts file

[Emil Medve]

Hello Tony,


On 06/09/2014 10:28 AM, Tony wrote:
> Thank Emil.
> 
> Where can i find the details about a 'diff' of qman revisions ?

Let me look if someody bothered to write an AN about this

> The code
> i ported doesnt support latest qman revision (REV3).

Ported from what (I suspect) SDK release? v1.5 should already have
support for the latest xMan revision(s)

> Can i still work on
> qman REV1.1 for all the latest targets ? (read t-series)

I'm inclined to say yes (of course the new features will not be
available), but I need to have a look at the code to see with what
limitations


Cheers,


> Regards
> 
> 
> On Mon, Jun 9, 2014 at 8:32 PM, Emil Medve <Emilian.Medve@freescale.com
> <mailto:Emilian.Medve@freescale.com>> wrote:
> 
>     Hello Tony,
> 
> 
>     On 06/09/2014 06:43 AM, Tony wrote:
>     > How's the fsl,qman-channel-id value different for different targets ?
> 
>     Channel ids are assigned in hardware
> 
>     > Is there any document on how this value is achieved ?
> 
>     They are described in the RM of each SoC and in the DPAA RM
> 
>     > Or can it be any value ???
> 
>     Nope. It must be the right value or frames will end up in the wrong
>     portal or worse
> 
> 
>     Cheers,
> 
> 
> 
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev