ASoC: SDCA: Add stubs for FDL helper functions
Subsystems (2)
Charles Keepax
maintainerPATCH 1/1 ASoC: SDCA: Add stubs for FDL helper functions
In the case the SDCA IRQ is built in but FDL support is not stub functions are required for the FDL helpers to avoid build failures. The FDL IRQs likely shouldn't get triggered in this case, however they would still be a part of the build.
--- include/sound/sdca_fdl.h | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)
include/sound/sdca_fdl.h +30 -0
@@ -64,6 +64,8 @@ struct fdl_state { SDCA_CTL_XU_FDLD_ACK_TRANSFER | \ SDCA_CTL_XU_FDLD_NEEDS_SET) +#if IS_ENABLED (CONFIG_SND_SOC_SDCA_FDL ) +int sdca_fdl_alloc_state (struct sdca_interrupt *interrupt);int sdca_fdl_process (struct sdca_interrupt *interrupt); int sdca_fdl_sync(struct device *dev, struct sdca_function_data *function,
@@ -72,4 +74,32 @@ int sdca_fdl_sync(struct device *dev, struct sdca_function_data *function,int sdca_reset_function (struct device *dev,struct sdca_function_data *function,struct regmap *regmap); +#else + +static inline int sdca_fdl_alloc_state (struct sdca_interrupt *interrupt) +{ +return 0 ; +} + +static inline int sdca_fdl_process (struct sdca_interrupt *interrupt) +{ +return 0 ; +} + +static inline int sdca_fdl_sync (struct device *dev, +struct sdca_function_data *function, +struct sdca_interrupt_info *info) +{ +return 0 ; +} + +static inline int sdca_reset_function (struct device *dev, +struct sdca_function_data *function, +struct regmap *regmap) +{ +return 0 ; +} + +#endif // CONFIG_SND_SOC_SDCA_FDL +#endif // __SDCA_FDL_H__
Signature · 1 line
2.47.3
Quoted 6 lines · Charles Keepax
In the case the SDCA IRQ is built in but FDL support is not stub functions are required for the FDL helpers to avoid build failures. The FDL IRQs likely shouldn't get triggered in this case, however they would still be a part of the build.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SDCA: Add stubs for FDL helper functions
commit: 3efee7362dbf896072af1c1aaeaf9fd6e235c591
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark