SoCFPGA: L3 NIC driver
Get series with b4
b4 am 20141204183730.GB11889@leverpostejVersions newest first · linked by author and title
- v3 Latest posting 2/20 of 3 patches 0 repliesNew
- v3 posting 1/20 of 3 patches 0 repliesSuperseded
Patches in v3 posting 2/2 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/3] SoCFPGA: L3 NIC driver
Quoted 28 lines · Arnd Bergmann
Quoted 10 lines · On Sunday 30 November 2014 21:53:31 Robert Schwebel wrote:
Quoted 6 lines · Arnd Bergmann
Quoted 4 lines
This series adds support for the SoCFPGA L3 NIC. As the memory range has a lot of holes, where you can not read from, syscon can not be used for this IP core. Instead add a new driver, that knows about all the allowed ranges and guards the access via regmap.
What is an L3 NIC?
Fron the SoCFPGA manual:
Quoted 16 lines
"
The hard processor system (HPS) level 3 (L3) interconnect and level 4 (L4) peripheral buses are implemented with the ARM CoreLinkTM Network Interconnect (NIC-301). The NIC-301 provides a foundation for a high-performance HPS interconnect based on the ARM Advanced Microcontroller Bus Architecture (AMBA) Advanced eXtensible Interface (AXI), Advanced High-Performance Bus (AHBTM), and Advanced Peripheral Bus (APBTM) protocols. The L3 interconnect implements a multilayer, nonblocking architecture that supports multiple simultaneous transactions between masters and slaves, including the Cortex-A9 microprocessor unit (MPU) subsystem. The interconnect provides five independent L4 buses to access control and status registers (CSRs) of peripherals, managers, and memory controllers Related Information
http://infocenter.arm.com/ Additional information is available in the AMBA Network Interconnect (NIC-301) Technical Reference Manual, revision r2p3, which you can download from the ARM info center website.
Quoted 3 lines
Please put something like this in the introductory mail and later into the pull request then. If the l3-nic is an ARM nic-301, shouldn't the compatible string be "arm,nic-301"?
We should also treat the device as a bus, with it's child devices as nodes underneath it (rather than a block on the side referred to by phandle).
Mark.