net: ipa: memory region rework, part 1
Status from this message: This series was applied to netdev/net-next.git (refs/heads/master):
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 11 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/11 | net: ipa: define IPA_MEM_END_MARKERdrivers/ drivers/ drivers/ +1 more | +5 | 0 replies | Applied |
| 2/11 | net: ipa: store memory region id in descriptordrivers/ drivers/ drivers/ +3 more | +106 | 0 replies | Applied |
| 3/11 | net: ipa: validate memory regions unconditionallydrivers/ | +3 | 0 replies | Applied |
| 4/11 | net: ipa: separate memory validation from initializationdrivers/ | +32 | 0 replies | Applied |
| 5/11 | net: ipa: separate region range check from other validationdrivers/ | +26 | 0 replies | Applied |
| 6/11 | net: ipa: validate memory regions at init timedrivers/ | +4 | 0 replies | Applied |
| 7/11 | net: ipa: pass memory configuration data to ipa_mem_valid()drivers/ | +14 | 0 replies | Applied |
| 8/11 | net: ipa: introduce ipa_mem_id_optional()drivers/ drivers/ | +53 | 0 replies | Applied |
| 9/11 | net: ipa: validate memory regions based on versiondrivers/ | +61 | 0 replies | Applied |
| 10/11 | net: ipa: flag duplicate memory regionsdrivers/ | +9 | 0 replies | Applied |
| 11/11 | net: ipa: use bitmap to check for missing regionsdrivers/ | +5 | 0 replies | Applied |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH net-next 00/11] net: ipa: memory region rework, part 1
This is the first portion of a very long series of patches that has been split in two. Once these patches are accepted, I'll post the remaining patches.
The combined series reworks the way memory regions are defined in the configuration data, and in the process solidifies code that ensures configurations are valid.
In this portion (part 1), most of the focus is on improving validation of code. This validation is now done unconditionally (something I promised Leon Romanovsky I would work on). Validation will occur earlier than before, catching configuration problems as early as possible and permitting the rest of the driver to avoid needing to do some error checking. There will now be checks to ensure all defined regions are supported by the hardware, that required regions are all defined, and that there are no duplicate regions.
The second portion (part 2) is mainly a set of small but pervasive changes whose result is to have the memory region array not be indexed by region ID. I'll provide further explanation when I post that series.
-Alex
Alex Elder (11):
net: ipa: define IPA_MEM_END_MARKER
net: ipa: store memory region id in descriptor
net: ipa: validate memory regions unconditionally
net: ipa: separate memory validation from initialization
net: ipa: separate region range check from other validation
net: ipa: validate memory regions at init time
net: ipa: pass memory configuration data to ipa_mem_valid()
net: ipa: introduce ipa_mem_id_optional()
net: ipa: validate memory regions based on version
net: ipa: flag duplicate memory regions
net: ipa: use bitmap to check for missing regions
drivers/net/ipa/ipa_data-v3.5.1.c | 15 +++ drivers/net/ipa/ipa_data-v4.11.c | 24 +++- drivers/net/ipa/ipa_data-v4.2.c | 20 ++- drivers/net/ipa/ipa_data-v4.5.c | 23 ++++ drivers/net/ipa/ipa_data-v4.9.c | 26 +++- drivers/net/ipa/ipa_mem.c | 196 ++++++++++++++++++++++++++---- drivers/net/ipa/ipa_mem.h | 25 ++-- 7 files changed, 291 insertions(+), 38 deletions(-)
Signature · 1 line
2.27.0