From: Vlad Karpovich <vkarpovi@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] ASoC: cs34l45: Hibernation support
Date: Thu, 2 Mar 2023 14:03:29 -0600 [thread overview]
Message-ID: <c7d98128-32ce-9a63-7dae-2f4b735d95e9@opensource.cirrus.com> (raw)
In-Reply-To: <1f9fd2b8-f5d5-4a9c-8c52-63386c85101d@sirena.org.uk>
On 3/2/23 12:08, Mark Brown wrote:
> On Thu, Mar 02, 2023 at 11:59:05AM -0600, Vlad Karpovich wrote:
>> The CS35L45 features a low-power Hibernation State. In this state, all
>> register contents are lost, but the contents of
>> RAM are retained. In the Hibernation State, only always-on digital functions
>> to support wake-up are enabled.
>> Entry to this state is achieved via the register interface (either by an
>> external driver using the control port, or the
>> programmable DSP). Exit from this state is triggered by activity on device
>> GPIO pins, intended SPI transaction, or I2C
>> transaction with intended slave address
> OK, so it's essentially just a faster mechanism for bringing the device
> out of runtime suspend?
I don't think it is a faster way since it requires interaction with DSP
and restoring all wiped registers.
But it saves a some power comparing a low power state in the current driver
> I would suggest doing something in the code to
> clarify that this is not the same thing as system level hibernation,
> having references to hibernate in the driver is likely to lead to
> confusion down the line.
The feature is named hibernation in the data sheet. Renaming it in the
driver will add confusing for the driver user.
> I'd also include a bit more description in the
> commit message too.
I will do in next version.
> Please don't top post, reply in line with needed context. This allows
> readers to readily follow the flow of conversation and understand what
> you are talking about and also helps ensure that everything in the
> discussion is being addressed.
Thanks. I will do.
prev parent reply other threads:[~2023-03-02 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302171154.2342527-1-vkarpovi@opensource.cirrus.com>
[not found] ` <20230302171154.2342527-5-vkarpovi@opensource.cirrus.com>
2023-03-02 17:19 ` Mark Brown
2023-03-02 17:59 ` Vlad Karpovich
2023-03-02 18:08 ` Mark Brown
2023-03-02 20:03 ` Vlad Karpovich [this message]
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=c7d98128-32ce-9a63-7dae-2f4b735d95e9@opensource.cirrus.com \
--to=vkarpovi@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--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®