fpga: Clarify how write_init works streaming modes
authorJason Gunthorpe <jgunthorpe@obsidianresearch.com>
Tue, 22 Nov 2016 18:22:09 +0000 (18:22 +0000)
committerAlan Tull <atull@opensource.altera.com>
Tue, 29 Nov 2016 21:51:49 +0000 (15:51 -0600)
commit1d7f1589d341344c0c598b00de44891a7968c6a0
treef1fd0d74131222096b584ebe16a11a9c0e476d34
parent340c0c53ea3073107d5bb7a61f3158e50bf189e0
fpga: Clarify how write_init works streaming modes

This interface was designed for streaming, but write_init's buf
argument has an unclear purpose. Define it to be the first bytes
of the bitstream. Each driver gets to set how many bytes (at most)
it wants to see. Short bitstreams will be passed through as-is, while
long ones will be truncated.

The intent is to allow drivers to peek at the header before the transfer
actually starts.

Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Acked-by: Alan Tull <atull@opensource.altera.com>
Documentation/fpga/fpga-mgr.txt
drivers/fpga/fpga-mgr.c
drivers/fpga/socfpga-a10.c
include/linux/fpga/fpga-mgr.h