From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 1/3] ARM: mm: add support for HW coherent systems in PL310 cache
Date: Mon, 30 Jun 2014 20:50:59 +0200 [thread overview]
Message-ID: <20140630205059.2e7b2278@free-electrons.com> (raw)
In-Reply-To: <20140630173217.GT28951@arm.com>
Dear Catalin Marinas,
On Mon, 30 Jun 2014 18:32:17 +0100, Catalin Marinas wrote:
> > +/*
> > * Note that the end addresses passed to Linux primitives are
> > * noninclusive, while the hardware cache range operations use
> > * inclusive start and end addresses.
> > @@ -1487,6 +1514,10 @@ int __init l2x0_of_init(u32 aux_val, u32 aux_mask)
> >
> > data = of_match_node(l2x0_ids, np)->data;
> >
> > + if (of_device_is_compatible(np, "arm,pl310-cache") &&
> > + of_property_read_bool(np, "arm,io-coherent"))
> > + data = &of_l2c310_coherent_data;
>
> I don't have a better way without duplicating the l2c_init_data
> structure since the fixup function does not take a device_node
> pointer. If it did, you could have added the check in l2c310_fixup and
> zeroed the sync pointer there.
>
> Anyway, your approach works for me as well:
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Thanks for the confirmation. Note that it comes a bit too late though:
the patch is already in 3.16-rc3:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/mm/cache-l2x0.c?id=98ea2dba65932ffc456b6d7b11b8a0624e2f7b95.
However, I'm interested in hearing your opinion about the I/O coherency
discussion in !SMP, and especially whether the TTB flags need to be
consistent with the PMD flags in terms of cache policy and
shareability. See
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263524.html.
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 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 15:09 [PATCHv5 0/3] ARM: implement workaround for Cortex-A9/PL310/PCIe deadlock Thomas Petazzoni
2014-06-12 15:09 ` [PATCHv5 1/3] ARM: mm: add support for HW coherent systems in PL310 cache Thomas Petazzoni
2014-06-12 20:12 ` Rob Herring
2014-06-30 17:32 ` Catalin Marinas
2014-06-30 18:50 ` Thomas Petazzoni [this message]
2014-06-12 15:09 ` [PATCHv5 2/3] ARM: mvebu: move Armada 375 external abort logic as a quirk Thomas Petazzoni
2014-06-21 0:55 ` Jason Cooper
2014-06-12 15:09 ` [PATCHv5 3/3] ARM: mvebu: update L2/PCIe deadlock workaround after L2CC cleanup Thomas Petazzoni
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=20140630205059.2e7b2278@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;
as well as URLs for NNTP newsgroup(s).