Skip to content

[FEATURE] Generic cache management formodule_set_large_config() #6285

Closed

Description

@lyakh

Is your feature request related to a problem? Please describe.
A problem with cache management has recently been fixed by #6274 for the volume module. However, that fix has to be made generic, not volume-specific.

Describe the solution you'd like
Cache invalidation for module configuration has to be done in module core, not in individual module drivers.

Additional context
See the aforementioned PR and particularly comment #6274 (comment) in it.

Activity

  1. added this to the v2.4 milestone on Oct 18, 2022
  2. lgirdwood commented on Oct 18, 2022

    @lgirdwood
    Member

    May need locking too.

  3. kv2019i commented on Feb 17, 2023

    @kv2019i
    Collaborator

    @lyakh Is this still open? If yes, ok to queue for v2.5?

  4. modified the milestones: v2.4, v2.5 on Feb 17, 2023
  5. kv2019i commented on Mar 6, 2023

    @kv2019i
    Collaborator

    @lyakh Still on track for V2.5 -- we aim to branch this week?

  6. kv2019i commented on Mar 9, 2023

    @kv2019i
    Collaborator

    No response, moving to v2.6.

  7. modified the milestones: v2.5, v2.6 on Mar 9, 2023
  8. modified the milestones: v2.6, v2.7 on May 11, 2023
  9. modified the milestones: v2.7, v2.8 on Aug 21, 2023
  10. kv2019i commented on Nov 22, 2023

    @kv2019i
    Collaborator

    @lyakh This has been pushed onwards since v2.5, let's try to cover this in v2.9 planning, so we have actual time to do this.

  11. modified the milestones: v2.8, v2.9 on Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions