All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	x86@kernel.org, linux-snps-arc@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
	linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/12] mfd/sm501: depend on HAS_DMA
Date: Wed, 13 Feb 2019 07:29:31 +0000	[thread overview]
Message-ID: <20190213072931.GD1863@dell> (raw)
In-Reply-To: <20190211133554.30055-2-hch@lst.de>

On Mon, 11 Feb 2019, Christoph Hellwig wrote:

> Currently the sm501 mfd driver can be compiled without any dependencies,
> but through the use of dma_declare_coherent it really depends on
> having DMA and iomem support.  Normally we don't explicitly require DMA
> support as we have stubs for it if on UML, but in this case the driver
> selects support for dma_declare_coherent and thus also requires
> memmap support.  Guard this by an explicit dependency.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  drivers/mfd/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index f461460a2aeb..f15f6489803d 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -1066,6 +1066,7 @@ config MFD_SI476X_CORE
>  
>  config MFD_SM501
>  	tristate "Silicon Motion SM501"
> +	depends on HAS_DMA
>  	 ---help---
>  	  This is the core driver for the Silicon Motion SM501 multimedia
>  	  companion chip. This device is a multifunction device which may

I would normally have taken this, but I fear it will conflict with
[PATCH 06/12].  For that reason, just take my:

  Acked-by: Lee Jones <lee.jones@linaro.org>

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xtensa@linux-xtensa.org, linux-sh@vger.kernel.org,
	devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	x86@kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-riscv@lists.infradead.org,
	linux-snps-arc@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/12] mfd/sm501: depend on HAS_DMA
Date: Wed, 13 Feb 2019 07:29:31 +0000	[thread overview]
Message-ID: <20190213072931.GD1863@dell> (raw)
In-Reply-To: <20190211133554.30055-2-hch@lst.de>

On Mon, 11 Feb 2019, Christoph Hellwig wrote:

> Currently the sm501 mfd driver can be compiled without any dependencies,
> but through the use of dma_declare_coherent it really depends on
> having DMA and iomem support.  Normally we don't explicitly require DMA
> support as we have stubs for it if on UML, but in this case the driver
> selects support for dma_declare_coherent and thus also requires
> memmap support.  Guard this by an explicit dependency.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  drivers/mfd/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index f461460a2aeb..f15f6489803d 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -1066,6 +1066,7 @@ config MFD_SI476X_CORE
>  
>  config MFD_SM501
>  	tristate "Silicon Motion SM501"
> +	depends on HAS_DMA
>  	 ---help---
>  	  This is the core driver for the Silicon Motion SM501 multimedia
>  	  companion chip. This device is a multifunction device which may

I would normally have taken this, but I fear it will conflict with
[PATCH 06/12].  For that reason, just take my:

  Acked-by: Lee Jones <lee.jones@linaro.org>

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 01/12] mfd/sm501: depend on HAS_DMA
Date: Wed, 13 Feb 2019 07:29:31 +0000	[thread overview]
Message-ID: <20190213072931.GD1863@dell> (raw)
In-Reply-To: <20190211133554.30055-2-hch@lst.de>

On Mon, 11 Feb 2019, Christoph Hellwig wrote:

> Currently the sm501 mfd driver can be compiled without any dependencies,
> but through the use of dma_declare_coherent it really depends on
> having DMA and iomem support.  Normally we don't explicitly require DMA
> support as we have stubs for it if on UML, but in this case the driver
> selects support for dma_declare_coherent and thus also requires
> memmap support.  Guard this by an explicit dependency.
> 
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
>  drivers/mfd/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index f461460a2aeb..f15f6489803d 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -1066,6 +1066,7 @@ config MFD_SI476X_CORE
>  
>  config MFD_SM501
>  	tristate "Silicon Motion SM501"
> +	depends on HAS_DMA
>  	 ---help---
>  	  This is the core driver for the Silicon Motion SM501 multimedia
>  	  companion chip. This device is a multifunction device which may

