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.
For the serial subsystem, it makes sense to have a different number of clients capable of input and output: not all clients which are capable of output will need input. Prior to this PR, there was a
SERIAL_NUM_CLIENTS
macro, as well as aSERIAL_TX_ONLY
macro which indicated whether or not serial input was required (e.g. whether the driver enabled RX IRQs, or if an RX virtualiser is necessary).I believe it makes more sense to instead have a separate count for each functionality, as for example it is plausible that a system may have only 1 client with input enabled, and more than 1 with output enabled.
This PR essentially turns the
SERIAL_NUM_CLIENTS
andSERIAL_TX_ONLY
macros into theSERIAL_NUM_TX_CLIENTS
andSERIAL_NUM_RX_CLIENTS
macros, in preparation for the tooling supporting specification for each client whether TX and/or RX are enabled.Merge after #301.