From: Xu Yilun <yilun.xu@intel.com>
To: Nava kishore Manne <nava.kishore.manne@amd.com>
Cc: mdf@kernel.org, hao.wu@intel.com, trix@redhat.com,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpga: xilinx-pr-decoupler: select FPGA_BRIDGE for 'Xilinx LogiCORE PR Decoupler'
Date: Sat, 1 Apr 2023 21:52:45 +0800 [thread overview]
Message-ID: <ZCg3LepdPRFtsAcb@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20230327115103.106059-1-nava.kishore.manne@amd.com>
On 2023-03-27 at 17:21:03 +0530, Nava kishore Manne wrote:
> The Xilinx LogiCORE PR Decoupler depends on the FPGA_BRIDGE always and
> hence select it explicitly to make sure that it will be available all
> the time when PR decoupler is enabled.
FPGA_BRIDGE is available all the time if XILINX_PR_DECOUPLER is selected
by user. What's the problem now?
Thanks,
Yilun
>
> Signed-off-by: Nava kishore Manne <nava.kishore.manne@amd.com>
> ---
> drivers/fpga/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
> index 0a00763b9f28..71003f256c60 100644
> --- a/drivers/fpga/Kconfig
> +++ b/drivers/fpga/Kconfig
> @@ -115,8 +115,8 @@ config ALTERA_FREEZE_BRIDGE
>
> config XILINX_PR_DECOUPLER
> tristate "Xilinx LogiCORE PR Decoupler"
> - depends on FPGA_BRIDGE
> depends on HAS_IOMEM
> + select FPGA_BRIDGE
> help
> Say Y to enable drivers for Xilinx LogiCORE PR Decoupler
> or Xilinx Dynamic Function eXchange AIX Shutdown Manager.
> --
> 2.25.1
>
prev parent reply other threads:[~2023-04-01 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:51 [PATCH] fpga: xilinx-pr-decoupler: select FPGA_BRIDGE for 'Xilinx LogiCORE PR Decoupler' Nava kishore Manne
2023-04-01 13:52 ` Xu Yilun [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=ZCg3LepdPRFtsAcb@yilunxu-OptiPlex-7050 \
--to=yilun.xu@intel.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=nava.kishore.manne@amd.com \
--cc=trix@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).