From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH v2 0/4] ASoC: cs42l42: Remove redundant code
Date: Tue, 16 Nov 2021 16:38:57 +0000 [thread overview]
Message-ID: <20211116163901.45390-1-rf@opensource.cirrus.com> (raw)
- Remove field writes in regmap_update_bits() calls where the code
intends that the field value is not changed.
- Remove unnecessary complexity from reporting jack unplug event
- Remove a PLL config value member that was introduced in a bugfix
but made redundant by a later bugfix.
Richard Fitzgerald (4):
ASoC: cs42l42: Remove redundant writes to DETECT_MODE
ASoC: cs42l42: Remove redundant writes to RS_PLUG/RS_UNPLUG masks
ASoC: cs42l42: Simplify reporting of jack unplug
ASoC: cs42l42: Remove redundant pll_divout member
sound/soc/codecs/cs42l42.c | 42 +++++++-----------------------------------
sound/soc/codecs/cs42l42.h | 1 -
2 files changed, 7 insertions(+), 36 deletions(-)
--
2.11.0
next reply other threads:[~2021-11-16 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:38 Richard Fitzgerald [this message]
2021-11-16 16:38 ` [PATCH v2 1/4] ASoC: cs42l42: Remove redundant writes to DETECT_MODE Richard Fitzgerald
2021-11-16 16:38 ` [PATCH v2 2/4] ASoC: cs42l42: Remove redundant writes to RS_PLUG/RS_UNPLUG masks Richard Fitzgerald
2021-11-16 16:39 ` [PATCH v2 3/4] ASoC: cs42l42: Simplify reporting of jack unplug Richard Fitzgerald
2021-11-16 16:39 ` [PATCH v2 4/4] ASoC: cs42l42: Remove redundant pll_divout member Richard Fitzgerald
2021-11-17 22:31 ` [PATCH v2 0/4] ASoC: cs42l42: Remove redundant code 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=20211116163901.45390-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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®