From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: SoC changes for v3.17
Date: Mon, 30 Jun 2014 12:22:16 +0200 [thread overview]
Message-ID: <20140630122216.6ea35ac9@free-electrons.com> (raw)
In-Reply-To: <20140628172044.4231c32d@free-electrons.com>
Jason,
On Sat, 28 Jun 2014 17:20:44 +0200, Thomas Petazzoni wrote:
> Yeah, sorry, I wasn't clear. If you look back at what I sent in
> https://www.mail-archive.com/devicetree at vger.kernel.org/msg30473.html
> ([PATCHv5 0/3] ARM: implement workaround for Cortex-A9/PL310/PCIe
> deadlock), there were three patches:
>
> PATCH 1/3, "ARM: mm: add support for HW coherent systems in PL310
> cache", for Russell. It has already been merged by Russell in
> "git-curr", as visible at
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8076/1.
> I'm hoping this is scheduled for 3.16, because I need this patch for
> 3.16 to avoid the PCIe deadlock.
>
> PATCH 2/3 and 3/3 are related, and the latter is needed to solve the
> PCIe deadlock, by using the new DT property made available in PATCH
> 1/3. PATCH 2/3 is ARM: mvebu: move Armada 375 external abort logic as
> a quirk and PATCH 3/3 is ARM: mvebu: update L2/PCIe deadlock
> workaround after L2CC cleanup.
>
> All in all, I'm hoping for the series at
> https://www.mail-archive.com/devicetree at vger.kernel.org/msg30473.html
> to fully show up in 3.16, because it's really related to fixing a
> serious PCIe deadlock (can be triggered in under a minute of PCIe
> usage).
Now that Russell is pushing PATCH 1/3 in the 3.16-rc cycle, can you
push PATCH 2/3 and PATCH 3/3 pointed above into the 3.16-rc cycle as
well?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-30 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:46 [GIT PULL] ARM: mvebu: SoC changes for v3.17 Jason Cooper
2014-06-28 14:23 ` Thomas Petazzoni
2014-06-28 15:07 ` Jason Cooper
2014-06-28 15:20 ` Thomas Petazzoni
2014-06-29 9:35 ` Russell King - ARM Linux
2014-06-29 9:56 ` Thomas Petazzoni
2014-06-30 10:22 ` Thomas Petazzoni [this message]
2014-06-30 10:29 ` Russell King - ARM Linux
2014-06-30 12:06 ` Jason Cooper
2014-06-30 12:11 ` Thomas Petazzoni
2014-06-30 12:14 ` Jason Cooper
2014-06-30 17:44 ` Jason Cooper
2014-06-30 18:50 ` Thomas Petazzoni
2014-07-01 12:11 ` [GIT PULL V2] " Jason Cooper
2014-07-08 5:28 ` Olof Johansson
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=20140630122216.6ea35ac9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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