RFC Unrestricted media entity ID range support
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest9 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | media: Rename MEDIA_ENTITY_ENUM_MAX_ID as MEDIA_ENTITY_MAX_LOW_IDdrivers/ include/ | +5 | 0 replies | |
| 2/9 | media: Introduce low_id for media entitiesdrivers/ include/ include/ | +19 | 0 replies | |
| 3/9 | media: Add an API to manage entity enumerationsinclude/ | +44 | 0 replies | |
| 4/9 | media: Use media entity enum API for managing low IDsdrivers/ include/ include/ | +20 | 0 replies | |
| 5/9 | media: Use entity enums in graph walkdrivers/ include/ | +6 | 0 replies | |
| 6/9 | media: entity: Remove useless WARN_ON()'sdrivers/ | +0 | 0 replies | |
| 7/9 | omap3isp: Use media entity enumeration APIdrivers/ drivers/ drivers/ +2 more | +18 | 0 replies | |
| 8/9 | vsp1: Use media entity enumeration APIdrivers/ | +3 | 0 replies | |
| 9/9 | staging: omap4iss: Use media entity enum APIdrivers/ drivers/ drivers/ +1 more | +10 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/9] Unrestricted media entity ID range support
Hi all,
This patchset adds an API for managing entity enumerations, i.e. storing a bit of information per entity. The entity ID is no longer limited to small integers (e.g. 31 or 63), but MEDIA_ENTITY_MAX_LOW_ID. The drivers are also converted to use that instead of a fixed number.
If the number of entities in a real use case grows beyond the capabilities of the approach, the algorithm may be changed. But most importantly, the API is used to perform the same operation everywhere it's done.
I'm sending this for review only, the code itself is untested.
I haven't entirely made up my mind on the fourth patch. It could be dropped, as it uses the API for a somewhat different purpose.
Signature · 2 lines
Kind regards, Sakari