From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <broonie@kernel.org>, <lgirdwood@gmail.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
kuninori.morimoto.gx@renesas.com, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: [alsa-devel] [PATCH 0/2] ASoC: pcm3168a: Update the reset GPIO handling
Date: Wed, 20 Nov 2019 15:17:51 +0200 [thread overview]
Message-ID: <20191120131753.6831-1-peter.ujfalusi@ti.com> (raw)
Hi,
Switch the rst-gpios to generic reset-gpios as suggested by Rob.
Based on other threads around GPIOs, revise the GPIO active vs assert/deassert
configuration: The RST pin is a reset pin and it is active low.
Regards,
Peter
---
Peter Ujfalusi (2):
ASoC: dt-bindings: pcm3168a: Update the optional RST gpio for clarity
ASoC: pcm3168a: Update the RST gpio handling to align with
documentation
.../devicetree/bindings/sound/ti,pcm3168a.txt | 9 +++++----
sound/soc/codecs/pcm3168a.c | 20 ++++++++++++++-----
2 files changed, 20 insertions(+), 9 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-11-20 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 13:17 Peter Ujfalusi [this message]
2019-11-20 13:17 ` [alsa-devel] [PATCH 1/2] ASoC: dt-bindings: pcm3168a: Update the optional RST gpio for clarity Peter Ujfalusi
2019-11-20 17:18 ` [alsa-devel] Applied "ASoC: dt-bindings: pcm3168a: Update the optional RST gpio for clarity" to the asoc tree Mark Brown
2019-11-20 13:17 ` [alsa-devel] [PATCH 2/2] ASoC: pcm3168a: Update the RST gpio handling to align with documentation Peter Ujfalusi
2019-11-20 17:18 ` [alsa-devel] Applied "ASoC: pcm3168a: Update the RST gpio handling to align with documentation" to the asoc tree 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=20191120131753.6831-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).