public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port
Date: Wed, 12 Sep 2007 15:20:25 +0200	[thread overview]
Message-ID: <6b92503d73565f8add983e64ad5d5d39@kernel.crashing.org> (raw)
In-Reply-To: <1DE5CB62-9EF1-42BA-93F3-CE15DD94F5DD@kernel.crashing.org>

>>> +		l2-cache-controller@20000 {
>>> +			compatible = "fsl,8572-l2-cache-controller";
>>> +			reg = <20000 1000>;
>>> +			cache-line-size = <20>;	// 32 bytes
>>> +			cache-size = <80000>;	// L2, 512K
>>> +			interrupt-parent = <&mpic>;
>>> +			interrupts = <10 2>;
>>> +		};
>>
>> Should this node be referenced by an l2-cache property in the cpu
>> node?
>
> No, its a front side cache.

What is a "front side cache"?  What exactly does it cache?  If it's
a cache for one CPU only, that fact should be shown in the device
tree somehow.

>>> +			device_type = "pci";
>>> +			#interrupt-cells = <1>;
>>> +			#size-cells = <2>;
>>> +			#address-cells = <3>;
>>> +			reg = <8000 1000>;
>>> +			bus-range = <0 ff>;
>>> +			ranges = <02000000 0 80000000 80000000 0 20000000
>>> +				  01000000 0 00000000 ffc00000 0 00010000>;
>>
>> No prefetchable mem space?
>
> we haven't normally provided prefetch on 85xx/86xx.. will deal with
> this later.

If you don't set up prefetchable memory regions on the PCI from
the firmware, this code is fine, sure.  It would be a good plan
to do map all BARs that say they are prefetchable in some
prefetchable PCI window, it gives a nice speed boost, even when
the kernel accesses it as simple non-cacheable space: the PCI
bridges in between can streamline loads from these areas.

In any case, the device tree should be in synch with how the
firmware set up the PCI hardware, and it seems that's what you
have now, so all is fine.


Segher

  reply	other threads:[~2007-09-13  2:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  6:29 [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port Kumar Gala
2007-09-11 14:17 ` Scott Wood
2007-09-11 15:58   ` Kumar Gala
2007-09-12 13:20     ` Segher Boessenkool [this message]
2007-09-13  3:27       ` Kumar Gala
2007-09-13 16:53         ` Segher Boessenkool
2007-09-13 21:23           ` Kumar Gala
2007-09-11 14:18 ` Olof Johansson
2007-09-11 15:50   ` Kumar Gala
2007-09-11 15:55     ` Olof Johansson
2007-09-11 16:00       ` Kumar Gala
2007-09-11 17:15         ` Olof Johansson
2007-09-11 17:21           ` Scott Wood
2007-09-11 17:33             ` Olof Johansson
2007-09-11 17:48               ` Scott Wood
2007-09-11 17:59                 ` Kumar Gala
2007-09-12  3:00                   ` David Gibson
2007-09-12  3:35                     ` Kumar Gala
2007-09-12  3:37                       ` David Gibson
2007-09-12  3:37                       ` Olof Johansson
2007-09-12 13:20             ` Segher Boessenkool

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=6b92503d73565f8add983e64ad5d5d39@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox