-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branches 'iommu/fixes', 'arm/omap', 'arm/smmu', 'arm/shmobile',…
… 'x86/amd', 'arm/exynos', 'arm/renesas', 'ppc/pamu' and 'arm/msm' into next
- Loading branch information
Showing
1,960 changed files
with
24,307 additions
and
35,579 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
97 changes: 97 additions & 0 deletions
97
Documentation/devicetree/bindings/arm/marvell,kirkwood.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,97 @@ | ||
| Marvell Kirkwood SoC Family Device Tree Bindings | ||
| ------------------------------------------------ | ||
|
|
||
| Boards with a SoC of the Marvell Kirkwook family, eg 88f6281 | ||
|
|
||
| * Required root node properties: | ||
| compatible: must contain "marvell,kirkwood" | ||
|
|
||
| In addition, the above compatible shall be extended with the specific | ||
| SoC. Currently known SoC compatibles are: | ||
|
|
||
| "marvell,kirkwood-88f6192" | ||
| "marvell,kirkwood-88f6281" | ||
| "marvell,kirkwood-88f6282" | ||
| "marvell,kirkwood-88f6283" | ||
| "marvell,kirkwood-88f6702" | ||
| "marvell,kirkwood-98DX4122" | ||
|
|
||
| And in addition, the compatible shall be extended with the specific | ||
| board. Currently known boards are: | ||
|
|
||
| "buffalo,lschlv2" | ||
| "buffalo,lsxhl" | ||
| "buffalo,lsxl" | ||
| "dlink,dns-320" | ||
| "dlink,dns-320-a1" | ||
| "dlink,dns-325" | ||
| "dlink,dns-325-a1" | ||
| "dlink,dns-kirkwood" | ||
| "excito,b3" | ||
| "globalscale,dreamplug-003-ds2001" | ||
| "globalscale,guruplug" | ||
| "globalscale,guruplug-server-plus" | ||
| "globalscale,sheevaplug" | ||
| "globalscale,sheevaplug" | ||
| "globalscale,sheevaplug-esata" | ||
| "globalscale,sheevaplug-esata-rev13" | ||
| "iom,iconnect" | ||
| "iom,iconnect-1.1" | ||
| "iom,ix2-200" | ||
| "keymile,km_kirkwood" | ||
| "lacie,cloudbox" | ||
| "lacie,inetspace_v2" | ||
| "lacie,laplug" | ||
| "lacie,netspace_lite_v2" | ||
| "lacie,netspace_max_v2" | ||
| "lacie,netspace_mini_v2" | ||
| "lacie,netspace_v2" | ||
| "marvell,db-88f6281-bp" | ||
| "marvell,db-88f6282-bp" | ||
| "marvell,mv88f6281gtw-ge" | ||
| "marvell,rd88f6281" | ||
| "marvell,rd88f6281" | ||
| "marvell,rd88f6281-a0" | ||
| "marvell,rd88f6281-a1" | ||
| "mpl,cec4" | ||
| "mpl,cec4-10" | ||
| "netgear,readynas" | ||
| "netgear,readynas" | ||
| "netgear,readynas-duo-v2" | ||
| "netgear,readynas-nv+-v2" | ||
| "plathome,openblocks-a6" | ||
| "plathome,openblocks-a7" | ||
| "raidsonic,ib-nas6210" | ||
| "raidsonic,ib-nas6210-b" | ||
| "raidsonic,ib-nas6220" | ||
| "raidsonic,ib-nas6220-b" | ||
| "raidsonic,ib-nas62x0" | ||
| "seagate,dockstar" | ||
| "seagate,goflexnet" | ||
| "synology,ds109" | ||
| "synology,ds110jv10" | ||
| "synology,ds110jv20" | ||
| "synology,ds110jv30" | ||
| "synology,ds111" | ||
| "synology,ds209" | ||
| "synology,ds210jv10" | ||
| "synology,ds210jv20" | ||
| "synology,ds212" | ||
| "synology,ds212jv10" | ||
| "synology,ds212jv20" | ||
| "synology,ds212pv10" | ||
| "synology,ds409" | ||
| "synology,ds409slim" | ||
| "synology,ds410j" | ||
| "synology,ds411" | ||
| "synology,ds411j" | ||
| "synology,ds411slim" | ||
| "synology,ds413jv10" | ||
| "synology,rs212" | ||
| "synology,rs409" | ||
| "synology,rs411" | ||
| "synology,rs812" | ||
| "usi,topkick" | ||
| "usi,topkick-1281P2" | ||
| "zyxel,nsa310" | ||
| "zyxel,nsa310a" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
70 changes: 70 additions & 0 deletions
70
Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| Samsung Exynos IOMMU H/W, System MMU (System Memory Management Unit) | ||
|
|
||
| Samsung's Exynos architecture contains System MMUs that enables scattered | ||
| physical memory chunks visible as a contiguous region to DMA-capable peripheral | ||
| devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth. | ||
|
|
||
| System MMU is an IOMMU and supports identical translation table format to | ||
| ARMv7 translation tables with minimum set of page properties including access | ||
| permissions, shareability and security protection. In addition, System MMU has | ||
| another capabilities like L2 TLB or block-fetch buffers to minimize translation | ||
| latency. | ||
|
|
||
| System MMUs are in many to one relation with peripheral devices, i.e. single | ||
| peripheral device might have multiple System MMUs (usually one for each bus | ||
| master), but one System MMU can handle transactions from only one peripheral | ||
| device. The relation between a System MMU and the peripheral device needs to be | ||
| defined in device node of the peripheral device. | ||
|
|
||
| MFC in all Exynos SoCs and FIMD, M2M Scalers and G2D in Exynos5420 has 2 System | ||
| MMUs. | ||
| * MFC has one System MMU on its left and right bus. | ||
| * FIMD in Exynos5420 has one System MMU for window 0 and 4, the other system MMU | ||
| for window 1, 2 and 3. | ||
| * M2M Scalers and G2D in Exynos5420 has one System MMU on the read channel and | ||
| the other System MMU on the write channel. | ||
| The drivers must consider how to handle those System MMUs. One of the idea is | ||
| to implement child devices or sub-devices which are the client devices of the | ||
| System MMU. | ||
|
|
||
| Note: | ||
| The current DT binding for the Exynos System MMU is incomplete. | ||
| The following properties can be removed or changed, if found incompatible with | ||
| the "Generic IOMMU Binding" support for attaching devices to the IOMMU. | ||
|
|
||
| Required properties: | ||
| - compatible: Should be "samsung,exynos-sysmmu" | ||
| - reg: A tuple of base address and size of System MMU registers. | ||
| - interrupt-parent: The phandle of the interrupt controller of System MMU | ||
| - interrupts: An interrupt specifier for interrupt signal of System MMU, | ||
| according to the format defined by a particular interrupt | ||
| controller. | ||
| - clock-names: Should be "sysmmu" if the System MMU is needed to gate its clock. | ||
| Optional "master" if the clock to the System MMU is gated by | ||
| another gate clock other than "sysmmu". | ||
| Exynos4 SoCs, there needs no "master" clock. | ||
| Exynos5 SoCs, some System MMUs must have "master" clocks. | ||
| - clocks: Required if the System MMU is needed to gate its clock. | ||
| - samsung,power-domain: Required if the System MMU is needed to gate its power. | ||
| Please refer to the following document: | ||
| Documentation/devicetree/bindings/arm/exynos/power_domain.txt | ||
|
|
||
| Examples: | ||
| gsc_0: gsc@13e00000 { | ||
| compatible = "samsung,exynos5-gsc"; | ||
| reg = <0x13e00000 0x1000>; | ||
| interrupts = <0 85 0>; | ||
| samsung,power-domain = <&pd_gsc>; | ||
| clocks = <&clock CLK_GSCL0>; | ||
| clock-names = "gscl"; | ||
| }; | ||
|
|
||
| sysmmu_gsc0: sysmmu@13E80000 { | ||
| compatible = "samsung,exynos-sysmmu"; | ||
| reg = <0x13E80000 0x1000>; | ||
| interrupt-parent = <&combiner>; | ||
| interrupts = <2 0>; | ||
| clock-names = "sysmmu", "master"; | ||
| clocks = <&clock CLK_SMMU_GSCL0>, <&clock CLK_GSCL0>; | ||
| samsung,power-domain = <&pd_gsc>; | ||
| }; |
Oops, something went wrong.