Hi Philipp, On 10/9/14, 4:03 AM, Philipp Zabel wrote: > Am Mittwoch, den 08.10.2014, 21:44 -0500 schrieb > dinguyen@xxxxxxxxxxxxxxxxxxxxx: >> From: Dinh Nguyen <dinguyen@xxxxxxxxxxxxxxxxxxxxx> >> >> There are certain drivers that are required to get loaded very early using >> arch_initcall. An example of such a driver is the SOCFPGA's FPGA bridge driver. >> This driver has to get loaded early because it needs to enable FPGA components >> that are connected to the bridge. >> >> This FPGA bridge driver will using the reset controller API to toggle it's >> reset bits, thus, it needs the reset driver to be loaded as early as possible >> in order for it to get used properly. > > Without knowing the details, this sounds like the wrong approach. Can't > the bridge driver return -EPROBE_DEFER until the reset controller is > available? > The bridge driver is also using arch_initcall, as it also needs to get loaded early for FPGA IPs to work, and so later driver loading will work for the FPGA IPs. Dinh -- 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
