From: ohaugan@codeaurora.org (Olav Haugan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm-smmu fixes for CBn_TCR and S2CR/SMR programming
Date: Mon, 4 Aug 2014 11:01:01 -0700 [thread overview]
Message-ID: <1407175263-10699-1-git-send-email-ohaugan@codeaurora.org> (raw)
Here are a couple fixes for the arm smmu driver. The first one deals with
ensuring that we program CBn_TCR correctly when we are programming a stage-1
context bank.
The second patch ensures that SMR registers are not touched when stream
matchign is not supported by the hardware. When stream id matching is not
supported by the hardware the SMR registers does not exists. However, even
if they are UNK/SBZP we prefer not to write to more registers than needed.
v1 -> v2:
* Fixed so that SL0 is programed for SMMUv1 hardware also
* Rebased onto Will's iommu/pci branch which only left one issue to fix
for the second patch.
Olav Haugan (2):
iommu/arm-smmu: Fix programming of SMMU_CBn_TCR for stage 1
iommu/arm-smmu: Do not access non-existing SMR registers
drivers/iommu/arm-smmu.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-08-04 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 18:01 Olav Haugan [this message]
2014-08-04 18:01 ` [PATCH v2 1/2] iommu/arm-smmu: Fix programming of SMMU_CBn_TCR for stage 1 Olav Haugan
2014-08-04 18:01 ` [PATCH v2 2/2] iommu/arm-smmu: Do not access non-existing SMR registers Olav Haugan
2014-08-06 10:19 ` Will Deacon
2014-08-06 16:44 ` Olav Haugan
2014-08-06 17:35 ` Will Deacon
2014-08-06 23:34 ` Olav Haugan
2014-08-07 9:22 ` Will Deacon
2014-08-08 18:51 ` Olav Haugan
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=1407175263-10699-1-git-send-email-ohaugan@codeaurora.org \
--to=ohaugan@codeaurora.org \
--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).