Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932765AbaKMLsL (ORCPT ); Thu, 13 Nov 2014 06:48:11 -0500 Received: from down.free-electrons.com ([37.187.137.238]:39185 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932552AbaKMLsJ (ORCPT ); Thu, 13 Nov 2014 06:48:09 -0500 From: Gregory CLEMENT To: "Kishon Vijay Abraham I" , Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Gregory CLEMENT Cc: Thomas Petazzoni , Ezequiel Garcia , linux-arm-kernel@lists.infradead.org, Lior Amsalem , Tawfik Bayouk , Nadav Haklai , Mark Rutland , devicetree@vger.kernel.org, Grant Likely , Rob Herring , linux-kernel@vger.kernel.org Subject: [PATCH v4 0/7] Add support for USB cluster(PHY muxer) on the Armada 375 Date: Thu, 13 Nov 2014 12:47:42 +0100 Message-Id: <1415879269-29711-1-git-send-email-gregory.clement@free-electrons.com> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, this is the forth version of a series adding support for the USB cluster which is on the Armada 375 SoC. We can mainly see this device as a PHY muxer. Since the last version I no more use a global variable and store it now in the platform data as suggested by Kishon. I also add a new patch adding myself as maintainer of this driver. While I ran coccicheck on my code I also found some possible improvement in the phy driver: it was done in the 1st patch. The second patch was a patch initially submitted by Andrew. This patch added the mvebu-phy.txt but fell through a crack when adding the driver. I join this patch on my series in order to be able to add the new binding for the USB cluster of the Armada 375. This was done in the third patch. The forth patch was the addition of the phys driver itself. The fifth and sixth patches are updating the device tree files related to the Armada 375 using the new biding. The seventh patch add myself as maintainer of this driver. Thanks, Gregory Changelog: v3 -> v4: - No more use a global variable to store the data related to the usb cluster and put them in the platform data instead. - Add more check on the NULL pointer in the driver to make it more robust. - Add a new patch to dd myself as maintainer of this driver. v2 -> v3: - Added Kishon acked-by on the 5th patch. - Used include/dt-bindings/phy/phy.h instead of creating a new one in the forth patch. v1 -> v2: - Add a patch fixing the use of PTR_ERR_OR_ZERO. - Add the patch adding the DT binding documentation for Marvell MVEBU SATA phy from Andrew Lunn - Move the DT binding documentation of the Armada 375 USB cluster into the phy-mvebu.txt file. - Made the armada375_usb_phy_xlate more robust" if there is a phy_put and then a phy_get". Andrew Lunn (1): Phy: DT binding documentation for Marvell MVEBU SATA phy. Gregory CLEMENT (6): phy: Use PTR_ERR_OR_ZERO to fix warning raised by coccinelle Phy: DT binding documentation for the Armada 375 USB cluster binding phy: add support for USB cluster on the Armada 375 SoC ARM: mvebu: add Device Tree description of USB cluster controller on Armada 375 ARM: mvebu: add PHY support to the dts for the USB controllers on Armada 375 MAINTAINERS: add entry for the Armada 375 USB cluster PHY driver Documentation/devicetree/bindings/ata/marvell.txt | 6 + .../devicetree/bindings/phy/phy-mvebu.txt | 43 ++++++ MAINTAINERS | 6 + arch/arm/boot/dts/armada-375.dtsi | 11 ++ drivers/phy/Kconfig | 6 + drivers/phy/Makefile | 1 + drivers/phy/phy-armada375-usb2.c | 158 +++++++++++++++++++++ drivers/phy/phy-berlin-sata.c | 5 +- drivers/phy/phy-hix5hd2-sata.c | 5 +- drivers/phy/phy-miphy365x.c | 5 +- drivers/phy/phy-stih41x-usb.c | 5 +- include/dt-bindings/phy/phy.h | 1 + 12 files changed, 236 insertions(+), 16 deletions(-) create mode 100644 Documentation/devicetree/bindings/phy/phy-mvebu.txt create mode 100644 drivers/phy/phy-armada375-usb2.c -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/