From: Scott Wood <scottwood@freescale.com>
To: Gala Kumar-B11780 <B11780@freescale.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Wood Scott-B07421 <B07421@freescale.com>,
Timur Tabi <timur@tabi.org>,
Yoder Stuart-B08248 <B08248@freescale.com>
Subject: Re: [PATCH 2/2] powerpc/85xx: describe the PAMU topology in the device tree
Date: Wed, 23 Jan 2013 16:15:19 -0600 [thread overview]
Message-ID: <1358979319.9710.13@snotra> (raw)
In-Reply-To: <CF1EE7AED478CD48A05574C8E2DA142D6DA7A5@039-SN1MPN1-005.039d.mgd.msft.net> (from B11780@freescale.com on Wed Jan 23 11:27:29 2013)
On 01/23/2013 11:27:29 AM, Gala Kumar-B11780 wrote:
>=20
> On Jan 17, 2013, at 4:34 PM, Timur Tabi wrote:
>=20
> > From: Timur Tabi <timur@freescale.com>
> >
> > The PAMU caches use the LIODNs to determine which cache lines hold =20
> the
> > entries for the corresponding LIODs. The LIODNs must therefore be
> > carefully assigned to avoid cache thrashing -- two active LIODs with
> > LIODNs that put them in the same cache line.
> >
> > Currently, LIODNs are statically assigned by U-Boot, but this has
> > limitations. LIODNs are assigned even for devices that may be =20
> disabled
> > or unused by the kernel. Static assignments also do not allow for =20
> device
> > drivers which may know which LIODs can be used simultaneously. In
> > other words, we really should assign LIODNs dynamically in Linux.
> >
> > To do that, we need to describe the PAMU device and cache =20
> topologies in
> > the device trees.
> >
> > Signed-off-by: Timur Tabi <timur@freescale.com>
> > ---
> > .../devicetree/bindings/powerpc/fsl/guts.txt | 14 ++-
> > .../devicetree/bindings/powerpc/fsl/pamu.txt | 142 =20
> ++++++++++++++++++++
> > arch/powerpc/boot/dts/fsl/p2041si-post.dtsi | 87 =20
> +++++++++++--
> > arch/powerpc/boot/dts/fsl/p3041si-post.dtsi | 87 =20
> +++++++++++--
> > arch/powerpc/boot/dts/fsl/p4080si-post.dtsi | 68 +++++++++-
> > arch/powerpc/boot/dts/fsl/p5020si-post.dtsi | 92 =20
> +++++++++++--
> > arch/powerpc/boot/dts/fsl/p5040si-post.dtsi | 92 =20
> +++++++++++--
> > 7 files changed, 533 insertions(+), 49 deletions(-)
> > create mode 100644 =20
> Documentation/devicetree/bindings/powerpc/fsl/pamu.txt
>=20
> Scott, Stuart, does this have your guys Ack?
ACK
-Scott=
next prev parent reply other threads:[~2013-01-23 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 22:34 [PATCH 1/2] powerpc/85xx: fix various PCI node compatible strings Timur Tabi
2013-01-17 22:34 ` [PATCH 2/2] powerpc/85xx: describe the PAMU topology in the device tree Timur Tabi
2013-01-23 17:27 ` Gala Kumar-B11780
2013-01-23 22:15 ` Scott Wood [this message]
2013-01-24 22:57 ` Yoder Stuart-B08248
2013-02-12 20:01 ` Gala Kumar-B11780
2013-02-12 20:01 ` [PATCH 1/2] powerpc/85xx: fix various PCI node compatible strings Gala Kumar-B11780
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=1358979319.9710.13@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B11780@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@tabi.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.