From: a0131933@ti.com (Lokesh Vutla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dra7: Enable Errata i877
Date: Tue, 8 Mar 2016 09:23:03 +0530 [thread overview]
Message-ID: <56DE4C9F.7060603@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603072355030.27387@utopia.booyaka.com>
On Tuesday 08 March 2016 05:26 AM, Paul Walmsley wrote:
> On Mon, 7 Mar 2016, Lokesh Vutla wrote:
>
>> On Monday 07 March 2016 03:09 PM, Paul Walmsley wrote:
>>> On Thu, 3 Mar 2016, Lokesh Vutla wrote:
>>>
>>>> This series enables Errata i877 for all DRA7 platforms. The public errata
>>>> documentation can be found here[1].
>>>>
>>>> [1] http://www.ti.com/lit/er/sprz429h/sprz429h.pdf
>>>>
>>>> Lokesh Vutla (1):
>>>> ARM: OMAP2+: hwmod: Introduce ti,no-idle dt property
>>>>
>>>> Mugunthan V N (1):
>>>> ARM: dts: dra7: do not gate cpsw clock due to errata i877
>>>
>>> I've sent these for merging immediately.
>>>
>>> Have you sent patches for U-boot yet?
>> Yes, It is already merged into u-boot.
>> http://git.denx.de/?p=u-boot.git;a=commitdiff;h=f986d9720836433ded29f06c8f5aed462bd20924;hp=65e9d56fb9ce9cfd7ffff7afaa6b7de50e400e06
>
> I may be misreading this patch, but all it seems to do is add clock
> control for GMAC. It doesn't seem to force the clock to stay on. What am
> I missing?
So, this is an array containing clock controls which are needed very
early. This array will be passed to clock framework to enable all the
clocks. Just adding it to the array is sufficient.
Thanks and regards,
Lokesh
>
>
> - Paul
>
prev parent reply other threads:[~2016-03-08 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 8:42 [PATCH 0/2] ARM: dra7: Enable Errata i877 Lokesh Vutla
2016-03-03 8:42 ` [PATCH 1/2] ARM: OMAP2+: hwmod: Introduce ti,no-idle dt property Lokesh Vutla
2016-03-05 4:28 ` Rob Herring
2016-03-03 8:42 ` [PATCH 2/2] ARM: dts: dra7: do not gate cpsw clock due to errata i877 Lokesh Vutla
2016-03-07 9:39 ` [PATCH 0/2] ARM: dra7: Enable Errata i877 Paul Walmsley
2016-03-07 9:40 ` Lokesh Vutla
2016-03-07 23:56 ` Paul Walmsley
2016-03-08 3:53 ` Lokesh Vutla [this message]
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=56DE4C9F.7060603@ti.com \
--to=a0131933@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).