From: Michal Simek <monstr@monstr.eu>
To: arnd@arndb.de, gregkh@linuxfoundation.org
Cc: Srikanth Thokala <srikanth.thokala@xilinx.com>,
rob.herring@calxeda.com, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@linaro.org,
Michal Simek <michal.simek@xilinx.com>,
Srikanth Thokala <sthokal@xilinx.com>
Subject: Re: [LINUX PATCH RFC v2] trafgen: xilinx: add axi traffic generator driver
Date: Fri, 26 Jul 2013 14:22:37 +0200 [thread overview]
Message-ID: <51F26A0D.40302@monstr.eu> (raw)
In-Reply-To: <477a2d56-a6f9-455f-b5c7-740ae9e9ba8e@CO1EHSMHS024.ehs.local>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Hi Greg and Arnd,
On 07/20/2013 05:01 PM, Srikanth Thokala wrote:
> This is the driver for 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.
>
> 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,
> Command RAM, Parameter RAM. 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.
>
> 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.
>
> Signed-off-by: Srikanth Thokala <sthokal@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> v2: Documented sysfs functions
Do you have any concern about this patch?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-07-26 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 15:01 [LINUX PATCH RFC v2] trafgen: xilinx: add axi traffic generator driver Srikanth Thokala
2013-07-26 12:22 ` Michal Simek [this message]
2013-08-02 3:24 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F26A0D.40302@monstr.eu \
--to=monstr@monstr.eu \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rob.herring@calxeda.com \
--cc=srikanth.thokala@xilinx.com \
--cc=sthokal@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).