[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160321202107.GO9329@atomide.com>
Date: Mon, 21 Mar 2016 13:21:07 -0700
From: Tony Lindgren <tony@...mide.com>
To: Peter Ujfalusi <peter.ujfalusi@...com>
Cc: Paul Walmsley <paul@...an.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jarkko Nikula <jarkko.nikula@...mer.com>,
Tero Kristo <t-kristo@...com>, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH 0/3] ARM: OMAP3: Fix McBSP2/3 hwmod setup for sidetone
Hi,
* Peter Ujfalusi <peter.ujfalusi@...com> [160321 01:39]:
>
> This is also interesting:
> McBSP2 sidetone is in region 39 and 40 (module and L4 interconnect) which is
> unique in case of OMAP34xx and OMAP35xx, but it is overlapping with GPIO6 on
> OMAP36xx. Not sure what are the implications.
Hmm GPIO6 is in a different L4 segment though? Maybe
you did not account for the segments?
0x49000000 + 0x20000 + 0x2000/0x4000/0x6000 for McBSP
0x49000000 + 0x50000 + 0x8000 for GPIO6
Or maybe I don't understand at which physical address the
overlap is? :)
Let me know if you need me to dump out the IO ranges for
you from the AP table for 34xx and 36xx.
Regards,
Tony
Powered by blists - more mailing lists