linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thor.thayer@linux.intel.com (thor.thayer at linux.intel.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 0/2] iommu/arm-smmu: Add Stratix10 SMMU Support
Date: Fri,  5 Oct 2018 15:56:58 -0500	[thread overview]
Message-ID: <1538773020-27784-1-git-send-email-thor.thayer@linux.intel.com> (raw)

From: Thor Thayer <thor.thayer@linux.intel.com>

Add SMMU support for the Stratix10 SOCFPGA. This patch requires
clock enables for the master TBUs and therefore has a dependency
on patches currently being reviewed.

This patchset is dependent on the patch series [1]

v4  Address Vivek's comment.
    Abandon dependency on [2] (no recent activity/reviews)
    Implement device tree parsing of clock on top of [1].
v3  Address comment from Robin and change dependency on device
    tree bulk clock patches [2].
v2  Change to dependency on [1].

[1] [v16,0/5] iommu/arm-smmu: Add runtime pm/sleep support
https://patchwork.kernel.org/cover/10581891/

[2] [PATCH V6 0/4] clk: new APIs to handle all available clocks
https://lkml.org/lkml/2018/8/31/97

Thor Thayer (2):
  arm64: dts: stratix10: Add Stratix10 SMMU support
  iommu/arm-smmu: Get clock config from device tree

 arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 29 ++++++++++++++++++++++
 drivers/iommu/arm-smmu.c                          | 30 ++++++++++++++++++++---
 2 files changed, 56 insertions(+), 3 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-10-05 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 20:56 thor.thayer at linux.intel.com [this message]
2018-10-05 20:56 ` [PATCHv4 1/2] arm64: dts: stratix10: Add Stratix10 SMMU support thor.thayer at linux.intel.com
2018-10-05 20:57 ` [PATCHv4 2/2] iommu/arm-smmu: Get clock config from device tree thor.thayer at linux.intel.com
2018-11-21 17:48   ` Will Deacon
2018-10-30 13:38 ` [PATCHv4 0/2] iommu/arm-smmu: Add Stratix10 SMMU Support Thor Thayer

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=1538773020-27784-1-git-send-email-thor.thayer@linux.intel.com \
    --to=thor.thayer@linux.intel.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).