On Tue, Apr 11, 2017 at 09:53:38AM -0500, Alan Tull wrote:
> On Tue, Apr 11, 2017 at 4:22 AM, Tobias Klauser wrote:
>
> Hi Tobias,
>
> Thanks!
>
> > If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
> > alt_fpga_bridge_probe(), the clock remains
On Tue, Apr 11, 2017 at 09:53:38AM -0500, Alan Tull wrote:
> On Tue, Apr 11, 2017 at 4:22 AM, Tobias Klauser wrote:
>
> Hi Tobias,
>
> Thanks!
>
> > If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
> > alt_fpga_bridge_probe(), the clock remains enabled and prepared. Also,
On Tue, Apr 11, 2017 at 4:22 AM, Tobias Klauser wrote:
Hi Tobias,
Thanks!
> If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
> alt_fpga_bridge_probe(), the clock remains enabled and prepared. Also,
> in the error path for _alt_hps2fpga_enable_set() a
On Tue, Apr 11, 2017 at 4:22 AM, Tobias Klauser wrote:
Hi Tobias,
Thanks!
> If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
> alt_fpga_bridge_probe(), the clock remains enabled and prepared. Also,
> in the error path for _alt_hps2fpga_enable_set() a call to
>
If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
alt_fpga_bridge_probe(), the clock remains enabled and prepared. Also,
in the error path for _alt_hps2fpga_enable_set() a call to
fpga_bridge_unregister() is made even though the bridge was not
registered yet.
Remove the
If either _alt_hps2fpga_enable_set() or fpga_bridge_register() fail in
alt_fpga_bridge_probe(), the clock remains enabled and prepared. Also,
in the error path for _alt_hps2fpga_enable_set() a call to
fpga_bridge_unregister() is made even though the bridge was not
registered yet.
Remove the
6 matches
Mail list logo