Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: nuno.sa@analog.com, linux-iio@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] iio: adc: adi-axi-adc: add platform dependencies
Date: Sat, 8 Jun 2024 18:34:55 +0100	[thread overview]
Message-ID: <20240608183455.01cf3e7c@jic23-huawei> (raw)
In-Reply-To: <20240604-dev-axi-adc-kconfig-v1-1-cfb725606b8e@analog.com>

On Tue, 04 Jun 2024 11:16:58 +0200
Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:

> From: Nuno Sa <nuno.sa@analog.com>
> 
> Being this device a soft core, it's only supported on some/specific
> platforms. Hence add proper dependencies for the supported platforms.
> Also add COMPILE_TEST to increase the build coverage.
People build kernels without COMPILE_TEST?  Weird :)

Applied

> 
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> ---
>  drivers/iio/adc/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index 5030319249c5..3d91015af6ea 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -353,6 +353,7 @@ config AD9467
>  
>  config ADI_AXI_ADC
>  	tristate "Analog Devices Generic AXI ADC IP core driver"
> +	depends on MICROBLAZE || NIOS2 || ARCH_ZYNQ || ARCH_ZYNQMP || ARCH_INTEL_SOCFPGA || COMPILE_TEST
>  	select IIO_BUFFER
>  	select IIO_BUFFER_HW_CONSUMER
>  	select IIO_BUFFER_DMAENGINE
> 
> ---
> base-commit: b3019fcdeb286b2cfe45e44bccb44dbcd8ff66dd
> change-id: 20240604-dev-axi-adc-kconfig-1058732cb384
> --
> 
> Thanks!
> - Nuno Sá
> 
> 


      reply	other threads:[~2024-06-08 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  9:16 [PATCH] iio: adc: adi-axi-adc: add platform dependencies Nuno Sa via B4 Relay
2024-06-08 17:34 ` Jonathan Cameron [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=20240608183455.01cf3e7c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=devnull+nuno.sa.analog.com@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.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