linux-kernel - [PATCH RFC] trafgen: xilinx: add axi traffic generator driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0b2c0db9-c1b5-4404-be6d-2644b4377e09@CH1EHSMHS034.ehs.local>
Date:	Mon, 15 Jul 2013 17:13:29 +0530
From:	Srikanth Thokala <srikanth.thokala@...inx.com>
To:	<arnd@...db.de>, <gregkh@...uxfoundation.org>,
	<rob.herring@...xeda.com>, <linux-kernel@...r.kernel.org>,
	<devicetree-discuss@...ts.ozlabs.org>, <grant.likely@...aro.org>
CC:	Michal Simek <michal.simek@...inx.com>,
	Srikanth Thokala <sthokal@...inx.com>
Subject: [PATCH RFC] trafgen: xilinx: add axi traffic generator driver 

Hi All,

This is the driver for Xilinx AXI Traffic Generator IP. The
AXI Traffic Generator IP is a core that stresses the AXI4 
interconnect and other AXI4 peripherals in the system.
It generates a wide variety of AXI4 transactions based on
the core programming.

For more details of this IP, please refer:
http://www.xilinx.com/support/documentation/ip_documentation/
axi_traffic_gen/v1_0/pg125-axi-traffic-gen.pdf

The architecture of the core is broadly separated into a master
and slave block, each of which contains the write block and
read block. Other support functions are provided by the
control registers and three internal RAMs - Master RAM (8KB), 
Command RAM(8KB), Parameter RAM(2KB). The initialisation sequence
includes programming Command RAM with commands, data into 
Master RAM (optional Parameter RAM programming) and then 
enable master logic using control register interface.
This sequence generates traffic to cores connected in the
h/w design. It can be interconnect or cores attached via the
interconnect.  The commands programmed selects the specific
core to stress.

The driver for this IP is designed to be a module with 
sysfs interface.  All the control registers and internal
RAMs can be accessed through sysfs interface. Internal
RAMs are designed to be sysfs files with BIN attributes.

Is sysfs the proper interface for this driver? If you 
guys feel there is an other framework where my driver
perfectly fits into, please suggest and provide your
inputs.

Thanks,
Srikanth.

Srikanth Thokala (1):
  trafgen: xilinx: add axi traffic generator driver

 .../devicetree/bindings/misc/xilinx-axitrafgen.txt |   21 +
 drivers/misc/Kconfig                               |   13 +
 drivers/misc/Makefile                              |    1 +
 drivers/misc/xilinx_trafgen.c                      | 1160 ++++++++++++++++++++
 4 files changed, 1195 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/misc/xilinx-axitrafgen.txt
 create mode 100644 drivers/misc/xilinx_trafgen.c

-- 
1.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/