From: Mark Brown <broonie@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
broonie@kernel.org, lgirdwood@gmail.com,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, jsarha@ti.com, robh+dt@kernel.org,
misael.lopez@ti.com, alsa-devel@alsa-project.org
Subject: Applied "ASoC: davinci-mcasp: Document GPIO support" to the asoc tree
Date: Fri, 4 Jan 2019 17:08:35 +0000 (GMT) [thread overview]
Message-ID: <20190104170835.554E711270A3@debutante.sirena.org.uk> (raw)
In-Reply-To: <20190103140552.29809-3-peter.ujfalusi@ti.com>
The patch
ASoC: davinci-mcasp: Document GPIO support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
From 4664b94c98b4f9fdd3845da41d5c65288e59c66c Mon Sep 17 00:00:00 2001
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
Date: Thu, 3 Jan 2019 16:05:51 +0200
Subject: [PATCH] ASoC: davinci-mcasp: Document GPIO support
McASP pins can be used as GPIO, add optional section to enable GPIO support
for McASP.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
.../bindings/sound/davinci-mcasp-audio.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt b/Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt
index b279b6072bd5..a58f79f5345c 100644
--- a/Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt
+++ b/Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt
@@ -45,6 +45,23 @@ Optional properties:
- fck_parent : Should contain a valid clock name which will be used as parent
for the McASP fck
+Optional GPIO support:
+If any McASP pin need to be used as GPIO then the McASP node must have:
+...
+ gpio-controller
+ #gpio-cells = <2>;
+...
+
+When requesting a GPIO, the first parameter is the PIN index in McASP_P*
+registers.
+For example to request the AXR2 pin of mcasp8:
+function-gpios = <&mcasp8 2 0>;
+
+Or to request the ACLKR pin of mcasp8:
+function-gpios = <&mcasp8 29 0>;
+
+For generic gpio information, please refer to bindings/gpio/gpio.txt
+
Example:
mcasp0: mcasp0@1d00000 {
--
2.20.1
next prev parent reply other threads:[~2019-01-04 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 14:05 [PATCH 0/3] ASoC: ti: davinci-mcasp: GPIO mode support for pins Peter Ujfalusi
2019-01-03 14:05 ` [PATCH 1/3] ASoC: ti: davinci-mcasp: Move context save/restore to runtime_pm callbacks Peter Ujfalusi
2019-01-04 17:08 ` Applied "ASoC: ti: davinci-mcasp: Move context save/restore to runtime_pm callbacks" to the asoc tree Mark Brown
2019-01-03 14:05 ` [PATCH 2/3] bindings: sound: davinci-mcasp: Document GPIO support Peter Ujfalusi
2019-01-04 17:08 ` Mark Brown [this message]
2019-01-07 12:24 ` Applied "ASoC: davinci-mcasp: Document GPIO support" to the asoc tree Mark Brown
2019-01-07 12:25 ` Mark Brown
2019-01-07 12:30 ` Mark Brown
2019-01-03 14:05 ` [PATCH 3/3] ASoC: ti: davinci-mcasp: Add support for GPIO mode of the pins Peter Ujfalusi
2019-01-04 17:08 ` Applied "ASoC: ti: davinci-mcasp: Add support for GPIO mode of the pins" to the asoc tree Mark Brown
2019-01-07 12:24 ` Mark Brown
2019-01-07 12:25 ` Mark Brown
2019-01-07 12:30 ` 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=20190104170835.554E711270A3@debutante.sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.com \
--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
all inboxes | Powered by JetHome®