I would normally have taken this, but I fear it will conflict with
[PATCH 06/12].  For that reason, just take my:

  Acked-by: Lee Jones <lee.jones at linaro.org>

-- 
Lee Jones [???]
Linaro Services Technical Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xtensa@linux-xtensa.org, linux-sh@vger.kernel.org,
	devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	x86@kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-riscv@lists.infradead.org,
	linux-snps-arc@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/12] mfd/sm501: depend on HAS_DMA
Date: Wed, 13 Feb 2019 07:29:31 +0000	[thread overview]
Message-ID: <20190213072931.GD1863@dell> (raw)
In-Reply-To: <20190211133554.30055-2-hch@lst.de>

On Mon, 11 Feb 2019, Christoph Hellwig wrote:

> Currently the sm501 mfd driver can be compiled without any dependencies,
> but through the use of dma_declare_coherent it really depends on
> having DMA and iomem support.  Normally we don't explicitly require DMA
> support as we have stubs for it if on UML, but in this case the driver
> selects support for dma_declare_coherent and thus also requires
> memmap support.  Guard this by an explicit dependency.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  drivers/mfd/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index f461460a2aeb..f15f6489803d 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -1066,6 +1066,7 @@ config MFD_SI476X_CORE
>  
>  config MFD_SM501
>  	tristate "Silicon Motion SM501"
> +	depends on HAS_DMA
>  	 ---help---
>  	  This is the core driver for the Silicon Motion SM501 multimedia
>  	  companion chip. This device is a multifunction device which may

I would normally have taken this, but I fear it will conflict with
[PATCH 06/12].  For that reason, just take my:

  Acked-by: Lee Jones <lee.jones@linaro.org>

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xtensa@linux-xtensa.org, linux-sh@vger.kernel.org,
	devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	x86@kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-riscv@lists.infradead.org,
	linux-snps-arc@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/12] mfd/sm501: depend on HAS_DMA
Date: Wed, 13 Feb 2019 07:29:31 +0000	[thread overview]
Message-ID: <20190213072931.GD1863@dell> (raw)
In-Reply-To: <20190211133554.30055-2-hch@lst.de>

On Mon, 11 Feb 2019, Christoph Hellwig wrote:

> Currently the sm501 mfd driver can be compiled without any dependencies,
> but through the use of dma_declare_coherent it really depends on
> having DMA and iomem support.  Normally we don't explicitly require DMA
> support as we have stubs for it if on UML, but in this case the driver
> selects support for dma_declare_coherent and thus also requires
> memmap support.  Guard this by an explicit dependency.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  drivers/mfd/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index f461460a2aeb..f15f6489803d 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -1066,6 +1066,7 @@ config MFD_SI476X_CORE
>  
>  config MFD_SM501
>  	tristate "Silicon Motion SM501"
> +	depends on HAS_DMA
>  	 ---help---
>  	  This is the core driver for the Silicon Motion SM501 multimedia
>  	  companion chip. This device is a multifunction device which may

I would normally have taken this, but I fear it will conflict with
[PATCH 06/12].  For that reason, just take my:

  Acked-by: Lee Jones <lee.jones@linaro.org>

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-13  7:29 UTC|newest]

