Skip to content
This repository has been archived by the owner on Dec 6, 2018. It is now read-only.

the bus driver: support xfer() while in IRQ #36

Closed
forGGe opened this issue May 3, 2016 · 1 comment
Closed

the bus driver: support xfer() while in IRQ #36

forGGe opened this issue May 3, 2016 · 1 comment

Comments

@forGGe
Copy link
Collaborator

forGGe commented May 3, 2016

Currently there is no way to start new bus transfer while servicing an interrupt. This is the significant limitation which prevents designing of event-driven systems based on the Core.

Refs:
Bus xfer() method.

@forGGe forGGe added this to the Release milestone: v0.2.0 milestone May 11, 2016
forGGe added a commit that referenced this issue May 27, 2016
Splitting the async xfer into two parts helps avoid unnecessary
overhead with setuping buffers and handlers.

Continuation xfer support included.
forGGe added a commit that referenced this issue May 27, 2016
Splitting the async xfer into two parts helps avoid unnecessary
overhead with setuping buffers and handlers.

Continuation xfer support included.
forGGe added a commit that referenced this issue May 27, 2016
Splitting the async xfer into two parts helps avoid unnecessary
overhead with setuping buffers and handlers.

Continuation xfer support included.
forGGe added a commit that referenced this issue May 27, 2016
Splitting the async xfer into two parts helps avoid unnecessary
overhead with setuping buffers and handlers.

Continuation xfer support included.
forGGe added a commit that referenced this issue May 28, 2016
The bus: #36 Basic support of running xfer() during IRQ
@forGGe
Copy link
Collaborator Author

forGGe commented May 28, 2016

Implemented in #64

@forGGe forGGe closed this as completed May 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant