From: Bjorn Helgaas <helgaas@kernel.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: YueHaibing <yuehaibing@huawei.com>,
lorenzo.pieralisi@arm.com, robh@kernel.org,
l.stach@pengutronix.de, andrew.smirnov@gmail.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: keystone: Fix build error while only CONFIG_PCI_KEYSTONE is set
Date: Mon, 22 Apr 2019 08:26:17 -0500 [thread overview]
Message-ID: <20190422132617.GL173520@google.com> (raw)
In-Reply-To: <9e674a96-5d19-47f6-41a4-9a4313652b5b@ti.com>
On Mon, Apr 22, 2019 at 01:19:53PM +0530, Kishon Vijay Abraham I wrote:
> Hi Bjorn,
> ...
> Sometime back Niklas had fixed this for DRA7xx in
>
> commit b052835c63857e13d9ada3ebc57a8f9e1d124f3a
> Author: Niklas Cassel <niklas.cassel@axis.com>
> Date: Wed Dec 20 00:29:28 2017 +0100
>
> PCI: dwc: dra7xx: Refactor Kconfig and Makefile handling for host/ep mode
>
> Refactor the Kconfig and Makefile handling for host/ep mode, since
> the previous handling was a bit unorthodox and would have been a bit
> bloated once more DWC based controllers added support for ep mode.
>
> Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
>
> Something similar is applicable for Keystone too as you mentioned without
> selecting PCI_KEYSTONE_HOST or PCI_KEYSTONE_EP, compiling pci-keystone.c
> doesn't make sense.
>
> Please see if below looks okay to you. This can be merged with "PCI:
> keystone:Add support for PCIe EP in AM654x Platforms"). Let me know if I have
> to send it separately with Fixes tag.
Lorenzo merged that commit, so I assume he'll take care of this.
> 8<---------------------------------------------------------
> From 8fba36048112cf72c49996fc47fd808534bf9689 Mon Sep 17 00:00:00 2001
> From: Kishon Vijay Abraham I <kishon@ti.com>
> Date: Mon, 22 Apr 2019 11:42:32 +0530
> Subject: [PATCH] PCI: keystone: Refactor Kconfig for RC/EP mode
>
> Do not allow PCI_KEYSTONE to be visible to user and let user visible
> CONFIG symbols PCI_KEYSTONE_HOST and PCI_KEYSTONE_EP select
> PCI_KEYSTONE. This will let pci-keystone.c to be compiled only when
> either PCI_KEYSTONE_HOST or PCI_KEYSTONE_EP is selected.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
> drivers/pci/controller/dwc/Kconfig | 24 +++++++++++-------------
> 1 file changed, 11 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/Kconfig
> b/drivers/pci/controller/dwc/Kconfig
> index b450ad2823a5..90618233d15b 100644
> --- a/drivers/pci/controller/dwc/Kconfig
> +++ b/drivers/pci/controller/dwc/Kconfig
> @@ -103,34 +103,32 @@ config PCIE_SPEAR13XX
> Say Y here if you want PCIe support on SPEAr13XX SoCs.
>
> config PCI_KEYSTONE
> - bool "TI Keystone PCIe controller"
> - depends on ARCH_KEYSTONE || ARCH_K3 || ((ARM || ARM64) && COMPILE_TEST)
> - help
> - Say Y here if you want to enable PCI controller support on Keystone
> - SoCs. The PCI controller on Keystone is based on DesignWare hardware
> - and therefore the driver re-uses the DesignWare core functions to
> - implement the driver.
> -
> -if PCI_KEYSTONE
> + bool
>
> config PCI_KEYSTONE_HOST
> bool "PCI Keystone Host Mode"
> + depends on ARCH_KEYSTONE || ARCH_K3 || ((ARM || ARM64) && COMPILE_TEST)
> depends on PCI_MSI_IRQ_DOMAIN
> select PCIE_DW_HOST
> + select PCI_KEYSTONE
> default y
> help
> Enables support for the PCIe controller in the Keystone SoC to work in
> - host mode.
> + host mode. The PCI controller on Keystone is based on DesignWare hardware
> + and therefore the driver re-uses the DesignWare core functions to
> + implement the driver.
>
> config PCI_KEYSTONE_EP
> bool "PCI Keystone Endpoint Mode"
> + depends on ARCH_KEYSTONE || ARCH_K3 || ((ARM || ARM64) && COMPILE_TEST)
> depends on PCI_ENDPOINT
> select PCIE_DW_EP
> + select PCI_KEYSTONE
> help
> Enables support for the PCIe controller in the Keystone SoC to work in
> - endpoint mode.
> -
> -endif
> + endpoint mode. The PCI controller on Keystone is based on DesignWare hardware
> + and therefore the driver re-uses the DesignWare core functions to
> + implement the driver.
>
> config PCI_LAYERSCAPE
> bool "Freescale Layerscape PCIe controller"
> --
> 2.17.1
next prev parent reply other threads:[~2019-04-22 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 2:58 [PATCH] PCI: keystone: Fix build error while only CONFIG_PCI_KEYSTONE is set Yue Haibing
2019-04-19 13:31 ` Bjorn Helgaas
2019-04-19 13:46 ` YueHaibing
2019-04-19 17:47 ` Bjorn Helgaas
2019-04-22 7:49 ` Kishon Vijay Abraham I
2019-04-22 13:26 ` Bjorn Helgaas [this message]
2019-04-23 9:43 ` Lorenzo Pieralisi
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=20190422132617.GL173520@google.com \
--to=helgaas@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=yuehaibing@huawei.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 NNTP newsgroup(s).