Hi Alan, On Mon, Dec 14, 2015 at 5:56 PM, Alan Tull <delicious.quinoa@xxxxxxxxx> wrote: >> I had an offline discussion with Josh Cartwright about his concerns. >> He brought up a good >> point on w.r.t to the way FPGA Area (Bus) deals with things. >> >> Currently we only support complete status = "okay" vs "disabled" kind >> of overlays. > Maybe i don't understand what you are saying; could you write out a > sequence you want to be able to do? Let's say you have a UART in the FPGA. You want to reprogram the FPGA fabric that includes the UART (assuming proper resets etc happen) 1) Driver gets notified of impending doom, keeps hands off of FPGA 2) FPGA Manager reloads FPGA 3) FPGA Manager lets driver know FPGA is back 4) Driver can continue to function as always It wouldn't even have to be a UART, on some boards simple SPI lines or UART lines go from the processor through the FPGA logic out to a pin. When you reload the FPGA for a short moment of time that doesn't work, while after the reload it works just fine. Maybe something like extcon could be used for that? > Is this a separate question/issue from the above? Are you talking > about acceleration? I meant stuff like SPI that gets routed through the FPGA, sorry for being unclear ;-) >> >> I've been toying around with hacking up struct device to include a >> FPGA 'domain', and then, similar >> to power domains allow devices to register suspend() / resume() style >> callbacks (could call them pre_reload() or something like that ...) >> >> I haven't gotten around to think it through. At this point it's just >> an idea and I don't have real code to show. >> >> I realize the issue with that is we'd have to make changes to struct device. > > That's interesting. Usually a FPGA image has many devices in it, so > so way of making that dependency clear would be needed. If any of the > devices involved are powered up, that FPGA image would need to be > loaded. Yeah. That's why I think the power domain model we have has a bunch of similarities. > Currently I'm trying to get some bindings approved for doing device > tree control of loading the FPGA and probing the devices. My idea is > that these bindings could be useful for some use cases where we are > loading hardware onto the FPGA that needs to show up in the device > tree. Some of Rob's feedback is that my proposal may be > Altera-specific. If the bindings that I am proposing are useful for at > least some uses with Xilinx parts, that would be valuable feedback at > this point. If they are Altera-specific, then I may need to add > "altr," to some of the compatible strings like "altr,fpga-bus" and > "altr,fpga-area". My original intent was to implement something that > you could use also, so I hope that's not the future here. > > So my question for you is: is this stuff useful for you? Definitely, I'm pretty happy with what you have so far! I think the points I mentioned above apply to Altera devices, too. Maybe we can solve this in two parts, and the first step is getting the loading bindings accepted ;-) Cheers, Moritz -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
