From: neil.armstrong@linaro.org
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Banajit Goswami <bgoswami@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] ASoC: codecs: Add WCD939x Codec driver
Date: Wed, 29 Nov 2023 16:12:18 +0100 [thread overview]
Message-ID: <0140f49d-c463-4011-8159-f4e56466e6bd@linaro.org> (raw)
In-Reply-To: <eaa034cb-06e8-4204-befa-4389bcb7d9e8@linaro.org>
On 29/11/2023 14:46, Konrad Dybcio wrote:
> On 28.11.2023 16:01, Neil Armstrong wrote:
>> On 25/11/2023 13:07, Konrad Dybcio wrote:
>>
>> <snip>
>>
>>>> +
>>>> +static int wcd939x_io_init(struct snd_soc_component *component)
>>>> +{
>>>> + snd_soc_component_write_field(component, WCD939X_ANA_BIAS,
>>>> + WCD939X_BIAS_ANALOG_BIAS_EN, 1);
>>> All of these values are BIT()s or 2-4 ORed BIT()s, can you check what they
>>> mean?
>>>
>>> Same for almost all other snd_soc_component_ write/modify functions
>>
>> It uses snd_soc_component_write_field() with is the same as
>> regmap_write_bits(REGISTER, REGISTER_MASK,
>> FIELD_PREP(REGISTER_MASK, value);
>>
>> So the 1 mean write in enable mask in this case, and mask is single bit,
>> read it exactly like if it was using FIELD_PREP(), but even for BITs.
>>
>> I did check every single snd_soc_component_write_field() so far to check
>> it matches.
>>
>> Or it's another question ?
> What I wanted to ask is whether it's possible to #define these magic
> values within these fields
OK, so most of writes are to boolean enable bits, I can use true/false
instead of 0 & 1 for those, would it be more readable ?
For the rest, those a integer values to a field, those are not bitmasks
and I do not have the definition of the values.
I did a full cleanup and tried to define as much as possible,
there were still lot of places where not defined bitmasks we used,
but there's still some integer values, but I think it's acceptable.
Neil
>
> Konrad
next prev parent reply other threads:[~2023-11-29 15:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:49 [PATCH 0/5] ASoC: codecs: add support for WCD939x Codec Neil Armstrong
2023-11-23 14:49 ` [PATCH 1/5] ASoC: dt-bindings: qcom,wcd938x: move out common properties Neil Armstrong
2023-11-24 8:29 ` Krzysztof Kozlowski
2023-11-23 14:49 ` [PATCH 2/5] ASoC: dt-bindings: document WCD939x Audio Codec Neil Armstrong
2023-11-24 8:33 ` Krzysztof Kozlowski
2023-11-28 8:59 ` Neil Armstrong
2023-11-28 9:04 ` Krzysztof Kozlowski
2023-11-28 9:14 ` neil.armstrong
2023-11-28 9:17 ` Krzysztof Kozlowski
2023-11-28 9:19 ` neil.armstrong
2023-11-23 14:49 ` [PATCH 3/5] ASoC: codec: wcd-mbhc-v2: add support when connected behind an USB-C audio mux Neil Armstrong
2023-11-23 17:38 ` Mark Brown
2023-11-28 8:59 ` Neil Armstrong
2023-11-23 14:49 ` [PATCH 4/5] ASoC: codecs: Add WCD939x Soundwire slave driver Neil Armstrong
2023-11-23 17:43 ` Mark Brown
2023-11-28 9:09 ` Neil Armstrong
2023-11-28 12:47 ` Mark Brown
2023-11-28 13:19 ` Neil Armstrong
2023-11-25 11:55 ` Konrad Dybcio
2023-11-28 9:16 ` Neil Armstrong
2023-11-29 13:45 ` Konrad Dybcio
2023-11-23 14:49 ` [PATCH 5/5] ASoC: codecs: Add WCD939x Codec driver Neil Armstrong
2023-11-24 10:19 ` Mark Brown
2023-11-28 9:18 ` Neil Armstrong
2023-11-25 12:07 ` Konrad Dybcio
2023-11-28 9:22 ` Neil Armstrong
2023-11-28 15:01 ` Neil Armstrong
2023-11-29 13:46 ` Konrad Dybcio
2023-11-29 15:12 ` neil.armstrong [this message]
2023-11-29 18:21 ` Konrad Dybcio
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=0140f49d-c463-4011-8159-f4e56466e6bd@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@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=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®