All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-sh@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
	iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v3] iommu: shmobile: Enable the driver on all ARM platforms
Date: Wed, 30 Oct 2013 12:40:12 +0100	[thread overview]
Message-ID: <1652955.Gs3XDiEUHO@avalon> (raw)
In-Reply-To: <20131030112625.GZ16735@n2100.arm.linux.org.uk>

Hi Russell,

[CC'ing Mark Brown]

On Wednesday 30 October 2013 11:26:25 Russell King - ARM Linux wrote:
> On Wed, Oct 30, 2013 at 12:20:43PM +0100, Laurent Pinchart wrote:
> > Renesas ARM platforms are transitioning from single-platform to
> > multi-platform kernels using the new ARCH_SHMOBILE_MULTI. Make the
> > driver available on all ARM platforms to enable it on both ARCH_SHMOBILE
> > and ARCH_SHMOBILE_MULTI and increase build testing coverage.
> > 
> > Don't enable COMPILE_TEST support as the driver doesn't compile on
> > non-ARM platforms due to usage of the ARM DMA IOMMU API.
> 
> For similar reasons as x86, can we please think about using:
> 
> 	depends on ARM
> 	depends on ARCH_SHMOBILE || ARCH_SHMOBILE_MULTI || COMPILE_TEST
> 
> This way we don't end up polluting the configuration for non-shmobile
> platforms.  Same goes for other ARM stuff... the number of options is
> getting rather large and we need to think about keeping that in check
> where its easily possible to do so.

I've been asked to move from depends ARM to no dependency at all, and have 
thus settled for ARM || COMPILE_TEST in most cases, and just ARM where the 
driver couldn't be compiled on other platforms.

I'm fine with your proposed option. As I don't want to respin the series 
dozens of time let's first agree on the course of action, I will then repost 
the patches. Mark, you've pushed towards as few platform dependencies as 
possible, what's your opinion on this ?

-- 
Regards,

Laurent Pinchart


WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] iommu: shmobile: Enable the driver on all ARM platforms
Date: Wed, 30 Oct 2013 11:40:12 +0000	[thread overview]
Message-ID: <1652955.Gs3XDiEUHO@avalon> (raw)
In-Reply-To: <20131030112625.GZ16735@n2100.arm.linux.org.uk>

Hi Russell,

[CC'ing Mark Brown]

On Wednesday 30 October 2013 11:26:25 Russell King - ARM Linux wrote:
> On Wed, Oct 30, 2013 at 12:20:43PM +0100, Laurent Pinchart wrote:
> > Renesas ARM platforms are transitioning from single-platform to
> > multi-platform kernels using the new ARCH_SHMOBILE_MULTI. Make the
> > driver available on all ARM platforms to enable it on both ARCH_SHMOBILE
> > and ARCH_SHMOBILE_MULTI and increase build testing coverage.
> > 
> > Don't enable COMPILE_TEST support as the driver doesn't compile on
> > non-ARM platforms due to usage of the ARM DMA IOMMU API.
> 
> For similar reasons as x86, can we please think about using:
> 
> 	depends on ARM
> 	depends on ARCH_SHMOBILE || ARCH_SHMOBILE_MULTI || COMPILE_TEST
> 
> This way we don't end up polluting the configuration for non-shmobile
> platforms.  Same goes for other ARM stuff... the number of options is
> getting rather large and we need to think about keeping that in check
> where its easily possible to do so.

I've been asked to move from depends ARM to no dependency at all, and have 
thus settled for ARM || COMPILE_TEST in most cases, and just ARM where the 
driver couldn't be compiled on other platforms.

I'm fine with your proposed option. As I don't want to respin the series 
dozens of time let's first agree on the course of action, I will then repost 
the patches. Mark, you've pushed towards as few platform dependencies as 
possible, what's your opinion on this ?

-- 
Regards,

Laurent Pinchart


WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] iommu: shmobile: Enable the driver on all ARM platforms
Date: Wed, 30 Oct 2013 12:40:12 +0100	[thread overview]
Message-ID: <1652955.Gs3XDiEUHO@avalon> (raw)
In-Reply-To: <20131030112625.GZ16735@n2100.arm.linux.org.uk>

Hi Russell,

[CC'ing Mark Brown]

On Wednesday 30 October 2013 11:26:25 Russell King - ARM Linux wrote:
> On Wed, Oct 30, 2013 at 12:20:43PM +0100, Laurent Pinchart wrote:
> > Renesas ARM platforms are transitioning from single-platform to
> > multi-platform kernels using the new ARCH_SHMOBILE_MULTI. Make the
> > driver available on all ARM platforms to enable it on both ARCH_SHMOBILE
> > and ARCH_SHMOBILE_MULTI and increase build testing coverage.
> > 
> > Don't enable COMPILE_TEST support as the driver doesn't compile on
> > non-ARM platforms due to usage of the ARM DMA IOMMU API.
> 
> For similar reasons as x86, can we please think about using:
> 
> 	depends on ARM
> 	depends on ARCH_SHMOBILE || ARCH_SHMOBILE_MULTI || COMPILE_TEST
> 
> This way we don't end up polluting the configuration for non-shmobile
> platforms.  Same goes for other ARM stuff... the number of options is
> getting rather large and we need to think about keeping that in check
> where its easily possible to do so.

I've been asked to move from depends ARM to no dependency at all, and have 
thus settled for ARM || COMPILE_TEST in most cases, and just ARM where the 
driver couldn't be compiled on other platforms.

I'm fine with your proposed option. As I don't want to respin the series 
dozens of time let's first agree on the course of action, I will then repost 
the patches. Mark, you've pushed towards as few platform dependencies as 
possible, what's your opinion on this ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2013-10-30 11:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 11:20 [PATCH v3] iommu: shmobile: Enable the driver on all ARM platforms Laurent Pinchart
2013-10-30 11:20 ` Laurent Pinchart
2013-10-30 11:20 ` Laurent Pinchart
2013-10-30 11:26 ` Russell King - ARM Linux
2013-10-30 11:26   ` Russell King - ARM Linux
2013-10-30 11:26   ` Russell King - ARM Linux
2013-10-30 11:40   ` Laurent Pinchart [this message]
2013-10-30 11:40     ` Laurent Pinchart
2013-10-30 11:40     ` Laurent Pinchart
2013-10-30 16:28     ` Mark Brown
2013-10-30 16:28       ` Mark Brown
2013-10-30 16:28       ` Mark Brown
2013-10-31  6:03       ` Simon Horman
2013-10-31  6:03         ` Simon Horman
2013-10-31  6:03         ` Simon Horman
     [not found]         ` <20131031060305.GU1603-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-10-31 17:49           ` Mark Brown
2013-10-31 17:49             ` Mark Brown
2013-10-31 17:49             ` Mark Brown
2013-11-01  0:39             ` Simon Horman
2013-11-01  0:39               ` Simon Horman
2013-11-01  0:39               ` Simon Horman
2013-11-05 18:59       ` Laurent Pinchart
2013-11-05 18:59         ` Laurent Pinchart
2013-11-05 18:59         ` Laurent Pinchart

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=1652955.Gs3XDiEUHO@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=broonie@kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.