From: Kishon Vijay Abraham I <kishon@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<nsekhar@ti.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Minghuan Lian <minghuan.Lian@freescale.com>,
Mingkai Hu <mingkai.hu@freescale.com>,
Roy Zang <tie-fei.zang@freescale.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
Murali Karicheri <m-karicheri2@ti.com>,
Jingoo Han <jingoohan1@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Pratyush Anand <pratyush.anand@gmail.com>,
Niklas Cassel <niklas.cassel@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Stanimir Varbanov <svarbanov@mm-sol.com>
Subject: Re: [PATCH v5] PCI: add a new directory for designware core
Date: Fri, 6 Jan 2017 18:42:24 +0530 [thread overview]
Message-ID: <586F97B8.8040300@ti.com> (raw)
In-Reply-To: <4757539.Mx4pNLiAHf@wuerfel>
Hi Arnd,
On Friday 06 January 2017 06:31 PM, Arnd Bergmann wrote:
> On Friday, January 6, 2017 6:22:48 PM CET Kishon Vijay Abraham I wrote:
>> Group all the PCI drivers that use designware core in dwc directory.
>> dwc IP is capable of operating in both host mode and device mode and
>> keeping it inside the *host* directory is misleading.
>
> I have no objections to the patch, it makes a lot of sense, but I think
> the reasoning above is a bit questionable, as a lot of the other
> host drivers (at least tegra, mvebu and xgene, probably more) equally support
> endpoint mode and remain in the same directory.
>
> Any suggestion to what we should do with them?
I'm not sure of the exact IP's used by these SoCs. Now that we decided to group
the drivers by IPs used, the best would be identify the IPs used in these SoCs
and create a separate directory for each of the IPs. If the vendors own IP is
used, then create a directory with the name of the vendor?. I'm sure such a
change would increase the number of directories but I'm not sure what else to
do here.
Thanks
Kishon
next prev parent reply other threads:[~2017-01-06 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 12:52 [PATCH v5] PCI: add a new directory for designware core Kishon Vijay Abraham I
2017-01-06 13:01 ` Arnd Bergmann
2017-01-06 13:12 ` Kishon Vijay Abraham I [this message]
2017-01-06 13:40 ` Joao Pinto
2017-01-09 9:31 ` Kishon Vijay Abraham I
2017-02-03 19:19 ` Bjorn Helgaas
2017-02-06 12:28 ` Kishon Vijay Abraham I
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=586F97B8.8040300@ti.com \
--to=kishon@ti.com \
--cc=Joao.Pinto@synopsys.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=hongxing.zhu@nxp.com \
--cc=jesper.nilsson@axis.com \
--cc=jingoohan1@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=minghuan.Lian@freescale.com \
--cc=mingkai.hu@freescale.com \
--cc=niklas.cassel@axis.com \
--cc=nsekhar@ti.com \
--cc=pratyush.anand@gmail.com \
--cc=svarbanov@mm-sol.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tie-fei.zang@freescale.com \
--cc=wangzhou1@hisilicon.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).