Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	jarkko.nikula@bitmer.com, tony@atomide.com
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
	aaro.koskinen@iki.fi
Subject: [PATCH 1/5] ARM: dts: omap2420-n810: Enable McBSP2 for audio
Date: Thu, 26 Apr 2018 14:51:11 +0300	[thread overview]
Message-ID: <20180426115115.13744-2-peter.ujfalusi@ti.com> (raw)
In-Reply-To: <20180426115115.13744-1-peter.ujfalusi@ti.com>

McBSP2 is used with the tlv320aic33 codec for audio.
Pin mux change is needed to get the needed signals in/out from the SoC.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
---
 arch/arm/boot/dts/omap2420-n810.dts | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/arch/arm/boot/dts/omap2420-n810.dts b/arch/arm/boot/dts/omap2420-n810.dts
index 7c485fbfa535..4c412a480c3e 100644
--- a/arch/arm/boot/dts/omap2420-n810.dts
+++ b/arch/arm/boot/dts/omap2420-n810.dts
@@ -8,9 +8,26 @@
 	compatible = "nokia,n810", "nokia,n8x0", "ti,omap2420", "ti,omap2";
 };
 
+&omap2420_pmx {
+	mcbsp2_pins: mcbsp2_pins {
+		pinctrl-single,pins = <
+			OMAP2420_CORE_IOPAD(0x0124, PIN_INPUT | MUX_MODE1)	/* eac_ac_sclk.mcbsp2_clkx */
+			OMAP2420_CORE_IOPAD(0x0125, PIN_INPUT | MUX_MODE1)	/* eac_ac_fs.mcbsp2_fsx */
+			OMAP2420_CORE_IOPAD(0x0126, PIN_INPUT | MUX_MODE1)	/* eac_ac_din.mcbsp2_dr */
+			OMAP2420_CORE_IOPAD(0x0127, PIN_OUTPUT | MUX_MODE1)	/* eac_ac_dout.mcbsp2_dx */
+		>;
+	};
+};
+
 &i2c2 {
 	aic3x@18 {
 		compatible = "tlv320aic3x";
 		reg = <0x18>;
 	};
 };
+&mcbsp2 {
+	pinctrl-names = "default";
+	pinctrl-0 = <&mcbsp2_pins>;
+
+	status = "okay";
+};
-- 
Peter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2018-04-26 11:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 11:51 [PATCH 0/5] ARM/ASoC: omap: n810 audio support Peter Ujfalusi
2018-04-26 11:51 ` Peter Ujfalusi [this message]
2018-04-26 18:15   ` [PATCH 1/5] ARM: dts: omap2420-n810: Enable McBSP2 for audio Jarkko Nikula
2018-04-26 11:51 ` [PATCH 2/5] ARM: dts: omap2420-n810: Correct the audio codec (tlv320aic33) node Peter Ujfalusi
2018-04-26 18:15   ` Jarkko Nikula
2018-04-26 11:51 ` [PATCH 3/5] ASoC: omap: n810: Correct the card level dapm_route Peter Ujfalusi
2018-04-26 18:17   ` Jarkko Nikula
2018-04-27 10:59   ` Applied "ASoC: omap: n810: Correct the card level dapm_route" to the asoc tree Mark Brown
2018-04-26 11:51 ` [PATCH 4/5] ASoC: omap: n810: Correct the cpu_dai, platform and codec name Peter Ujfalusi
2018-04-26 18:17   ` Jarkko Nikula
2018-04-27 10:59   ` Applied "ASoC: omap: n810: Correct the cpu_dai, platform and codec name" to the asoc tree Mark Brown
2018-04-26 11:51 ` [PATCH 5/5] ASoC: omap: Remove OMAP_MUX dependency from Nokia N810 audio support Peter Ujfalusi
2018-04-26 12:54   ` Mark Brown
2018-04-26 13:01     ` Peter Ujfalusi
2018-04-26 13:03       ` Mark Brown
2018-04-26 13:06         ` Peter Ujfalusi
2018-04-26 13:08           ` 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=20180426115115.13744-2-peter.ujfalusi@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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