| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 8 Jul 2014 08:49:00 -0400 From: Murali Karicheri <m-karicheri2@...com> To: Bjorn Helgaas <bhelgaas@...gle.com> CC: <linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, Santosh Shilimkar <santosh.shilimkar@...com>, Russell King <linux@....linux.org.uk>, Grant Likely <grant.likely@...aro.org>, Rob Herring <robh+dt@...nel.org>, Mohit Kumar <mohit.kumar@...com>, Jingoo Han <jg1.han@...sung.com>, Pratyush Anand <pratyush.anand@...com>, Richard Zhu <r65037@...escale.com>, Kishon Vijay Abraham I <kishon@...com>, Marek Vasut <marex@...x.de>, Arnd Bergmann <arnd@...db.de>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org>, Randy Dunlap <rdunlap@...radead.org> Subject: Re: [PATCH v3 0/5] Add Keystone PCIe controller driver 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@...com> >> CC: Russell King<linux@....linux.org.uk> >> CC: Grant Likely<grant.likely@...aro.org> >> CC: Rob Herring<robh+dt@...nel.org> >> CC: Mohit Kumar<mohit.kumar@...com> >> CC: Jingoo Han<jg1.han@...sung.com> >> CC: Bjorn Helgaas<bhelgaas@...gle.com> >> CC: Pratyush Anand<pratyush.anand@...com> >> CC: Richard Zhu<r65037@...escale.com> >> CC: Kishon Vijay Abraham I<kishon@...com> >> CC: Marek Vasut<marex@...x.de> >> CC: Arnd Bergmann<arnd@...db.de> >> CC: Pawel Moll<pawel.moll@....com> >> CC: Mark Rutland<mark.rutland@....com> >> CC: Ian Campbell<ijc+devicetree@...lion.org.uk> >> CC: Kumar Gala<galak@...eaurora.org> >> CC: Randy Dunlap<rdunlap@...radead.org> >> CC: Grant Likely<grant.likely@...aro.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 >> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists