From mboxrd@z Thu Jan  1 00:00:00 1970
From: nm@ti.com (Nishanth Menon)
Date: Fri, 2 Sep 2016 09:52:21 -0500
Subject: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux
 configurations
In-Reply-To: <9bdf5693-ba02-8ce5-04b0-08875ccf7603@ti.com>
References: <20160902090600.27262-1-nm@ti.com>
 <20160902090600.27262-2-nm@ti.com>
 <9bdf5693-ba02-8ce5-04b0-08875ccf7603@ti.com>
Message-ID: <007b3c61-ec4c-a89d-e80e-adcec314e298@ti.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On 09/02/2016 05:18 AM, Sekhar Nori wrote:
> On Friday 02 September 2016 02:35 PM, Nishanth Menon wrote:
>> pinmuxing for DRA7x/AM57x family of processors need to be done in IO
>> isolation as part of initial bootloader executed from SRAM. This is
>> done as part of iodelay configuration sequence and is required due to
>> the limitations introduced by erratum ID: i869[1] and elaborated in
>> the Technical Reference Manual[2] 18.4.6.1.7 Isolation Requirements.
>>
>> Only peripheral that is permitted for dynamic pin mux configuration is
>> MMC. This is to accommodate the requirements for varied speeds (which
>
> Actually its MMC and DCAN. DCAN because of i893 ("DCAN Initialization
> Sequence"). But I can see you may have omitted reference to it since
> DCAN is not really used on the x15.

True, I should add that for completeness. will do. thanks for catching 
the same.


-- 
Regards,
Nishanth Menon