On Sun, Jul 28, 2024 at 12:30:12PM +0200, Krzysztof Kozlowski wrote: > On 27/07/2024 22:23, Stephan Gerhold wrote: > > On Tue, Jul 23, 2024 at 10:33:00AM +0200, Krzysztof Kozlowski wrote: > >> The APQ8016 SBC and MSM8916 QDSP6 sound cards are a bit different from > >> others: they have additional IO muxing address space and pin control. > >> Move them to separate schema, so the original qcom,sm8250.yaml will be > >> easier to manage. New schema is going to grow for other platforms > >> having more of IO muxing address spaces. > >> > >> Cc: Adam Skladowski <a39.skl@xxxxxxxxx> > >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> > >> --- > >> .../sound/qcom,apq8016-sbc-sndcard.yaml | 205 ++++++++++++++++++ > >> .../bindings/sound/qcom,sm8250.yaml | 137 ------------ > >> 2 files changed, 205 insertions(+), 137 deletions(-) > >> create mode 100644 Documentation/devicetree/bindings/sound/qcom,apq8016-sbc-sndcard.yaml > >> > >> diff --git a/Documentation/devicetree/bindings/sound/qcom,apq8016-sbc-sndcard.yaml b/Documentation/devicetree/bindings/sound/qcom,apq8016-sbc-sndcard.yaml > >> new file mode 100644 > >> index 000000000000..6ad451549036 > >> [...] > >> diff --git a/Documentation/devicetree/bindings/sound/qcom,sm8250.yaml b/Documentation/devicetree/bindings/sound/qcom,sm8250.yaml > >> index c9076dcd44c1..1d3acdc0c733 100644 > >> --- a/Documentation/devicetree/bindings/sound/qcom,sm8250.yaml > >> +++ b/Documentation/devicetree/bindings/sound/qcom,sm8250.yaml > >> @@ -27,9 +27,7 @@ properties: > >> - qcom,sm8650-sndcard > >> - const: qcom,sm8450-sndcard > >> - enum: > >> - - qcom,apq8016-sbc-sndcard > >> - qcom,apq8096-sndcard > >> - - qcom,msm8916-qdsp6-sndcard > >> - qcom,qcm6490-idp-sndcard > >> - qcom,qcs6490-rb3gen2-sndcard > >> - qcom,qrb5165-rb5-sndcard > >> @@ -58,18 +56,6 @@ properties: > >> $ref: /schemas/types.yaml#/definitions/string > >> description: User visible long sound card name > >> > >> - pin-switches: > >> - description: List of widget names for which pin switches should be created. > >> - $ref: /schemas/types.yaml#/definitions/string-array > >> - > >> - widgets: > >> - description: User specified audio sound widgets. > >> - $ref: /schemas/types.yaml#/definitions/non-unique-string-array > >> - > > > > These two properties are also valid and supported on all newer > > platforms, please keep them here! There are certain use cases where > > these are needed independent of the platform, e.g. to control an analog > > switch or mux connected to speaker or headphone outputs. > > > > I agree that it is cleaner to move the IO muxing to a new schema though. > > Perhaps we could define something like a shared qcom,sndcard-common.yaml > > schema to avoid duplication for these generic properties? In the Linux > > driver, these are handled for all platforms in sound/soc/qcom/common.c. > > This was added to the common driver code but it does not mean it is > reasonable binding. I don't understand why for example we even accept > here aux-devs, instead of putting them into one of DAI links. > The auxiliary devices (typically analog audio components) are not necessarily related to one particular digital audio interface link. It is typically the case (e.g. an analog speaker amplifier connected in parallel to the headphone output of one of the codecs), but I don't think we can assume that as a general rule. There are often multiple DAI links that go to one codec and then it might be tricky to decide which of the DAI links the aux-dev belongs to. > The pin-switches and widgets could be used, but are they? The only valid > argument to keep them is that you added them to common driver code. These go hand in hand with the aux-devs property. If you have multiple analog audio components connected to a codec output (e.g. an analog speaker amplifier connected to the codec headphone output) then the pin-switches/widgets describe that the output paths (speaker and headphones) should be separately controllable. The alternative for pin-switches and widgets in the DT is to hardcode them in the ASoC board/machine driver with a separate board-specific compatible. Personally, I would prefer to keep the machine driver specific to the SoC instead of having definitions for each and every board. Thanks, Stephan
