mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Jeffy Chen <jeffy.chen@rock-chips.com>
Cc: linux-kernel@vger.kernel.org, briannorris@chromium.org,
	dianders@chromium.org, tfiga@chromium.org, seanpaul@chromium.org,
	zyw@rock-chips.com, mark.yao@rock-chips.com,
	iommu@lists.linux-foundation.org, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] iommu/rockchip: Remove build dependency on ARM
Date: Wed, 10 May 2017 12:37:56 +0200	[thread overview]
Message-ID: <2219350.J3uHR7SeXA@diego> (raw)
In-Reply-To: <1494412092-25458-1-git-send-email-jeffy.chen@rock-chips.com>

Hi Jeffy,

Am Mittwoch, 10. Mai 2017, 18:28:12 CEST schrieb Jeffy Chen:
> This patch removes the build dependency on ARM, so we can build on arm64
> as well.
> 
> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> ---
> 
>  drivers/iommu/Kconfig | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> index 6ee3a25..cb26f45 100644
> --- a/drivers/iommu/Kconfig
> +++ b/drivers/iommu/Kconfig
> @@ -219,7 +219,6 @@ config OMAP_IOMMU_DEBUG
> 
>  config ROCKCHIP_IOMMU
>  	bool "Rockchip IOMMU Support"
> -	depends on ARM

The previous patch from Simon Xue that was delayed due to the drm
changes needed did a
	depends in ARM || ARM64
instead.

I'm not sure which variant is better and Rockchip is currently not
providing any other cpu architectures, just noting the difference and
letting you and Joerg decide which one to choose :-) .

Enabling the iommu on arm64 looks good to me in any case.


Heiko



>  	depends on ARCH_ROCKCHIP || COMPILE_TEST
>  	select IOMMU_API
>  	select ARM_DMA_USE_IOMMU

      reply	other threads:[~2017-05-10 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 10:28 Jeffy Chen
2017-05-10 10:37 ` Heiko Stübner [this message]

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=2219350.J3uHR7SeXA@diego \
    --to=heiko@sntech.de \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jeffy.chen@rock-chips.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.yao@rock-chips.com \
    --cc=seanpaul@chromium.org \
    --cc=tfiga@chromium.org \
    --cc=zyw@rock-chips.com \
    /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

all inboxes | Powered by JetHome®