From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754174AbcIBOxr (ORCPT ); Fri, 2 Sep 2016 10:53:47 -0400 Received: from bear.ext.ti.com ([198.47.19.11]:40909 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753332AbcIBOxo (ORCPT ); Fri, 2 Sep 2016 10:53:44 -0400 Subject: Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations To: Sekhar Nori , Tony Lindgren References: <20160902090600.27262-1-nm@ti.com> <20160902090600.27262-2-nm@ti.com> <9bdf5693-ba02-8ce5-04b0-08875ccf7603@ti.com> CC: Tomi Valkeinen , Kishon Vijay Abraham I , , , , From: Nishanth Menon Message-ID: <007b3c61-ec4c-a89d-e80e-adcec314e298@ti.com> Date: Fri, 2 Sep 2016 09:52:21 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <9bdf5693-ba02-8ce5-04b0-08875ccf7603@ti.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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