From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Joao Pinto <Joao.Pinto@synopsys.com>
Cc: <Vineet.Gupta1@synopsys.com>, <arnd@arndb.de>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-snps-arc@lists.infradead.org>,
<CARLOS.PALMINHA@synopsys.com>, <Alexey.Brodkin@synopsys.com>,
<robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>
Subject: Re: [PATCH v8 2/2] add new platform driver for PCI RC
Date: Fri, 5 Feb 2016 10:44:29 +0000 [thread overview]
Message-ID: <56B47D0D.5030204@synopsys.com> (raw)
In-Reply-To: <20160204234334.GH7031@localhost>
Hi,
On 2/4/2016 11:43 PM, Bjorn Helgaas wrote:
>> What do you think?
>
> I don't think the "dw" part is relevant (none of the other
> DesignWare-based drivers includes it in the driver or file name).
>
> How do people typically refer to this board?
>
> I really like "synopsys" because it fits the pattern of being
> recognizable and pronounceable like "altera", "designware", "qcom",
> "keystone", "layerscape", "tegra", etc. But I can't tell whether it's
> too generic.
>
> "ipk" or "haps" would be fine with me. I think it's OK if it doesn't
> cover 100% of the possible systems.
I think we should follow the iproc example: pcie-iproc-platform.c
In this case we would have pcie-designware-platform.c
I think this would be the best name because the driver is a non soc specific
designware platform driver.
Arnd and Bjorn agree on this name?
>
> Bjorn
>
Joao
next prev parent reply other threads:[~2016-02-05 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 15:52 [PATCH v8 0/2] adding PCI support to AXS10x Joao Pinto
2016-02-04 15:52 ` [PATCH v8 1/2] PCI support added to ARC Joao Pinto
2016-02-04 15:52 ` [PATCH v8 2/2] add new platform driver for PCI RC Joao Pinto
2016-02-04 18:19 ` Bjorn Helgaas
2016-02-04 18:31 ` Joao Pinto
2016-02-04 23:43 ` Bjorn Helgaas
2016-02-05 10:44 ` Joao Pinto [this message]
2016-02-05 14:39 ` Arnd Bergmann
2016-02-05 14:51 ` Joao Pinto
2016-02-05 15:43 ` Arnd Bergmann
2016-02-05 15:50 ` Joao Pinto
2016-02-05 23:32 ` Bjorn Helgaas
2016-02-08 12:31 ` Arnd Bergmann
2016-02-08 12:52 ` Joao Pinto
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=56B47D0D.5030204@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=galak@codeaurora.org \
--cc=helgaas@kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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
Powered by JetHome