public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Astrid Rost <astridr@axis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Astrid Rost <astrid.rost@axis.com>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Dylan Reid <dgreid@chromium.org>
Cc: <kernel@axis.com>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] ASoC: dt-bindings: ti,ts3a227e.yaml: add jack-type
Date: Mon, 23 Jan 2023 09:39:29 +0100	[thread overview]
Message-ID: <0b0c0030-3587-5501-c7b2-eccbbe4551e0@axis.com> (raw)
In-Reply-To: <2d05a943-3510-5ee9-9906-247a6344190a@linaro.org>

Hello Krzysztof,

On 1/22/23 15:16, Krzysztof Kozlowski wrote:
> On 20/01/2023 11:25, Astrid Rost wrote:
>> Add jack-type: Bitmap value of snd_jack_type to allow combining
>> card drivers to create a jack for it.
> 
> Subject: drop "yaml". We do not filename extensions to subject prefix.
> Nowhere.
> 

yes, true.

>>
>> Signed-off-by: Astrid Rost <astrid.rost@axis.com>
>> ---
>>   Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml | 8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml b/Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml
>> index 785930658029..1d949b805f98 100644
>> --- a/Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml
>> +++ b/Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml
>> @@ -27,6 +27,14 @@ properties:
>>     interrupts:
>>       maxItems: 1
>>   
>> +  jack-type:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    description: Bitmap value of snd_jack_type to allow combining
>> +      card drivers to create a jack for it. Supported is
> 
> Why the device would once support (allow) headphone and once not? Device
> either always supports them or never...
> 

If a device has two connectors (pink and green), one for the microphone 
and one for the headset. It would be easier to see from the available 
events, which is which. But of course it is possible to give it good names.
My first approach was, that it returned all supported types, so no 
devicetree change needed. But by colleges agreed that it would be nice
to remove unused flags. I am happy to remove it and someone who requires 
it can add it.

>> +        1 SND_JACK_HEADPHONE
>> +        2 SND_JACK_MICROPHONE
> 
> minimum and maximum

I do not understand this? It is a bitmap. I can put it as an
enum:
  - 1 # SND_JACK_HEADPHONE
  - 2 # SND_JACK_MICROPHONE
  - 3 # SND_JACK_HEADPHONE | SND_JACK_MICROPHONE
> 
>> +    default: 3
>> +
>>     ti,micbias:
>>       $ref: /schemas/types.yaml#/definitions/uint32
>>       description: Intended MICBIAS voltage (datasheet section 9.6.7).
> 
> Best regards,
> Krzysztof
> 

Thank you for your comments

Astrid

  reply	other threads:[~2023-01-23  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 10:25 [PATCH v2 0/4] ASoC: simple-card-utils: create jack inputs for aux_devs Astrid Rost
2023-01-20 10:25 ` [PATCH v2 1/4] ASoC: soc-component: add get_jack_type Astrid Rost
2023-01-20 10:25 ` [PATCH v2 2/4] ASoC: simple-card-utils: create jack inputs for aux_devs Astrid Rost
2023-01-20 10:25 ` [PATCH v2 3/4] ASoC: ts3a227e: add set_jack and get_jack_type Astrid Rost
2023-01-20 10:25 ` [PATCH v2 4/4] ASoC: dt-bindings: ti,ts3a227e.yaml: add jack-type Astrid Rost
2023-01-22 14:16   ` Krzysztof Kozlowski
2023-01-23  8:39     ` Astrid Rost [this message]
2023-01-23  9:05       ` Krzysztof Kozlowski
2023-01-23  9:19         ` Astrid Rost
2023-01-23 22:09   ` Rob Herring
2023-01-24  8:46     ` Astrid Rost

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=0b0c0030-3587-5501-c7b2-eccbbe4551e0@axis.com \
    --to=astridr@axis.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=astrid.rost@axis.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dgreid@chromium.org \
    --cc=kernel@axis.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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