NetBSD/sys/dev/marvell/files.armada

#	$NetBSD: files.armada,v 1.3 2015/06/03 04:20:02 hsuenaga Exp $
# Configuration info for Marvell ARMADA integrated peripherals

# ARMADA XP Buffer Manger
device	mvxpbm { [port = -1 ], [irq = -1] }
file	dev/marvell/mvxpbm.c

# ARMADA XP Gigabit Ethernet Controller Interface
define	mvxpe { [port = -1 ], [irq = -1] }
device	mvxpe: mvxpbm, ether, ifnet, arp, mii
file	dev/marvell/if_mvxpe.c			mvxpe		needs-flag

# ARMADA XP Cryptographic Engines and Security Accelerator
define	mvxpsec { [port = -1 ], [irq = -1] }
device	mvxpsec: opencrypto
file	dev/marvell/mvxpsec.c			mvxpsec		needs-flag
add new cryptographic accelerator driver 'mvxpsec.' this driver controls CESA unit as same as mvcesa, but uses DMA engines and does CBC operations, HMAC operations by hardware. about 2 kbytes of data are processed at one. supported algorithms are: - DES-CBC, 3DES-CBC, AES-CBC - HMAC-SHA1, HMAC-MD5 non-CBC algorithm such as AES-GCM is not supported by CESA's acceleration engine. mvcesa is still useful to implement such algorithms as combination of accelerated block cipher and software chaining. 2015-06-03 07:20:02 +03:00			`# $NetBSD: files.armada,v 1.3 2015/06/03 04:20:02 hsuenaga Exp $`
move Marvell ARMADA SoC's device driver definitions from arm/marvell to dev/marvell. 2015-06-03 06:34:38 +03:00			`# Configuration info for Marvell ARMADA integrated peripherals`

separate buffer management codes 'mvxpbm.c' from if_mvxpe.c. the buffer management(ex. fill the rx descriptors/buffers) is done by H/W in ARMADA XP/380, and is done by S/W in ARMADA 370. the H/W BM support is not yet implemented, so all devices use the S/W management mode at this time. 2015-06-03 06:55:47 +03:00			`# ARMADA XP Buffer Manger`
			`device mvxpbm { [port = -1 ], [irq = -1] }`
			`file dev/marvell/mvxpbm.c`

move Marvell ARMADA SoC's device driver definitions from arm/marvell to dev/marvell. 2015-06-03 06:34:38 +03:00			`# ARMADA XP Gigabit Ethernet Controller Interface`
			`define mvxpe { [port = -1 ], [irq = -1] }`
separate buffer management codes 'mvxpbm.c' from if_mvxpe.c. the buffer management(ex. fill the rx descriptors/buffers) is done by H/W in ARMADA XP/380, and is done by S/W in ARMADA 370. the H/W BM support is not yet implemented, so all devices use the S/W management mode at this time. 2015-06-03 06:55:47 +03:00			`device mvxpe: mvxpbm, ether, ifnet, arp, mii`
move Marvell ARMADA SoC's device driver definitions from arm/marvell to dev/marvell. 2015-06-03 06:34:38 +03:00			`file dev/marvell/if_mvxpe.c mvxpe needs-flag`
add new cryptographic accelerator driver 'mvxpsec.' this driver controls CESA unit as same as mvcesa, but uses DMA engines and does CBC operations, HMAC operations by hardware. about 2 kbytes of data are processed at one. supported algorithms are: - DES-CBC, 3DES-CBC, AES-CBC - HMAC-SHA1, HMAC-MD5 non-CBC algorithm such as AES-GCM is not supported by CESA's acceleration engine. mvcesa is still useful to implement such algorithms as combination of accelerated block cipher and software chaining. 2015-06-03 07:20:02 +03:00
			`# ARMADA XP Cryptographic Engines and Security Accelerator`
			`define mvxpsec { [port = -1 ], [irq = -1] }`
			`device mvxpsec: opencrypto`
			`file dev/marvell/mvxpsec.c mvxpsec needs-flag`