Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
	srini@kernel.org, lgirdwood@gmail.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, krzysztof.kozlowski@linaro.org,
	neil.armstrong@linaro.org
Subject: Re: [PATCH v2 2/8] ASoC: codecs: wcd: add common helper for wcd codecs
Date: Fri, 5 Sep 2025 08:03:49 +0100	[thread overview]
Message-ID: <f6a631bb-d17d-4eba-adfc-4db08540f5a0@oss.qualcomm.com> (raw)
In-Reply-To: <kmm4e5bg7uehmlsgrfhzo4agr6ga6d5gxtpxq5sg4t3wql5p6m@llwyz4kzsj7y>

Sorry for some reason I did not notice this email!.

On 8/22/25 12:18 PM, Dmitry Baryshkov wrote:
>> + */
>> +
>> +#ifndef __WCD_COMMON_H__
>> +#define __WCD_COMMON_H___
>> +
>> +#define WCD_MIN_MICBIAS_MV	1000
>> +#define WCD_DEF_MICBIAS_MV	1800
>> +#define WCD_MAX_MICBIAS_MV	2850
> These do not belong to a public header.


All the wcd codecs have same MICBIAS circuitry, this is the internal
micbias circuit we are talking about here.

Actual micbias value comes from device tree, but these are min/max
ranges that are supported by all WCD codecs.

Why do you think it should not be part of common header?

--srini
> 
>> +#define WCD_MAX_MICBIAS		4
>> +
>> +struct wcd_common {
>> +	struct device *dev;
>> +	int max_bias;
>> +	u32 micb_mv[WCD_MAX_MICBIAS];
>> +	u32 micb_vout[WCD_MAX_MICBIAS];
>> +};
>> +
>> +int wcd_get_micb_vout_ctl_val(struct device *dev, u32 micb_mv);
>> +int wcd_dt_parse_micbias_info(struct wcd_common *common);
>> +
>> +#endif /* __WCD_COMMON_H___  */


  reply	other threads:[~2025-09-05  7:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 10:49 [PATCH v2 0/8] ASoC: codecs: wcd93xxx: remove code duplication Srinivas Kandagatla
2025-08-22 10:49 ` [PATCH v2 1/8] ASoC: codecs: wcd937x: set the comp soundwire port correctly Srinivas Kandagatla
2025-08-22 10:49 ` [PATCH v2 2/8] ASoC: codecs: wcd: add common helper for wcd codecs Srinivas Kandagatla
2025-08-22 11:18   ` Dmitry Baryshkov
2025-09-05  7:03     ` Srinivas Kandagatla [this message]
2025-09-05 13:50       ` Dmitry Baryshkov
2025-09-05 13:59         ` Srinivas Kandagatla
2025-08-22 10:49 ` [PATCH v2 3/8] ASoC: codecs: wcd-common: move WCD_SDW_CH to common Srinivas Kandagatla
2025-08-22 11:21   ` Dmitry Baryshkov
2025-08-22 10:49 ` [PATCH v2 4/8] ASoC: codecs: wcd-common: move component ops " Srinivas Kandagatla
2025-08-22 11:28   ` Dmitry Baryshkov
2025-08-22 10:49 ` [PATCH v2 5/8] ASoC: codecs: wcd939x: get regmap directly Srinivas Kandagatla
2025-08-22 10:49 ` [PATCH v2 6/8] ASoC: codecs: wcd-common: move status_update callback to common Srinivas Kandagatla
2025-08-22 11:32   ` Dmitry Baryshkov
2025-08-22 10:49 ` [PATCH v2 7/8] ASoC: codecs: wcd938x: get regmap directly Srinivas Kandagatla
2025-08-22 10:49 ` [PATCH v2 8/8] ASoC: codecs: wcd937x: " Srinivas Kandagatla

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=f6a631bb-d17d-4eba-adfc-4db08540f5a0@oss.qualcomm.com \
    --to=srinivas.kandagatla@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --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=neil.armstrong@linaro.org \
    --cc=perex@perex.cz \
    --cc=srini@kernel.org \
    --cc=tiwai@suse.com \
    /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