Re: [RFC PATCH v2] Xilinx AXI-Stream FIFO v4.1 IP core driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 16, 2018 at 09:43:47AM +0200, Greg KH wrote:
> On Sun, Jul 15, 2018 at 04:38:51PM -0400, Jacob Feder wrote:
> > On Sun, Jul 15, 2018 at 09:44:58PM +0200, Greg KH wrote:
> > > On Sun, Jul 15, 2018 at 12:34:28PM -0400, Jacob Feder wrote:
> > > > Hi,
> > > > I have updated this with the recommended changes. I haven't tried out the
> > > > UIO though. It will be a pretty significant undertaking and I don't want
> > > > to spend the time on it unless there is a specific reason you think it
> > > > will be faster.
> > > > 
> > > > Thanks all.
> > > > 
> > > > Cheers,
> > > > Jacob
> > > > 
> > > > This IP core has read and write AXI-Stream FIFOs, the contents of which can
> > > > be accessed from the AXI4 memory-mapped interface. This is useful for
> > > > transferring data from a processor into the FPGA fabric. The driver creates
> > > > a character device that can be read/written to with standard
> > > > open/read/write/close.
> > > > 
> > > > See Xilinx PG080 document for IP details.
> > > > 
> > > > https://www.xilinx.com/support/documentation/ip_documentation/axi_fifo_mm_s/v4_1/pg080-axi-fifo-mm-s.pdf
> > > > 
> > > > The driver currently supports only store-forward mode with a 32-bit
> > > > AXI4 Lite interface. DOES NOT support:
> > > > 	- cut-through mode
> > > > 	- AXI4 (non-lite)
> > > > 
> > > > Signed-off-by: Jacob Feder <jacobsfeder@xxxxxxxxx>
> > > > ---
> > > >  Documentation/devicetree/bindings/axisfifo.txt |   89 ++
> > > 
> > > This should live in the directory with the driver until it gets
> > > accepted into the "main" part of the kernel tree.
> > > 
> > 
> > Ok will do.
> > 
> > > >  drivers/staging/axisfifo/axis-fifo.c           | 1242 ++++++++++++++++++++++++
> > > >  2 files changed, 1331 insertions(+)
> > > >  create mode 100644 Documentation/devicetree/bindings/axisfifo.txt
> > > >  create mode 100644 drivers/staging/axisfifo/axis-fifo.c
> > > 
> > > No Makefile or Kconfig to actually build the driver?
> > > 
> > > Please fix that up so we can at least test-build the thing :)
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Oh... how do I do that exactly? :) I am currently building it with
> > Petalinux (Xilinx's wrapper for Yocto). I'm guessing there is a makefile
> > somewhere in the Yocto directory I can give you?
> 
> No, it needs to be in the directory of the driver itself.  Look at how
> all of the other drivers/staging/*/Makefile look, same for Kconfig.  If
> you need help, just ask and I can easily make one up for you.
> 
> thanks,
> 
> greg k-h

I'll give it a shot.

Thanks,
Jacob
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel



[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux