From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Chen Subject: [PATCH v3 0/5] usb: change clock information for chipidea Date: Mon, 21 Sep 2015 08:43:01 +0800 Message-ID: <1442796186-2574-1-git-send-email-peter.chen@freescale.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, pawel.moll-5wv7dgnIgG8@public.gmane.org, mark.rutland-5wv7dgnIgG8@public.gmane.org, fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org, Peter Chen List-Id: devicetree@vger.kernel.org This patch set changes usb clock information for legacy i.mx platforms. At these platforms, they needs three clocks to let controller work. Hi Fabio, Would you please have a test at imx27 and imx25 boards, thanks. Changes for v3: - Delete property "needs-three-clocks", and using of_device_id->data to differentiate platforms - change #v3.19+ to #v4.1+ Changes for v2: - Add imx25 & imx27 dts change - Add Fabio's tested-by and Cc: #v3.19+ - Some typo and commit description Peter Chen (5): doc: dt-binding: ci-hdrc-usb2: split vendor specific properties ARM: dts: imx27.dtsi: change the clock information for usb ARM: dts: imx25.dtsi: change the clock information for usb ARM: dts: imx35.dtsi: change the clock information for usb usb: chipidea: imx: refine clock operations to adapt for all platforms .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 10 +- arch/arm/boot/dts/imx25.dtsi | 8 +- arch/arm/boot/dts/imx27.dtsi | 16 ++- arch/arm/boot/dts/imx35.dtsi | 8 +- drivers/usb/chipidea/ci_hdrc_imx.c | 156 ++++++++++++++++++--- 5 files changed, 164 insertions(+), 34 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html