From: Sami Liedes <sliedes@nvidia.com>
To: iommu@lists.linux-foundation.org
Cc: Sami Liedes <sliedes@nvidia.com>, Joerg Roedel <joro@8bytes.org>,
Hiroshi Doyu <hdoyu@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Reding <thierry.reding@avionic-design.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] iommu/tegra: Add missing spinlock initialization
Date: Mon, 4 Feb 2013 14:31:48 +0200 [thread overview]
Message-ID: <1359981110-9924-1-git-send-email-sliedes@nvidia.com> (raw)
Fix tegra_smmu_probe() to initialize client_lock spinlocks in
per-address-space structures.
Signed-off-by: Sami Liedes <sliedes@nvidia.com>
---
drivers/iommu/tegra-smmu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c
index f08dbcd..46cc8cf 100644
--- a/drivers/iommu/tegra-smmu.c
+++ b/drivers/iommu/tegra-smmu.c
@@ -1,7 +1,7 @@
/*
* IOMMU API for SMMU in Tegra30
*
- * Copyright (c) 2011-2012, NVIDIA CORPORATION. All rights reserved.
+ * Copyright (c) 2011-2013, NVIDIA CORPORATION. All rights reserved.
*
* This program is free software; you can redistribute it and/or modify it
* under the terms and conditions of the GNU General Public License,
@@ -1217,6 +1217,7 @@ static int tegra_smmu_probe(struct platform_device *pdev)
as->pte_attr = _PTE_ATTR;
spin_lock_init(&as->lock);
+ spin_lock_init(&as->client_lock);
INIT_LIST_HEAD(&as->client);
}
spin_lock_init(&smmu->lock);
--
1.7.9.5
next reply other threads:[~2013-02-04 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 12:31 Sami Liedes [this message]
[not found] ` <1359981110-9924-1-git-send-email-sliedes-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-04 14:13 ` [PATCH] iommu/tegra: Add missing spinlock initialization Joerg Roedel
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=1359981110-9924-1-git-send-email-sliedes@nvidia.com \
--to=sliedes@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdoyu@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=thierry.reding@avionic-design.de \
/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).