From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chancel Liu <chancel.liu@nxp.com>, Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/4] ASoC: dt-bindings: wlf,wm8524: Add a property to specify power up sequency time
Date: Fri, 24 Feb 2023 11:59:26 +0100 [thread overview]
Message-ID: <0827a05c-117d-3d4c-2e3a-f8d80e256ca0@linaro.org> (raw)
In-Reply-To: <VI1PR04MB4222996DB8494FD14A1D5FCEE3A89@VI1PR04MB4222.eurprd04.prod.outlook.com>
On 24/02/2023 11:56, Chancel Liu wrote:
>> On Wed, Feb 22, 2023 at 07:39:43PM +0800, Chancel Liu wrote:
>>> This property specifies power up to audio out time. It's necessary
>>> beacause this device has to wait some time before ready to output
>>> audio after MCLK, BCLK and MUTE=1 are enabled. For more details about
>>> the timing constraints, please refer to WTN0302 on
>>> https://www.cirrus.com/products/wm8524/
>>
>> According to that the delay is a property of MCLK and the sample rate rather
>> than a per board constant, it shouldn't be in DT but rather the driver should
>> figure out the required delay on each startup.
>
> I can't agree with you more. From the power up to audio out timing table in
> WTN0302, the delay depends on sample rate and MCLK. Driver should calculate it
> rather than read it from DT. However as I mentioned in my last email, values in
> the table seem not accurate for all systems. It's a kind of compromise to get
> the value from DT. Do other codecs have a similar situation?
DT is for hardware properties, not for software compromises.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-24 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:39 [PATCH 1/4] ASoC: dt-bindings: wlf,wm8524: Convert to json-schema Chancel Liu
2023-02-22 11:39 ` [PATCH 2/4] ASoC: dt-bindings: wlf,wm8524: Add a property to specify power up sequency time Chancel Liu
2023-02-22 12:42 ` Krzysztof Kozlowski
2023-02-24 10:54 ` Chancel Liu
2023-02-24 11:00 ` Krzysztof Kozlowski
2023-02-27 9:06 ` Chancel Liu
2023-02-22 12:50 ` Mark Brown
2023-02-24 10:56 ` Chancel Liu
2023-02-24 10:59 ` Krzysztof Kozlowski [this message]
2023-02-22 11:39 ` [PATCH 3/4] ASoC: wm8524: Correct the MUTE setting while power up/down Chancel Liu
2023-02-22 11:39 ` [PATCH 4/4] ASoC: wm8524: Delay some time to follow power up sequency Chancel Liu
2023-02-22 12:48 ` Mark Brown
2023-02-24 10:54 ` Chancel Liu
2023-02-24 12:30 ` Mark Brown
2023-02-27 9:07 ` Chancel Liu
2023-02-22 12:36 ` [PATCH 1/4] ASoC: dt-bindings: wlf,wm8524: Convert to json-schema Krzysztof Kozlowski
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=0827a05c-117d-3d4c-2e3a-f8d80e256ca0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chancel.liu@nxp.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).