Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754303Ab3GTPAQ (ORCPT ); Sat, 20 Jul 2013 11:00:16 -0400 Received: from mail-db9lp0250.outbound.messaging.microsoft.com ([213.199.154.250]:32789 "EHLO db9outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754174Ab3GTPAO (ORCPT ); Sat, 20 Jul 2013 11:00:14 -0400 X-Forefront-Antispam-Report: CIP:149.199.60.83;KIP:(null);UIP:(null);IPV:NLI;H:xsj-gw1;RD:unknown-60-83.xilinx.com;EFVD:NLI X-SpamScore: 0 X-BigFish: VPS0(z551bizd799h4015I14ffIzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz17326ah1de097h1de096h8275bhz2fh95h668h839hd24hf0ah119dh1288h12a5h12a9h12bdh12e5h137ah139eh13b6h1441h14ddh1504h1537h162dh1631h1758h1898h18e1h1946h19b5h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1e23h906i1155h192ch) From: Srikanth Thokala To: , , , , , CC: Michal Simek , Srikanth Thokala Subject: [LINUX PATCH RFC v2] Add new driver for Xilinx AXI Traffic Generator IP Date: Sat, 20 Jul 2013 20:29:47 +0530 X-Mailer: git-send-email 1.7.4 X-RCIS-Action: ALLOW MIME-Version: 1.0 Content-Type: text/plain Message-ID: X-OriginatorOrg: xilinx.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2283 Lines: 58 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 | 1394 ++++++++++++++++++++ 4 files changed, 1429 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/