From: "H. Nikolaus Schaller" <hns@goldelico.com> To: Peter Ujfalusi <peter.ujfalusi@gmail.com> Cc: Mark Brown <broonie@kernel.org>, tony@atomide.com, alsa-devel@alsa-project.org, lgirdwood@gmail.com, linux-omap@vger.kernel.org Subject: Re: [PATCH 0/5] ASoC: ti: davinci-mcasp: Fix the DIT mode and OMAP4 support Date: Mon, 5 Jul 2021 15:32:53 +0200 [thread overview] Message-ID: <E1C17C0D-1363-4109-89B3-A652A2B47703@goldelico.com> (raw) In-Reply-To: <20210704150450.20106-1-peter.ujfalusi@gmail.com> Hi Péter, > Am 04.07.2021 um 17:04 schrieb Peter Ujfalusi <peter.ujfalusi@gmail.com>: > > Hi, > > it has been on my todo list for several years to support McASP on OMAP4 devices. > For Galaxy Nexus we had an omap-mcasp driver (which was mostly a stripped down > davinci-mcasp driver) to support what was needed on that specific phone + it's > dock for S/PDIF (48KHz, 16bit, stereo). > > Not many (if any) device available to test the DIT mode of McASP. > I have used BeagleBone White (McASP1 AXR3 can be routed to a pin) to get the > S/PDIF mode working then PandaES for OMAP4 support (on PandaES the gpio_121 is > not used and the signal is routed to expansion J6 pin14) > > In theory the McASP in OMAP5 should be working after this series, but the OMAP5 > TRM is not public and I do not have one to check the addresses and see if there > is a way to test it on omap5-uevm. > > Mark, Tony: > The ASoC and dts patches can go via separate tree I felt that it is better if > they are together, at least initially. > > Nikolaus: fyi, this might be useful for Pyra? Yes, definitively. I just wonder how compatible it is with the "old" omap-mcasp driver we carry along for the Pyra: https://git.goldelico.com/?p=letux-kernel.git;a=blob;f=sound/soc/ti/omap-mcasp.c;h=24d839a24f34ec02456176744d3690016592b5a3;hb=7789ab635e56a2fd9fe04ca2e9ccfeaccb8e0f52 Does it now have additional functionality or robustness? And does it need changes of the OMAP5 device tree? And also important seems to be the ABE/AESS integration where we so far failed to make it work again on more recent kernels. Our most recent patch set is here: https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux/aess-v5 Anyways I am happy to see a little progress on the omap4/5 audio subsystem. BR and thanks, Nikolaus > > Regards, > Péter > --- > Peter Ujfalusi (5): > ASoC: ti: davinci-mcasp: Fix DIT mode support > ASoC: dt-bindings: davinci-mcasp: Add compatible string for OMAP4 > ASoC: ti: davinci-mcasp: Add support for the OMAP4 version of McASP > ARM: dts: omap4-l4-abe: Correct sidle modes for McASP > ARM: dts: omap4-l4-abe: Add McASP configuration > > .../bindings/sound/davinci-mcasp-audio.txt | 1 + > arch/arm/boot/dts/omap4-l4-abe.dtsi | 39 ++-- > include/linux/platform_data/davinci_asp.h | 1 + > sound/soc/ti/Kconfig | 1 + > sound/soc/ti/davinci-mcasp.c | 168 +++++++++++++++--- > 5 files changed, 168 insertions(+), 42 deletions(-) > > -- > 2.32.0 >
WARNING: multiple messages have this Message-ID (diff)
From: "H. Nikolaus Schaller" <hns@goldelico.com> To: Peter Ujfalusi <peter.ujfalusi@gmail.com> Cc: tony@atomide.com, alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>, lgirdwood@gmail.com, linux-omap@vger.kernel.org Subject: Re: [PATCH 0/5] ASoC: ti: davinci-mcasp: Fix the DIT mode and OMAP4 support Date: Mon, 5 Jul 2021 15:32:53 +0200 [thread overview] Message-ID: <E1C17C0D-1363-4109-89B3-A652A2B47703@goldelico.com> (raw) In-Reply-To: <20210704150450.20106-1-peter.ujfalusi@gmail.com> Hi Péter, > Am 04.07.2021 um 17:04 schrieb Peter Ujfalusi <peter.ujfalusi@gmail.com>: > > Hi, > > it has been on my todo list for several years to support McASP on OMAP4 devices. > For Galaxy Nexus we had an omap-mcasp driver (which was mostly a stripped down > davinci-mcasp driver) to support what was needed on that specific phone + it's > dock for S/PDIF (48KHz, 16bit, stereo). > > Not many (if any) device available to test the DIT mode of McASP. > I have used BeagleBone White (McASP1 AXR3 can be routed to a pin) to get the > S/PDIF mode working then PandaES for OMAP4 support (on PandaES the gpio_121 is > not used and the signal is routed to expansion J6 pin14) > > In theory the McASP in OMAP5 should be working after this series, but the OMAP5 > TRM is not public and I do not have one to check the addresses and see if there > is a way to test it on omap5-uevm. > > Mark, Tony: > The ASoC and dts patches can go via separate tree I felt that it is better if > they are together, at least initially. > > Nikolaus: fyi, this might be useful for Pyra? Yes, definitively. I just wonder how compatible it is with the "old" omap-mcasp driver we carry along for the Pyra: https://git.goldelico.com/?p=letux-kernel.git;a=blob;f=sound/soc/ti/omap-mcasp.c;h=24d839a24f34ec02456176744d3690016592b5a3;hb=7789ab635e56a2fd9fe04ca2e9ccfeaccb8e0f52 Does it now have additional functionality or robustness? And does it need changes of the OMAP5 device tree? And also important seems to be the ABE/AESS integration where we so far failed to make it work again on more recent kernels. Our most recent patch set is here: https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux/aess-v5 Anyways I am happy to see a little progress on the omap4/5 audio subsystem. BR and thanks, Nikolaus > > Regards, > Péter > --- > Peter Ujfalusi (5): > ASoC: ti: davinci-mcasp: Fix DIT mode support > ASoC: dt-bindings: davinci-mcasp: Add compatible string for OMAP4 > ASoC: ti: davinci-mcasp: Add support for the OMAP4 version of McASP > ARM: dts: omap4-l4-abe: Correct sidle modes for McASP > ARM: dts: omap4-l4-abe: Add McASP configuration > > .../bindings/sound/davinci-mcasp-audio.txt | 1 + > arch/arm/boot/dts/omap4-l4-abe.dtsi | 39 ++-- > include/linux/platform_data/davinci_asp.h | 1 + > sound/soc/ti/Kconfig | 1 + > sound/soc/ti/davinci-mcasp.c | 168 +++++++++++++++--- > 5 files changed, 168 insertions(+), 42 deletions(-) > > -- > 2.32.0 >
next prev parent reply other threads:[~2021-07-05 13:33 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-04 15:04 [PATCH 0/5] ASoC: ti: davinci-mcasp: Fix the DIT mode and OMAP4 support Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-04 15:04 ` [PATCH 1/5] ASoC: ti: davinci-mcasp: Fix DIT mode support Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-05 14:38 ` kernel test robot 2021-07-05 14:58 ` Péter Ujfalusi 2021-07-05 14:58 ` Péter Ujfalusi 2021-07-05 15:50 ` Mark Brown 2021-07-05 15:50 ` Mark Brown 2021-07-04 15:04 ` [PATCH 2/5] ASoC: dt-bindings: davinci-mcasp: Add compatible string for OMAP4 Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-04 15:04 ` [PATCH 3/5] ASoC: ti: davinci-mcasp: Add support for the OMAP4 version of McASP Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-04 15:04 ` [PATCH 4/5] ARM: dts: omap4-l4-abe: Correct sidle modes for McASP Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-04 15:04 ` [PATCH 5/5] ARM: dts: omap4-l4-abe: Add McASP configuration Peter Ujfalusi 2021-07-04 15:04 ` Peter Ujfalusi 2021-07-05 13:32 ` H. Nikolaus Schaller [this message] 2021-07-05 13:32 ` [PATCH 0/5] ASoC: ti: davinci-mcasp: Fix the DIT mode and OMAP4 support H. Nikolaus Schaller 2021-07-05 14:10 ` Péter Ujfalusi 2021-07-05 14:10 ` Péter Ujfalusi 2021-07-05 15:33 ` H. Nikolaus Schaller 2021-07-05 15:33 ` H. Nikolaus Schaller
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=E1C17C0D-1363-4109-89B3-A652A2B47703@goldelico.com \ --to=hns@goldelico.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linux-omap@vger.kernel.org \ --cc=peter.ujfalusi@gmail.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.