From: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Igor Opaniuk <igor.opaniuk@toradex.com>,
Oleksandr Suvorov <oleksandr.suvorov@toradex.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: [PATCH v1 5/6] ASoC: Define a set of DAPM pre/post-up events
Date: Tue, 21 May 2019 13:36:18 +0300 [thread overview]
Message-ID: <20190521103619.4707-6-oleksandr.suvorov@toradex.com> (raw)
In-Reply-To: <20190521103619.4707-1-oleksandr.suvorov@toradex.com>
Prepare to use SND_SOC_DAPM_PRE_POST_PMU definition to
reduce coming code size and make it more readable.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
---
include/sound/soc-dapm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git include/sound/soc-dapm.h include/sound/soc-dapm.h
index c00a0b8ade08..6c6694160130 100644
--- include/sound/soc-dapm.h
+++ include/sound/soc-dapm.h
@@ -353,6 +353,8 @@ struct device;
#define SND_SOC_DAPM_WILL_PMD 0x80 /* called at start of sequence */
#define SND_SOC_DAPM_PRE_POST_PMD \
(SND_SOC_DAPM_PRE_PMD | SND_SOC_DAPM_POST_PMD)
+#define SND_SOC_DAPM_PRE_POST_PMU \
+ (SND_SOC_DAPM_PRE_PMU | SND_SOC_DAPM_POST_PMU)
/* convenience event type detection */
#define SND_SOC_DAPM_EVENT_ON(e) \
--
2.20.1
--
Ciklum refers to one or more of Ciklum Group Holdings LTD. and its
subsidiaries and affiliates each of which is a legally separate entity.
Ciklum LLC is a limited liability company registered in Ukraine under
EDRPOU code 31902643, with its registered address at 12 Amosova St., 03680,
Kyiv, Ukraine.
The contents of this e-mail (including any attachments)
are confidential and may be legally privileged. If you are not the intended
recipient of this e-mail, please notify the sender immediately and then
delete it (including any attachments) from all your systems. Any
unauthorised use, reproduction, distribution, disclosure and/or
modification of this message and/or its contents are strictly prohibited.
We cannot guarantee that this e-mail is secure or error-free. Ciklum cannot
be held liable for any loss or damage caused by software viruses or
resulting from any use of or reliance on this email by anyone, other than
the intended addressee to the extent agreed in a contract for the matter to
which this email relates (if any). Messages sent to and from Ciklum may be
monitored; by replying to this e-mail you give your consent to such
monitoring. Notice: we do not accept service by e-mail of court
proceedings, other processes or formal notices of any kind without specific
prior written agreement. This email does not constitute a binding offer or
acceptance for Ciklum unless so set forth in a separate document.
next prev parent reply other threads:[~2019-05-21 10:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 10:36 [PATCH v1 0/6] VAG power control improvement for sgtl5000 codec Oleksandr Suvorov
2019-05-21 10:36 ` [PATCH v1 1/6] ASoC: sgtl5000: Fix definition of VAG Ramp Control Oleksandr Suvorov
2019-06-13 9:05 ` Marcel Ziswiler
2019-06-19 10:00 ` Oleksandr Suvorov
2019-06-24 11:10 ` Marcel Ziswiler
2019-05-21 10:36 ` [PATCH v1 2/6] ASoC: sgtl5000: add ADC mute control Oleksandr Suvorov
2019-06-13 9:05 ` Marcel Ziswiler
2019-05-21 10:36 ` [PATCH v1 3/6] ASoC: sgtl5000: Fix of unmute outputs on probe Oleksandr Suvorov
2019-06-13 9:05 ` Marcel Ziswiler
2019-05-21 10:36 ` [PATCH v1 4/6] ASoC: sgtl5000: Fix charge pump source assignment Oleksandr Suvorov
2019-06-13 9:06 ` Marcel Ziswiler
2019-05-21 10:36 ` Oleksandr Suvorov [this message]
2019-06-13 9:06 ` [PATCH v1 5/6] ASoC: Define a set of DAPM pre/post-up events Marcel Ziswiler
2019-05-21 10:36 ` [PATCH v1 6/6] ASoC: sgtl5000: Improve VAG power and mute control Oleksandr Suvorov
2019-06-13 9:06 ` Marcel Ziswiler
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=20190521103619.4707-6-oleksandr.suvorov@toradex.com \
--to=oleksandr.suvorov@toradex.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--cc=igor.opaniuk@toradex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.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;
as well as URLs for NNTP newsgroup(s).