Re: [PATCH v3] powerpc/fsl: Added binding for Freescale CoreNet coherency fabric (CCF)

On May 5, 2014, at 10:58 AM, Diana Craciun [off-list ref] =
wrote:

From: Diana Craciun <redacted>
=20
The CoreNet coherency fabric is a fabric-oriented, conectivity
infrastructure that enables the implementation of coherent, multicore
systems. The CCF acts as a central interconnect for cores,
platform-level caches, memory subsystem, peripheral devices and I/O =

host

bridges in the system.
=20
Signed-off-by: Diana Craciun <redacted>
---
v3:
	- added port ID mapping
	- removed fsl,corenetx-cf
=20
.../devicetree/bindings/powerpc/fsl/ccf.txt        | 42 =

++++++++++++++++++++++

.../devicetree/bindings/powerpc/fsl/cpus.txt       |  8 +++++
.../devicetree/bindings/powerpc/fsl/pamu.txt       |  8 +++++
3 files changed, 58 insertions(+)
create mode 100644 =

Documentation/devicetree/bindings/powerpc/fsl/ccf.txt

[snip]

category

	name with all uppercase letters converted to lowercase, =

indicates that

	the category is supported by the implementation.
+
+	- fsl,portid-mapping : <u32>
+	The Coherency Subdomain ID Port Mapping Registers and Snoop ID =

Port Mapping

+	registers which are part of the CoreNet Coherency fabric (CCF) =

provide a

+	CoreNet Coherency Subdomain ID/CoreNet Snoop ID to cpu mapping =

functions.

+	Certain bits from these registers should be set if the =

coresponding CPU

+	should be snooped. This property defines a bitmask which selects =

the bit that

+	should be set if this cpu should be snooped.

Under what cases can software not figure out how to set this based on =
the PAMUs in the DT?

b/Documentation/devicetree/bindings/powerpc/fsl/pamu.txt

Port Mapping

+	registers which are part of the CoreNet Coherency fabric (CCF) =

provide a

+	CoreNet Coherency Subdomain ID/CoreNet Snoop ID to pamu mapping =

functions.

+	Certain bits from these registers should be set if PAMUs should =

be snooped.

+	This property defines a bitmask which selects the bits that =

should be set