From: Dilip Kota <eswara.kota@linux.intel.com>
To: linux-kernel@vger.kernel.org, kishon@ti.com, vkoul@kernel.org,
devicetree@vger.kernel.org
Cc: robh@kernel.org, andriy.shevchenko@intel.com,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, yixin.zhu@intel.com,
Dilip Kota <eswara.kota@linux.intel.com>
Subject: [RESEND PATCH v8 1/3] dt-bindings: phy: Add PHY_TYPE_XPCS definition
Date: Fri, 15 May 2020 16:13:33 +0800 [thread overview]
Message-ID: <6091f0d2a1046f1e3656d9e33b6cc433d5465eaf.1589530082.git.eswara.kota@linux.intel.com> (raw)
In-Reply-To: <cover.1589530082.git.eswara.kota@linux.intel.com>
In-Reply-To: <cover.1589530082.git.eswara.kota@linux.intel.com>
Add definition for Ethernet PCS phy type.
Signed-off-by: Dilip Kota <eswara.kota@linux.intel.com>
Acked-by: Rob Herring <robh@kernel.org>
---
Changes on v8:
No Change
Changes on v7:
No Change
Changes on v6:
Add Acked-by: Rob Herring <robh@kernel.org>
include/dt-bindings/phy/phy.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/phy/phy.h b/include/dt-bindings/phy/phy.h
index 1f3f866fae7b..3727ef72138b 100644
--- a/include/dt-bindings/phy/phy.h
+++ b/include/dt-bindings/phy/phy.h
@@ -17,5 +17,6 @@
#define PHY_TYPE_USB3 4
#define PHY_TYPE_UFS 5
#define PHY_TYPE_DP 6
+#define PHY_TYPE_XPCS 7
#endif /* _DT_BINDINGS_PHY */
--
2.11.0
next prev parent reply other threads:[~2020-05-15 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 8:13 [RESEND PATCH v8 0/3] Add Intel ComboPhy driver Dilip Kota
2020-05-15 8:13 ` Dilip Kota [this message]
2020-05-15 8:13 ` [RESEND PATCH v8 2/3] dt-bindings: phy: Add YAML schemas for Intel ComboPhy Dilip Kota
2020-05-15 8:13 ` [RESEND PATCH v8 3/3] phy: intel: Add driver support for ComboPhy Dilip Kota
2020-05-18 12:41 ` [RESEND PATCH v8 0/3] Add Intel ComboPhy driver Vinod Koul
2020-05-18 13:49 ` Kishon Vijay Abraham I
2020-05-19 3:56 ` Dilip Kota
2020-05-19 5:17 ` Kishon Vijay Abraham I
2020-05-19 5:25 ` Dilip Kota
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=6091f0d2a1046f1e3656d9e33b6cc433d5465eaf.1589530082.git.eswara.kota@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=yixin.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).