From: Simon Horman <horms@verge.net.au>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-pci <linux-pci@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] PCI: rcar, rcar-gen2: Use ARCH_RENESAS
Date: Mon, 29 Feb 2016 09:36:18 +0900 [thread overview]
Message-ID: <20160229003618.GA25079@verge.net.au> (raw)
In-Reply-To: <HK2PR0601MB1393372115B466FBB5F2D4EEF5A70@HK2PR0601MB1393.apcprd06.prod.outlook.com>
On Fri, Feb 26, 2016 at 09:22:04AM +0000, Phil Edworthy wrote:
> Hi Geert,
>
> On 25 February 2016 08:05, Geert Uytterhoeven wrote:
> > On Thu, Feb 25, 2016 at 1:45 AM, Simon Horman
> > <horms+renesas@verge.net.au> wrote:
> > > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
> > >
> > > This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> > > ARCH_RENESAS the motivation for which being that RENESAS seems to be a
> > more
> > > appropriate name than SHMOBILE for the majority of Renesas ARM based
> > SoCs.
> > >
> > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >
> > Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > > --- a/drivers/pci/host/Kconfig
> > > +++ b/drivers/pci/host/Kconfig
> >
> > > @@ -49,7 +49,7 @@ config PCI_RCAR_GEN2
> > >
> > > config PCI_RCAR_GEN2_PCIE
> > > bool "Renesas R-Car PCIe controller"
> > > - depends on ARCH_SHMOBILE || (ARM && COMPILE_TEST)
> > > + depends on ARCH_RENESAS || (ARM && COMPILE_TEST)
> > > help
> > > Say Y here if you want PCIe controller support on R-Car Gen2 SoCs.
> >
> > BTW, this looks like a misnomer: the driver supports a compatible value for
> > R-Car H1, too ("renesas,pcie-r8a7779"), but it's not used in r8a7779.dtsi.
> IIRC, H1 PCIe support was nobbled in some way that meant you could not
> use it with any normal PCIe card. You could connect to another R-Car that
> was acting as an endpoint though.
It sounds like that might be worth documenting somewhere.
In any case, I think we could s/Gen2 // in the text above.
next prev parent reply other threads:[~2016-02-29 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 0:45 [PATCH] PCI: rcar, rcar-gen2: Use ARCH_RENESAS Simon Horman
2016-02-25 8:04 ` Geert Uytterhoeven
2016-02-26 9:22 ` Phil Edworthy
2016-02-29 0:36 ` Simon Horman [this message]
2016-03-08 18:36 ` Bjorn Helgaas
2016-03-11 1:49 ` Simon Horman
2016-03-11 18:13 ` Bjorn Helgaas
2016-03-11 18:08 ` Bjorn Helgaas
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=20160229003618.GA25079@verge.net.au \
--to=horms@verge.net.au \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=phil.edworthy@renesas.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).