linux-kernel - Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <007b3c61-ec4c-a89d-e80e-adcec314e298@ti.com>
Date:   Fri, 2 Sep 2016 09:52:21 -0500
From:   Nishanth Menon <nm@...com>
To:     Sekhar Nori <nsekhar@...com>, Tony Lindgren <tony@...mide.com>
CC:     Tomi Valkeinen <tomi.valkeinen@...com>,
        Kishon Vijay Abraham I <kishon@...com>,
        <linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux
 configurations

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