Thread overview: 159+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 13:35 dma_declare_coherent spring cleaning Christoph Hellwig
2019-02-11 13:35 ` Christoph Hellwig
2019-02-11 13:35 ` Christoph Hellwig
2019-02-11 13:35 ` Christoph Hellwig
2019-02-11 13:35 ` Christoph Hellwig
2019-02-11 13:35 ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 01/12] mfd/sm501: depend on HAS_DMA Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-13  7:29   ` Lee Jones [this message]
2019-02-13  7:29     ` Lee Jones
2019-02-13  7:29     ` Lee Jones
2019-02-13  7:29     ` Lee Jones
2019-02-13  7:29     ` Lee Jones
2019-02-13 18:17     ` Christoph Hellwig
2019-02-13 18:17       ` Christoph Hellwig
2019-02-13 18:17       ` Christoph Hellwig
2019-02-13 18:17       ` Christoph Hellwig
2019-02-13 18:17       ` Christoph Hellwig
2019-02-13 18:17       ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 02/12] device.h: dma_mem is only needed for HAVE_GENERIC_DMA_COHERENT Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12  7:49   ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-11 13:35 ` [PATCH 03/12] of: mark early_init_dt_alloc_reserved_memory_arch static Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12 20:24   ` Rob Herring
2019-02-12 20:24     ` Rob Herring
2019-02-12 20:24     ` Rob Herring
2019-02-12 20:24     ` Rob Herring
2019-02-12 20:24     ` Rob Herring
2019-02-12 20:24     ` Rob Herring
2019-02-13 18:16     ` Christoph Hellwig
2019-02-13 18:16       ` Christoph Hellwig
2019-02-13 18:16       ` Christoph Hellwig
2019-02-13 18:16       ` Christoph Hellwig
2019-02-13 18:16       ` Christoph Hellwig
2019-02-13 18:16       ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 04/12] of: select OF_RESERVED_MEM automatically Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12 20:11   ` Rob Herring
2019-02-12 20:11     ` Rob Herring
2019-02-12 20:11     ` Rob Herring
2019-02-12 20:11     ` Rob Herring
2019-02-12 20:11     ` Rob Herring
2019-02-12 20:11     ` Rob Herring
2019-02-11 13:35 ` [PATCH 05/12] dma-mapping: remove an incorrect __iommem annotation Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 06/12] dma-mapping: improve selection of dma_declare_coherent availability Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12  2:17   ` Paul Burton
2019-02-12  2:17     ` Paul Burton
2019-02-12  2:17     ` Paul Burton
2019-02-12  2:17     ` Paul Burton
2019-02-12  2:17     ` Paul Burton
2019-02-12  7:49   ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12  7:49     ` Greg Kroah-Hartman
2019-02-12 20:40   ` Rob Herring
2019-02-12 20:40     ` Rob Herring
2019-02-12 20:40     ` Rob Herring
2019-02-12 20:40     ` Rob Herring
2019-02-12 20:40     ` Rob Herring
2019-02-12 20:40     ` Rob Herring
2019-02-13 18:24     ` Christoph Hellwig
2019-02-13 18:24       ` Christoph Hellwig
2019-02-13 18:24       ` Christoph Hellwig
2019-02-13 18:24       ` Christoph Hellwig
2019-02-13 18:24       ` Christoph Hellwig
2019-02-13 18:24       ` Christoph Hellwig
2019-02-13 19:27       ` Rob Herring
2019-02-13 19:27         ` Rob Herring
2019-02-13 19:27         ` Rob Herring
2019-02-13 19:27         ` Rob Herring
2019-02-13 19:27         ` Rob Herring
2019-02-13 19:27         ` Rob Herring
2019-02-13  7:27   ` Lee Jones
2019-02-13  7:27     ` Lee Jones
2019-02-13  7:27     ` Lee Jones
2019-02-13  7:27     ` Lee Jones
2019-02-13  7:27     ` Lee Jones
2019-02-11 13:35 ` [PATCH 07/12] dma-mapping: move CONFIG_DMA_CMA to kernel/dma/Kconfig Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12  7:50   ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-11 13:35 ` [PATCH 08/12] dma-mapping: remove dma_mark_declared_memory_occupied Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 09/12] dma-mapping: remove the DMA_MEMORY_EXCLUSIVE flag Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-12  7:50   ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-12  7:50     ` Greg Kroah-Hartman
2019-02-11 13:35 ` [PATCH 10/12] dma-mapping: simplify allocations from per-device coherent memory Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 11/12] dma-mapping: handle per-device coherent memory mmap in common code Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35 ` [PATCH 12/12] dma-mapping: remove dma_assign_coherent_memory Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig
2019-02-11 13:35   ` Christoph Hellwig

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=20190213072931.GD1863@dell \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=x86@kernel.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 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.