From: Nishanth Menon <nm@ti.com>
To: Sekhar Nori <nsekhar@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations
Date: Fri, 2 Sep 2016 09:52:21 -0500 [thread overview]
Message-ID: <007b3c61-ec4c-a89d-e80e-adcec314e298@ti.com> (raw)
In-Reply-To: <9bdf5693-ba02-8ce5-04b0-08875ccf7603@ti.com>
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
next prev parent reply other threads:[~2016-09-02 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:05 [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
2016-09-02 9:05 ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations Nishanth Menon
[not found] ` <20160902090600.27262-2-nm-l0cyMroinI0@public.gmane.org>
2016-09-02 10:18 ` Sekhar Nori
2016-09-02 14:52 ` Nishanth Menon [this message]
[not found] ` <20160902090600.27262-1-nm-l0cyMroinI0@public.gmane.org>
2016-09-02 9:06 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1 Nishanth Menon
2016-09-02 9:58 ` Tomi Valkeinen
2016-09-02 10:01 ` Nishanth Menon
2016-09-02 11:48 ` Tomi Valkeinen
2016-09-02 10:41 ` Sekhar Nori
[not found] ` <dd74f5e1-304f-661e-7fd9-f5f81bcfc55e-l0cyMroinI0@public.gmane.org>
2016-09-02 11:18 ` Tomi Valkeinen
2016-09-02 13:52 ` Robert Nelson
2016-09-02 15:01 ` Nishanth Menon
[not found] ` <CAOCHtYiFjB-cuABmCiw96spc-De+qNNQYGrjp-MmNDuH2mJ9Bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-02 15:06 ` Tony Lindgren
2016-09-06 10:10 ` Sekhar Nori
2016-09-06 20:05 ` Tony Lindgren
[not found] ` <20160906200553.wqkvwsfww3rllhd5-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-09-07 5:09 ` Sekhar Nori
2016-09-02 9:14 ` [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=007b3c61-ec4c-a89d-e80e-adcec314e298@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).