Bounine, Alexandre wrote:
That real PW message may be dropped by the controller (85xx is good
example). Everything depends on number of PW messages directed to the
host/controller. I am trying to use the first available notification to
service device removal. If the real PW message is received
Micha Nelissen wrote:
Perhaps an idea is to use the repeated port-write sending feature so
that dropped port-writes are not a problem anymore.
Unfortunately, this feature is not defined by RIO spec. This is
proprietary function, so we
cannot rely on it. Yes, this is nice feature of Tsi57x
Alexandre Bounine wrote:
Add check if PW message source device is accessible and change PW message
handler to recover if PW message source device is not available anymore (power
down or link disconnect).
I am not quite sure what the point is of this patch. What do you need to
recover from?
Micha Nelissen wrote:
Alexandre Bounine wrote:
Add check if PW message source device is accessible and change PW
message
handler to recover if PW message source device is not available
anymore (power
down or link disconnect).
I am not quite sure what the point is of this patch. What do
Add check if PW message source device is accessible and change PW message
handler to recover if PW message source device is not available anymore (power
down or link disconnect).
To avoid possible loss of notification, the PW message handler scans the route
back from the source device to identify
