From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
"eugeniy.paltsev@synopsys.com" <eugeniy.paltsev@synopsys.com>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"robh@kernel.org" <robh@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"joao.pinto@synopsys.com" <joao.pinto@synopsys.com>
Cc: "linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v2] ARC: Add PCIe support for ARC HSDK platform
Date: Thu, 21 Jun 2018 09:07:54 -0700 [thread overview]
Message-ID: <f845c9f6-a020-5a4c-3a66-52e36c9f3d72@synopsys.com> (raw)
In-Reply-To: <e1d274a5ed756f86ced3df50538ef8c7e67ef4b6.1529589452.git.gustavo.pimentel@synopsys.com>
On 06/21/2018 07:06 AM, Gustavo Pimentel wrote:
> Add PCI support to the ARC HSDK platform allowing to use the generic PCI
> setup functions.
>
> Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
> Acked-by: Alexey Brodkin <abrodkin@synopsys.com>
Queued to #for-curr after minor fixed up to commit msg subject "ARC: [plat-hsdk]"
Curious, how exactly are you going to use PCI on hsdk ? What is the use case.
> ---
> arch/arc/plat-hsdk/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arc/plat-hsdk/Kconfig b/arch/arc/plat-hsdk/Kconfig
> index 19ab3cf..556bc5e 100644
> --- a/arch/arc/plat-hsdk/Kconfig
> +++ b/arch/arc/plat-hsdk/Kconfig
> @@ -9,3 +9,4 @@ menuconfig ARC_SOC_HSDK
> bool "ARC HS Development Kit SOC"
> select CLK_HSDK
> select RESET_HSDK
> + select MIGHT_HAVE_PCI
next prev parent reply other threads:[~2018-06-21 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 14:06 [PATCH v2] ARC: Add PCIe support for ARC HSDK platform Gustavo Pimentel
2018-06-21 16:07 ` Vineet Gupta [this message]
2018-06-21 16:26 ` Gustavo Pimentel
[not found] <9f41b2f9d6da018563fa35aee462ddb60afd922f.1529505192.git.gustavo.pimentel@synopsys.com>
2018-06-20 19:09 ` Alexey Brodkin
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=f845c9f6-a020-5a4c-3a66-52e36c9f3d72@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=bhelgaas@google.com \
--cc=eugeniy.paltsev@synopsys.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=joao.pinto@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=robh@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 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).