On Fri, May 17, 2024 at 05:05:38AM -0400, Elinor Montmasson wrote: > This new compatible is intended to be used when there is no codec > device/driver. There is technically no codec device/driver for which > the clock input can be set. This is obviously not true, there clearly is a driver. > Is it a bad idea to allow setting the cpu sysclk direction only ? > Should the compatible be limited to use-cases where the cpu sysclk > direction cannot be set by the machine driver ? When I said "this should use the clock bindings" I meant that we should use the clock bindings for configuration here.
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- From: Elinor Montmasson
- Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- References:
- [PATCHv4 0/9] ASoC: fsl-asoc-card: compatibility integration of a generic codec use case for use with S/PDIF controller
- From: Elinor Montmasson
- [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- From: Elinor Montmasson
- Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- From: Mark Brown
- Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- From: Elinor Montmasson
- [PATCHv4 0/9] ASoC: fsl-asoc-card: compatibility integration of a generic codec use case for use with S/PDIF controller
- Prev by Date: [PATCH 2/2] ASoC: fsl_mqs: Add i.MX95 platform support
- Next by Date: Re: [PATCHv4 9/9] ASoC: dt-bindings: fsl-asoc-card: add compatible for generic codec
- Previous by thread: Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- Next by thread: Re: [PATCHv4 8/9] ASoC: fsl-asoc-card: add DT property "cpu-system-clock-direction-out"
- Index(es):