From: Luca Weiss <luca.weiss@fairphone.com>
To: Weidong Wang <wangweidong.a@awinic.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Luca Weiss <luca.weiss@fairphone.com>
Subject: [PATCH v2 0/2] Remove reset GPIO for AW88261
Date: Mon, 02 Oct 2023 16:00:10 +0200 [thread overview]
Message-ID: <20231002-aw88261-reset-v2-0-837cb1e7b95c@fairphone.com> (raw)
The AW88261 chip doesn't have a reset gpio, so remove it from the
bindings and from the driver.
Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
---
Changes in v2:
- Include dt-bindings change
- Link to v1: https://lore.kernel.org/r/20230929-aw88261-reset-v1-1-fcbce194a823@fairphone.com
---
Luca Weiss (2):
ASoC: dt-bindings: awinic,aw88395: Remove reset-gpios from AW88261
ASoC: codecs: aw88261: Remove non-existing reset gpio
.../devicetree/bindings/sound/awinic,aw88395.yaml | 16 ++++++++++++----
sound/soc/codecs/aw88261.c | 15 ---------------
2 files changed, 12 insertions(+), 19 deletions(-)
---
base-commit: df964ce9ef9fea10cf131bf6bad8658fde7956f6
change-id: 20230929-aw88261-reset-7e00d9e25952
Best regards,
--
Luca Weiss <luca.weiss@fairphone.com>
next reply other threads:[~2023-10-02 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:00 Luca Weiss [this message]
2023-10-02 14:00 ` [PATCH v2 1/2] ASoC: dt-bindings: awinic,aw88395: Remove reset-gpios from AW88261 Luca Weiss
2023-10-02 14:00 ` [PATCH v2 2/2] ASoC: codecs: aw88261: Remove non-existing reset gpio Luca Weiss
2023-10-03 17:08 ` [PATCH v2 0/2] Remove reset GPIO for AW88261 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=20231002-aw88261-reset-v2-0-837cb1e7b95c@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=wangweidong.a@awinic.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).