linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 01/14] usb: doc: phy-mxs: Add more compatible strings
Date: Fri, 20 Dec 2013 15:51:57 +0800	[thread overview]
Message-ID: <1387525930-27313-2-git-send-email-peter.chen@freescale.com> (raw)
In-Reply-To: <1387525930-27313-1-git-send-email-peter.chen@freescale.com>

Add "fsl,imx6q-usbphy" for imx6dq and imx6dl, add
"fsl,imx6sl-usbphy" for imx6sl.

Signed-off-by: Peter Chen <peter.chen@freescale.com>
---
 Documentation/devicetree/bindings/usb/mxs-phy.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/Documentation/devicetree/bindings/usb/mxs-phy.txt b/Documentation/devicetree/bindings/usb/mxs-phy.txt
index 5835b27..b43d4c9e 100644
--- a/Documentation/devicetree/bindings/usb/mxs-phy.txt
+++ b/Documentation/devicetree/bindings/usb/mxs-phy.txt
@@ -1,7 +1,8 @@
 * Freescale MXS USB Phy Device
 
 Required properties:
-- compatible: Should be "fsl,imx23-usbphy"
+- compatible: "fsl,imx23-usbphy" for imx23 and imx28, "fsl,imx6q-usbphy"
+  for imx6dq and imx6dl, "fsl,imx6sl-usbphy" for imx6sl
 - reg: Should contain registers location and length
 - interrupts: Should contain phy interrupt
 
-- 
1.7.8

  reply	other threads:[~2013-12-20  7:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  7:51 [PATCH v7 00/14] Add power management support for mxs phy Peter Chen
2013-12-20  7:51 ` Peter Chen [this message]
2013-12-20  7:51 ` [PATCH v7 02/14] usb: phy-mxs: Add platform judgement code Peter Chen
2013-12-20  7:51 ` [PATCH v7 03/14] usb: phy-mxs: Add auto clock and power setting Peter Chen
2013-12-20  7:52 ` [PATCH v7 04/14] usb: doc: phy-mxs: update binding for adding anatop phandle Peter Chen
2013-12-20  7:52 ` [PATCH v7 05/14] ARM: dts: imx6: add anatop phandle for usbphy Peter Chen
2013-12-20  7:52 ` [PATCH v7 06/14] usb: phy-mxs: Add anatop regmap Peter Chen
2013-12-24  0:15   ` Shawn Guo
2013-12-24  1:20     ` Peter Chen
2013-12-24  2:05       ` Shawn Guo
2013-12-20  7:52 ` [PATCH v7 07/14] usb: phy-mxs: change description of usb device speed Peter Chen
2013-12-20 10:40   ` David Laight
2013-12-23  1:05     ` Peter Chen
2013-12-20  7:52 ` [PATCH v7 08/14] usb: phy-mxs: Enable IC fixes for related SoCs Peter Chen
2013-12-20  7:52 ` [PATCH v7 09/14] ARM: dts: imx: add mxs phy controller id Peter Chen
2013-12-20  7:52 ` [PATCH v7 10/14] usb: phy-mxs: add " Peter Chen
2013-12-24  2:08   ` Shawn Guo
2013-12-24  1:34     ` Peter Chen
2013-12-24  2:25       ` Shawn Guo
2013-12-24  2:09         ` Peter Chen
2013-12-24  2:54           ` Shawn Guo
2013-12-20  7:52 ` [PATCH v7 11/14] usb: phy: Add set_wakeup API Peter Chen
2013-12-20  7:52 ` [PATCH v7 12/14] usb: phy-mxs: Add implementation of set_wakeup Peter Chen
2013-12-20  7:52 ` [PATCH v7 13/14] usb: phy-mxs: Add system suspend/resume API Peter Chen
2013-12-20  7:52 ` [PATCH v7 14/14] usb: phy-mxs: Add sync time after controller clear phcd Peter Chen
2013-12-23 16:58 ` [PATCH v7 00/14] Add power management support for mxs phy Felipe Balbi

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=1387525930-27313-2-git-send-email-peter.chen@freescale.com \
    --to=peter.chen@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).