From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthijs van Duin Subject: Re: [PATCH 5/7] ARM: dts: Add nodes for missing omap4 interconnect target modules Date: Thu, 12 Oct 2017 10:40:30 +0200 Message-ID: <20171012084030.lshobr3ewu3t5goc@squirrel.local> References: <20170929223411.9691-1-tony@atomide.com> <20170929223411.9691-6-tony@atomide.com> <20171011165850.jnaievrgcszcawh3@earth> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Peter Ujfalusi Cc: Sebastian Reichel , Tony Lindgren , linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, =?iso-8859-1?Q?Beno=EEt?= Cousson , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Laurent Pinchart , Liam Girdwood , Mark Brown , Mark Rutland , Mauro Carvalho Chehab , Nishanth Menon , Paul Walmsley , Rob Herring , Sakari Ailus , Tero Kristo , Tomi Valkeinen List-Id: devicetree@vger.kernel.org On Thu, Oct 12, 2017 at 09:07:55AM +0300, Peter Ujfalusi wrote: > I don't see much benefit of using McASP on OMAP4, only drawbacks... It > lacks AFIFO so it is prone to underrun and if it underruns you need to > reset McASP. Been there with the Samsung Galaxy Nexus. AESS/ATC isn't able to consistently respond to a DMA request within 20 us ? Strange.. I would have expected it to have no trouble with that. (And presumably so did TI, or they would have included AFIFO?) > I wonder how Motorola is using the McASP as the OMAP4 version > (officially) does not support I2S. Hmm? I checked the omap4430 TRM and I don't see that mentioned. It seems to have pins for i2s transmit: abe_mcasp_axr O Audio transmit data abe_mcasp_aclkx O Transmit bit clock abe_mcasp_ahclkx O Transmit high-frequency master clock abe_mcasp_afsx O Transmit frame synchronization abe_mcasp_amute O Mute out to external abe_mcasp_amutein I Mute in from external If it supported s/pdif tx only, then all of these except axr would be useless. Matthijs -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: matthijsvanduin@gmail.com (Matthijs van Duin) Date: Thu, 12 Oct 2017 10:40:30 +0200 Subject: [PATCH 5/7] ARM: dts: Add nodes for missing omap4 interconnect target modules In-Reply-To: References: <20170929223411.9691-1-tony@atomide.com> <20170929223411.9691-6-tony@atomide.com> <20171011165850.jnaievrgcszcawh3@earth> Message-ID: <20171012084030.lshobr3ewu3t5goc@squirrel.local> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Oct 12, 2017 at 09:07:55AM +0300, Peter Ujfalusi wrote: > I don't see much benefit of using McASP on OMAP4, only drawbacks... It > lacks AFIFO so it is prone to underrun and if it underruns you need to > reset McASP. Been there with the Samsung Galaxy Nexus. AESS/ATC isn't able to consistently respond to a DMA request within 20 us ? Strange.. I would have expected it to have no trouble with that. (And presumably so did TI, or they would have included AFIFO?) > I wonder how Motorola is using the McASP as the OMAP4 version > (officially) does not support I2S. Hmm? I checked the omap4430 TRM and I don't see that mentioned. It seems to have pins for i2s transmit: abe_mcasp_axr O Audio transmit data abe_mcasp_aclkx O Transmit bit clock abe_mcasp_ahclkx O Transmit high-frequency master clock abe_mcasp_afsx O Transmit frame synchronization abe_mcasp_amute O Mute out to external abe_mcasp_amutein I Mute in from external If it supported s/pdif tx only, then all of these except axr would be useless. Matthijs