Describe serial interrupt in serial interrupt section #555
+2
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes the (out of place) description of the serial port from the 'Interrupt Sources' page and replaces it with a description of when the serial interrupt is requested (which is the main thing that should be there).
This fixes #528, but I haven't moved any of the deleted text to the Serial Data Transfer page. It was almost all redundant. I don't think we're losing anything. But there is a couple of statements that aren't definitely wrong and also aren't explicitly mentioned on the main Serial page:
I read this as saying that the output line level is only changed when transmitting a bit that differs from the last one -- i.e., once per clock cycle at most.
I don't see how or why the behaviour would be otherwise. So maybe it's just describing something obvious (to me?) or maybe I don't know what it means.
This one is just weird. Wake-on-LAN?!
I wouldn't expect the serial port to be doing anything during STOP mode.
There's no reason to expect the/a remote device to have such control via the serial port.
Again, I don't think these are important enough to keep/move, but I found them confusing so maybe I'm missing something.