public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Banajit Goswami <bgoswami@quicinc.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Adam Skladowski <a39.skl@gmail.com>,
	Stephan Gerhold <stephan.gerhold@linaro.org>
Subject: Re: [PATCH] ASoC: dt-bindings: qcom,apq8016-sbc-sndcard: move to separate binding
Date: Sun, 28 Jul 2024 12:30:12 +0200	[thread overview]
Message-ID: <3d9f76c1-2e14-43dc-b438-5fac94ffc73e@kernel.org> (raw)
In-Reply-To: <ZqVXUI37fNB5D0DM@gerhold.net>

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@gmail.com>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>> .../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 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.

Best regards,
Krzysztof


  reply	other threads:[~2024-07-28 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23  8:33 [PATCH] ASoC: dt-bindings: qcom,apq8016-sbc-sndcard: move to separate binding Krzysztof Kozlowski
2024-07-23 21:16 ` Rob Herring (Arm)
2024-07-27 20:23 ` Stephan Gerhold
2024-07-28 10:30   ` Krzysztof Kozlowski [this message]
2024-07-30 10:30     ` Stephan Gerhold
2024-07-30 10:35       ` Mark Brown
2024-07-29 17:17 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3d9f76c1-2e14-43dc-b438-5fac94ffc73e@kernel.org \
    --to=krzk@kernel.org \
    --cc=a39.skl@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgoswami@quicinc.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=stephan.gerhold@linaro.org \
    --cc=stephan@gerhold.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox