xref: /linux/Documentation/driver-api/fpga/fpga-mgr.rst (revision 4a6ff3c9a6fadd98ca4ba8e78820a06ad3e50863)
1547b822cSAlan TullFPGA Manager
2547b822cSAlan Tull============
3547b822cSAlan Tull
4547b822cSAlan TullOverview
5547b822cSAlan Tull--------
6547b822cSAlan Tull
7547b822cSAlan TullThe FPGA manager core exports a set of functions for programming an FPGA with
8547b822cSAlan Tullan image.  The API is manufacturer agnostic.  All manufacturer specifics are
9547b822cSAlan Tullhidden away in a low level driver which registers a set of ops with the core.
10547b822cSAlan TullThe FPGA image data itself is very manufacturer specific, but for our purposes
11547b822cSAlan Tullit's just binary data.  The FPGA manager core won't parse it.
12547b822cSAlan Tull
13547b822cSAlan TullThe FPGA image to be programmed can be in a scatter gather list, a single
14547b822cSAlan Tullcontiguous buffer, or a firmware file.  Because allocating contiguous kernel
15547b822cSAlan Tullmemory for the buffer should be avoided, users are encouraged to use a scatter
16547b822cSAlan Tullgather list instead if possible.
17547b822cSAlan Tull
18547b822cSAlan TullThe particulars for programming the image are presented in a structure (struct
19547b822cSAlan Tullfpga_image_info).  This struct contains parameters such as pointers to the
20547b822cSAlan TullFPGA image as well as image-specific particulars such as whether the image was
21547b822cSAlan Tullbuilt for full or partial reconfiguration.
22547b822cSAlan Tull
23547b822cSAlan TullHow to support a new FPGA device
24547b822cSAlan Tull--------------------------------
25547b822cSAlan Tull
26547b822cSAlan TullTo add another FPGA manager, write a driver that implements a set of ops.  The
27547b822cSAlan Tullprobe function calls fpga_mgr_register(), such as::
28547b822cSAlan Tull
29547b822cSAlan Tull	static const struct fpga_manager_ops socfpga_fpga_ops = {
30547b822cSAlan Tull		.write_init = socfpga_fpga_ops_configure_init,
31547b822cSAlan Tull		.write = socfpga_fpga_ops_configure_write,
32547b822cSAlan Tull		.write_complete = socfpga_fpga_ops_configure_complete,
33547b822cSAlan Tull		.state = socfpga_fpga_ops_state,
34547b822cSAlan Tull	};
35547b822cSAlan Tull
36547b822cSAlan Tull	static int socfpga_fpga_probe(struct platform_device *pdev)
37547b822cSAlan Tull	{
38547b822cSAlan Tull		struct device *dev = &pdev->dev;
39547b822cSAlan Tull		struct socfpga_fpga_priv *priv;
40547b822cSAlan Tull		struct fpga_manager *mgr;
41547b822cSAlan Tull		int ret;
42547b822cSAlan Tull
43547b822cSAlan Tull		priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
44547b822cSAlan Tull		if (!priv)
45547b822cSAlan Tull			return -ENOMEM;
46547b822cSAlan Tull
47547b822cSAlan Tull		/*
48547b822cSAlan Tull		 * do ioremaps, get interrupts, etc. and save
49547b822cSAlan Tull		 * them in priv
50547b822cSAlan Tull		 */
51547b822cSAlan Tull
52084181feSAlan Tull		mgr = devm_fpga_mgr_create(dev, "Altera SOCFPGA FPGA Manager",
53547b822cSAlan Tull					   &socfpga_fpga_ops, priv);
54547b822cSAlan Tull		if (!mgr)
55547b822cSAlan Tull			return -ENOMEM;
56547b822cSAlan Tull
57547b822cSAlan Tull		platform_set_drvdata(pdev, mgr);
58547b822cSAlan Tull
59084181feSAlan Tull		return fpga_mgr_register(mgr);
60547b822cSAlan Tull	}
61547b822cSAlan Tull
62547b822cSAlan Tull	static int socfpga_fpga_remove(struct platform_device *pdev)
63547b822cSAlan Tull	{
64547b822cSAlan Tull		struct fpga_manager *mgr = platform_get_drvdata(pdev);
65547b822cSAlan Tull
66547b822cSAlan Tull		fpga_mgr_unregister(mgr);
67547b822cSAlan Tull
68547b822cSAlan Tull		return 0;
69547b822cSAlan Tull	}
70547b822cSAlan Tull
71547b822cSAlan Tull
72547b822cSAlan TullThe ops will implement whatever device specific register writes are needed to
73547b822cSAlan Tulldo the programming sequence for this particular FPGA.  These ops return 0 for
74547b822cSAlan Tullsuccess or negative error codes otherwise.
75547b822cSAlan Tull
76547b822cSAlan TullThe programming sequence is::
77547b822cSAlan Tull 1. .write_init
78547b822cSAlan Tull 2. .write or .write_sg (may be called once or multiple times)
79547b822cSAlan Tull 3. .write_complete
80547b822cSAlan Tull
81547b822cSAlan TullThe .write_init function will prepare the FPGA to receive the image data.  The
82a59f95c7SAlan Tullbuffer passed into .write_init will be at most .initial_header_size bytes long;
83547b822cSAlan Tullif the whole bitstream is not immediately available then the core code will
84547b822cSAlan Tullbuffer up at least this much before starting.
85547b822cSAlan Tull
86547b822cSAlan TullThe .write function writes a buffer to the FPGA. The buffer may be contain the
87547b822cSAlan Tullwhole FPGA image or may be a smaller chunk of an FPGA image.  In the latter
88547b822cSAlan Tullcase, this function is called multiple times for successive chunks. This interface
89547b822cSAlan Tullis suitable for drivers which use PIO.
90547b822cSAlan Tull
91547b822cSAlan TullThe .write_sg version behaves the same as .write except the input is a sg_table
92547b822cSAlan Tullscatter list. This interface is suitable for drivers which use DMA.
93547b822cSAlan Tull
94547b822cSAlan TullThe .write_complete function is called after all the image has been written
95547b822cSAlan Tullto put the FPGA into operating mode.
96547b822cSAlan Tull
97a59f95c7SAlan TullThe ops include a .state function which will determine the state the FPGA is in
98a59f95c7SAlan Tulland return a code of type enum fpga_mgr_states.  It doesn't result in a change
99a59f95c7SAlan Tullin state.
100547b822cSAlan Tull
101547b822cSAlan TullAPI for implementing a new FPGA Manager driver
102547b822cSAlan Tull----------------------------------------------
103547b822cSAlan Tull
104*4a6ff3c9SAlan Tull* ``fpga_mgr_states`` —  Values for :c:member:`fpga_manager->state`.
105*4a6ff3c9SAlan Tull* struct :c:type:`fpga_manager` —  the FPGA manager struct
106*4a6ff3c9SAlan Tull* struct :c:type:`fpga_manager_ops` —  Low level FPGA manager driver ops
107*4a6ff3c9SAlan Tull* :c:func:`devm_fpga_mgr_create` —  Allocate and init a manager struct
108*4a6ff3c9SAlan Tull* :c:func:`fpga_mgr_register` —  Register an FPGA manager
109*4a6ff3c9SAlan Tull* :c:func:`fpga_mgr_unregister` —  Unregister an FPGA manager
110*4a6ff3c9SAlan Tull
111*4a6ff3c9SAlan Tull.. kernel-doc:: include/linux/fpga/fpga-mgr.h
112*4a6ff3c9SAlan Tull   :functions: fpga_mgr_states
113*4a6ff3c9SAlan Tull
114547b822cSAlan Tull.. kernel-doc:: include/linux/fpga/fpga-mgr.h
115547b822cSAlan Tull   :functions: fpga_manager
116547b822cSAlan Tull
117547b822cSAlan Tull.. kernel-doc:: include/linux/fpga/fpga-mgr.h
118547b822cSAlan Tull   :functions: fpga_manager_ops
119547b822cSAlan Tull
120547b822cSAlan Tull.. kernel-doc:: drivers/fpga/fpga-mgr.c
121084181feSAlan Tull   :functions: devm_fpga_mgr_create
122084181feSAlan Tull
123084181feSAlan Tull.. kernel-doc:: drivers/fpga/fpga-mgr.c
124547b822cSAlan Tull   :functions: fpga_mgr_register
125547b822cSAlan Tull
126547b822cSAlan Tull.. kernel-doc:: drivers/fpga/fpga-mgr.c
127547b822cSAlan Tull   :functions: fpga_mgr_unregister
128