From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: yung-chuan.liao@linux.intel.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Support clock stop mode 1 if enabled in ACPI
Date: Wed, 11 Mar 2026 15:58:35 +0000 [thread overview]
Message-ID: <c6b8c5e8-fdb6-45a9-aaab-d028e87a90ea@opensource.cirrus.com> (raw)
In-Reply-To: <5e12ba28-de41-466c-ae58-aaa32c72955b@sirena.org.uk>
On 11/03/2026 3:50 pm, Mark Brown wrote:
> On Wed, Mar 11, 2026 at 03:34:54PM +0000, Richard Fitzgerald wrote:
>> On 11/03/2026 3:30 pm, Mark Brown wrote:
>
>>> Hrm, OK - the property seems to be confusingly named and defined :( Can
>>> it have any values other than 0 and 1?
>
>> It's part of the SoundWire spec. We have to follow it.
>
>> The current spec says:
>
>> mipi-sdw-clock-stop-mode1-supported
>> This optional Boolean Property shall indicate whether or not Clock-stop
>> is supported on this Device.
>> Integer (Boolean)
>> Values:
>> False (zero): Clock-stop mode1 is not supported on this Device.
>> True (nonzero): Clock-stop mode1 is supported on this Device.
>
> Oh dear, cute enterprise nonsense hacks :(
The ACPI spec says that each property must be a {key,value} pair.
If you always need a value there's the possibility that someone will
create it with value 0 and expect that to mean false. So relying on its
presence to indicate true is dodgy, safer to define that the value
has meaning.
next prev parent reply other threads:[~2026-03-11 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 14:21 Richard Fitzgerald
2026-03-11 15:03 ` Mark Brown
2026-03-11 15:17 ` Richard Fitzgerald
2026-03-11 15:30 ` Mark Brown
2026-03-11 15:34 ` Richard Fitzgerald
2026-03-11 15:50 ` Mark Brown
2026-03-11 15:58 ` Richard Fitzgerald [this message]
2026-03-11 16:09 ` Mark Brown
2026-03-11 18:56 ` Mark Brown
2026-03-14 21:58 ` 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=c6b8c5e8-fdb6-45a9-aaab-d028e87a90ea@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=yung-chuan.liao@linux.intel.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®