Re: drvAsynIPPortConfigure and I/O Intr with asynRecord possible?

[Benjamin Franksen via Tech-talk <tech-talk@aps.anl.gov>]

Am 04.04.19 um 20:32 schrieb Mark Rivers via Tech-talk:
> The asyn record does NOT work with SCAN=I/O Intr for TCP devices. The
> problem is that drvAsynIPPort does not have a mechanism to do
> callbacks when there is new data, so asyn client needs to poll.  The
> only code I know of that does this is StreamDevice.
It is easy to add this capability to drvAsynIPPort. But when I call
pasynManager->registerInterruptSource I get an error
"asynManager:registerInterruptSource already registered". Apparently
there is a mechanism in place that generically registers an interrupt
source for /every/ asynOctet interface (and all other standard asyn
interfaces, too). This effectively blocks this feature for all standard
asyn interfaces, so it becomes impossible to add I/O Intr support to
drvAsynIPPort. The code that calls registerInterruptSource in this
generic manner is guarded by an "if (octetCanInterrupt)" but I was
unable to find out what I should do for this flag to be reset. It gets
set by the constructor for class asynPortDriver, but I found no place
where this class actually gets instantiated to an object, i.e. a call to
the constructor takes place. I find all this pretty confusing and would
appreciate hints...

Cheers
Ben

Attachment: signature.asc
Description: OpenPGP digital signature