On 3/15/24 16:33, Mark Brown wrote: > On Fri, Mar 15, 2024 at 02:21:45AM +0300, Jan Dakinevich wrote: > >> static const struct regmap_config g12a_toacodec_regmap_cfg = { >> - .reg_bits = 32, >> - .val_bits = 32, >> - .reg_stride = 4, >> + .reg_bits = 32, >> + .val_bits = 32, >> + .reg_stride = 4, >> + .max_register = TOACODEC_CTRL0, >> + .max_register_is_0 = true, > > If the maximum register is 0 how does the regmap have a stride? reg_stride inherited from existing code. Apparently, it was meaningless even before my modifications (the hardware has single register regardless of max_register declaration) and it should be dropped. But, is it okay to remove it in the same commit? -- Best regards Jan Dakinevich
- Follow-Ups:
- Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- From: Mark Brown
- Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- From: Jerome Brunet
- Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- References:
- [PATCH 00/25] Introduce support of audio for Amlogic A1 SoC family
- From: Jan Dakinevich
- [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- From: Jan Dakinevich
- Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- From: Mark Brown
- [PATCH 00/25] Introduce support of audio for Amlogic A1 SoC family
- Prev by Date: Re: [PATCH 08/25] ASoC: dt-bindings: meson: g12a-toacodec: add support for A1 SoC family
- Next by Date: Re: [PATCH 13/25] ASoC: dt-bindings: meson: axg-pdm: document 'sysrate' property
- Previous by thread: Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- Next by thread: Re: [PATCH 09/25] ASoC: meson: g12a-toacodec: add support for A1 SoC family
- Index(es):