From: Murali Karicheri <m-karicheri2@ti.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Russell King <linux@arm.linux.org.uk>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mohit Kumar <mohit.kumar@st.com>,
Jingoo Han <jg1.han@samsung.com>,
Pratyush Anand <pratyush.anand@st.com>,
Richard Zhu <r65037@freescale.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Marek Vasut <marex@denx.de>, Arnd Bergmann <arnd@arndb.de>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3 0/5] Add Keystone PCIe controller driver
Date: Tue, 8 Jul 2014 08:49:00 -0400 [thread overview]
Message-ID: <53BBE8BC.2090302@ti.com> (raw)
In-Reply-To: <20140705182332.GB28871@google.com>
On 07/05/2014 02:23 PM, Bjorn Helgaas wrote:
> On Mon, Jun 30, 2014 at 05:45:15PM -0400, Murali Karicheri wrote:
>> This patch add PCIe controller driver for Keystone SoCs. This
>> is based on v2 of the series posted to the mailing list.
>> Keystone PCI controller is based on version 3.65 of the DW
>> hardware. This driver re-uses some of the DW core driver
>> functions and required modification in some to support
>> the old DW h/w based Keystone driver.
>>
>> Please review and let me know if you have any comments.
>
> I'm waiting for acks from Mohit or Jingoo for the designware changes.
>
Bjorn,
Thanks for your email.
So far I got Ack for 1/5 and 2/5. I will ping them today for 3/5 and 4/5.
> I'd also like an ack from the devicetree folks for the Keystone binding.
>
Ok
> And I think we need a MAINTAINERS update for drivers/pci/host/\*keystone\*
I will address your comments against 5/5 and discuss them if any and
make the above update for v4 and send the patch set to the list.
Thanks and regards,
Murali
>
>> CC: Santosh Shilimkar<santosh.shilimkar@ti.com>
>> CC: Russell King<linux@arm.linux.org.uk>
>> CC: Grant Likely<grant.likely@linaro.org>
>> CC: Rob Herring<robh+dt@kernel.org>
>> CC: Mohit Kumar<mohit.kumar@st.com>
>> CC: Jingoo Han<jg1.han@samsung.com>
>> CC: Bjorn Helgaas<bhelgaas@google.com>
>> CC: Pratyush Anand<pratyush.anand@st.com>
>> CC: Richard Zhu<r65037@freescale.com>
>> CC: Kishon Vijay Abraham I<kishon@ti.com>
>> CC: Marek Vasut<marex@denx.de>
>> CC: Arnd Bergmann<arnd@arndb.de>
>> CC: Pawel Moll<pawel.moll@arm.com>
>> CC: Mark Rutland<mark.rutland@arm.com>
>> CC: Ian Campbell<ijc+devicetree@hellion.org.uk>
>> CC: Kumar Gala<galak@codeaurora.org>
>> CC: Randy Dunlap<rdunlap@infradead.org>
>> CC: Grant Likely<grant.likely@linaro.org>
>>
>> Changelog:
>>
>> v3
>> - DW application register handling code is now part of
>> Keystone PCI driver. RFC had this code part of Keystone
>> PCI driver, then V1 moved this to a separate file to
>> re-use on other platforms that uses this version of the
>> DW h/w. Then based on comments against v2, this is moved
>> back to Keystone driver.
>> - Keystone SerDes phy driver is removed from this series so that
>> this can be merged independent of that patch
>> - added msi_set_irq()/clear_irq() API's to support Keystone
>>
>> V2
>> - Split the designware pcie enhancement patch to multiple
>> patches based on functionality added
>> - Remove the quirk code and add a patch to fix mps/mrss
>> tuning for ARM. Use kernel command line parameter
>> pci=pcie_bus_perf to work with Keystone PCI Controller.
>> Following patch addressed this.
>> [PATCH v1] ARM: pci: add call to pcie_bus_configure_settings()
>> - Add documentation for device tree bindings
>> - Add separate interrupt controller nodes for MSI and Legacy
>> IRQs and use irq map for legacy IRQ
>> - Use compatibility to identify v3.65 version of the DW hardware
>> and use it to customize the designware common code.
>> - Use reg property for configuration space instead of range
>> - Other minor updates based on code inspection.
>>
>> V1
>> - Add an interrupt controller node for Legacy irq chip and use
>> interrupt map/map-mask property to map legacy IRQs A/B/C/D
>> - Add a Phy driver to replace the original serdes driver
>> - Move common application register handling code to a separate
>> file to allow re-use across other platforms that use older
>> DW PCIe h/w
>> - PCI quirk for maximum read request size. Check and override only
>> if the maximum is higher than what controller can handle.
>> - Converted to a module platform driver.
>>
>> Murali Karicheri (5):
>> PCI: designware: add rd[wr]_other_conf API
>> PCI: designware: refactor MSI code to work with v3.65 dw hardware
>> PCI: designware: refactor host init code to re-use on keystone PCI
>> PCI: designware: enhance dw core driver to support Keystone PCI host
>> controller
>> PCI: add PCI controller for Keystone PCIe h/w
>>
>> .../devicetree/bindings/pci/designware-pcie.txt | 2 +
>> .../devicetree/bindings/pci/pci-keystone.txt | 69 +++
>> drivers/pci/host/Kconfig | 5 +
>> drivers/pci/host/Makefile | 1 +
>> drivers/pci/host/pci-keystone-dw.c | 523 ++++++++++++++++++++
>> drivers/pci/host/pci-keystone.c | 381 ++++++++++++++
>> drivers/pci/host/pci-keystone.h | 56 +++
>> drivers/pci/host/pcie-designware.c | 206 ++++++--
>> drivers/pci/host/pcie-designware.h | 17 +-
>> 9 files changed, 1207 insertions(+), 53 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/pci/pci-keystone.txt
>> create mode 100644 drivers/pci/host/pci-keystone-dw.c
>> create mode 100644 drivers/pci/host/pci-keystone.c
>> create mode 100644 drivers/pci/host/pci-keystone.h
>>
>> --
>> 1.7.9.5
>>
next prev parent reply other threads:[~2014-07-08 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:45 Murali Karicheri
2014-06-30 21:45 ` [PATCH v3 1/5] PCI: designware: add rd[wr]_other_conf API Murali Karicheri
2014-07-07 4:11 ` Mohit KUMAR DCG
2014-07-07 16:53 ` Murali Karicheri
2014-07-08 12:17 ` Jingoo Han
2014-06-30 21:45 ` [PATCH v3 2/5] PCI: designware: refactor MSI code to work with v3.65 dw hardware Murali Karicheri
2014-07-07 4:17 ` Mohit KUMAR DCG
2014-07-07 16:53 ` Murali Karicheri
2014-07-08 12:20 ` Jingoo Han
2014-06-30 21:45 ` [PATCH v3 3/5] PCI: designware: refactor host init code to re-use on keystone PCI Murali Karicheri
2014-07-08 13:20 ` Murali Karicheri
2014-07-08 13:31 ` Jingoo Han
2014-06-30 21:45 ` [PATCH v3 4/5] PCI: designware: enhance dw core driver to support Keystone PCI host controller Murali Karicheri
2014-07-08 13:24 ` Murali Karicheri
2014-06-30 21:45 ` [PATCH v3 5/5] PCI: add PCI controller for Keystone PCIe h/w Murali Karicheri
2014-07-05 18:45 ` Bjorn Helgaas
2014-07-08 12:43 ` Jingoo Han
2014-07-08 13:25 ` Murali Karicheri
2014-07-05 18:23 ` [PATCH v3 0/5] Add Keystone PCIe controller driver Bjorn Helgaas
2014-07-08 12:49 ` Murali Karicheri [this message]
2014-07-09 13:52 ` Santosh Shilimkar
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=53BBE8BC.2090302@ti.com \
--to=m-karicheri2@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jg1.han@samsung.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=mohit.kumar@st.com \
--cc=pawel.moll@arm.com \
--cc=pratyush.anand@st.com \
--cc=r65037@freescale.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.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
Powered by JetHome