public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "hancock@sedsystems.ca" <hancock@sedsystems.ca>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "michal.simek@xilinx.com" <michal.simek@xilinx.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"knaack.h@gmx.de" <knaack.h@gmx.de>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: adc: xilinx: support all ARM platforms
Date: Thu, 6 Jun 2019 10:09:59 +0000	[thread overview]
Message-ID: <379a99c8405b4cfbaa61ac49f9b40d4c577eb2a8.camel@analog.com> (raw)
In-Reply-To: <1559768858-1175-1-git-send-email-hancock@sedsystems.ca>

On Wed, 2019-06-05 at 15:07 -0600, Robert Hancock wrote:
> [External]
> 
> 
> Since the XADC logic can be used with standalone Xilinx FPGAs, this driver
> can potentially be used with various ARM platforms, not just Zynq.
> Change the Zynq dependency to ARM in the list of supported platforms
> in the Kconfig dependencies for this driver.

To my knowledge, there are 3 FPGA platforms with ARM supported in Linux.
And symbols are ARCH_ZYNQ, ARCH_ZYNQMP & ARCH_SOCFPGA.
For these ARM + FPGA SoCs, it is usually preferred to list the supported/tested ARM + FPGA platforms in Kconfig.

I am curious: are you using something that isn't in the above list?

Thanks
Alex

> 
> Signed-off-by: Robert Hancock <hancock@sedsystems.ca>
> ---
>  drivers/iio/adc/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index f96a770..93863bb 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -1085,7 +1085,7 @@ config VIPERBOARD_ADC
> 
>  config XILINX_XADC
>         tristate "Xilinx XADC driver"
> -       depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
> +       depends on ARM || MICROBLAZE || COMPILE_TEST
>         depends on HAS_IOMEM
>         select IIO_BUFFER
>         select IIO_TRIGGERED_BUFFER
> --
> 1.8.3.1
> 

  reply	other threads:[~2019-06-06 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 21:07 [PATCH] iio: adc: xilinx: support all ARM platforms Robert Hancock
2019-06-06 10:09 ` Ardelean, Alexandru [this message]
2019-06-06 15:21   ` Robert Hancock
2019-06-07  7:30     ` Michal Simek
2019-06-07 19:17       ` Alexandru Ardelean
2019-06-07 19:32         ` Robert Hancock
2019-06-08 12:00           ` Jonathan Cameron
2019-06-10  7:34             ` Ardelean, Alexandru

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=379a99c8405b4cfbaa61ac49f9b40d4c577eb2a8.camel@analog.com \
    --to=alexandru.ardelean@analog.com \
    --cc=hancock@sedsystems.ca \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=pmeerw@pmeerw.net \
    /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