From: Scott Wood <scottwood@freescale.com>
To: Pledge Roy-R01356 <roy.pledge@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Bucur Madalin-Cristian-B32716" <madalin.bucur@freescale.com>,
Wang Haiying-R54964 <Haiying.Wang@freescale.com>
Subject: Re: [PATCH 1/2] powerpc/qman: Change fsl,qman-channel-id to cell-index
Date: Thu, 20 Aug 2015 11:53:48 -0500 [thread overview]
Message-ID: <20150820165348.GA4881@home.buserror.net> (raw)
In-Reply-To: <BN3PR0301MB12675C1EC30FBC1E823161908C660@BN3PR0301MB1267.namprd03.prod.outlook.com>
On Thu, Aug 20, 2015 at 09:52:46AM -0500, Pledge Roy-R01356 wrote:
> I guess my point isn't getting through - channel-id and cell-index are
> too independent concepts that are coincidentally the same. Cell-index
> is only used by u-boot and is used to determine the portal number. It
> is absolutely possible that we produce and SoC where portal number 0
> has channel 0x1000. We've changed these things in the past as well -
> this is why we introduced the channel-id property. This is also
> consistent with other blocks (FMan, PME, DCE) that have channels
> associated with them.
>
> The cell-index is useless - the portal ID can be derived from the
> portal address. The fact that you're unwilling to remove cell-index
> doesn't mean that channel-id is redundant and should be removed.
I guess my point isn't getting through. Any concept that cell-index
represented that was not identical to channel id is dead and gone, as is
the concept of "portal number". Every time you see cell-index just
pretend you are seeing fsl,qman-channel-id.
cell-index is *not* defined as anything to do with the portal address.
> > > The only thing cell-index indicates is the offset of the portal in the
> > > QMan address space.
> >
> > cell-index has been redefined to not mean that at all. It now only means
> > channel ID. We can do this because the value happens to be the same for all
> > existing SoCs (and we should be sure to avoid putting things into the SDK for
> > the aforementioned ARM chips that are contrary to the new definition).
> >
>
> U-boot doesn't dictate the HW architecture and shouldn't - you're
> trying very hard not to admit you changed something you didn't fully
> understand and actually making the system harder to deal with. At no
> point in time have we ever assumed portal ID would equal channel id.
cell-index does not mean "portal ID".
> With your logic u-boot is broken because it is using channel ID to
> index into an array that is per portal not per channel. We shouldn't
> have removed channel-id in the first place - trying to redefine that
> portals = channels is just plain incorrect.
That's not what happened.
> I'm not sure how else to get through to you on this, your base
> assumption is wrong.
Likewise.
-Scott
prev parent reply other threads:[~2015-08-20 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 22:53 [PATCH 1/2] powerpc/qman: Change fsl,qman-channel-id to cell-index Scott Wood
2015-04-17 22:53 ` [PATCH 2/2] powerpc/mpc85xx: Add FSL QorIQ DPAA QMan support to device tree(s) Scott Wood
2015-05-05 16:04 ` [PATCH 1/2] powerpc/qman: Change fsl,qman-channel-id to cell-index Roy Pledge
2015-05-05 20:45 ` Scott Wood
2015-05-12 21:19 ` Roy Pledge
2015-05-12 22:46 ` Scott Wood
2015-08-19 20:52 ` Roy Pledge
2015-08-19 21:30 ` Scott Wood
2015-08-20 14:52 ` Roy Pledge
2015-08-20 16:53 ` Scott Wood [this message]
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=20150820165348.GA4881@home.buserror.net \
--to=scottwood@freescale.com \
--cc=Haiying.Wang@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=roy.pledge@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).