From: Swapnil Jakhade <sjakhade@cadence.com>
To: <vkoul@kernel.org>, <kishon@ti.com>,
<linux-kernel@vger.kernel.org>, <maxime@cerno.tech>,
<Laurent.pinchart@ideasonboard.com>
Cc: <mparab@cadence.com>, <sjakhade@cadence.com>,
<yamonkar@cadence.com>, <nsekhar@ti.com>, <tomi.valkeinen@ti.com>,
<jsarha@ti.com>, <praneeth@ti.com>
Subject: [PATCH v6 1/2] phy: Add new PHY attribute max_link_rate
Date: Fri, 11 Sep 2020 08:18:33 +0200 [thread overview]
Message-ID: <1599805114-22063-2-git-send-email-sjakhade@cadence.com> (raw)
In-Reply-To: <1599805114-22063-1-git-send-email-sjakhade@cadence.com>
Add new PHY attribute max_link_rate to struct phy_attrs. This indicates
maximum link rate supported by PHY (in Mbps).
Signed-off-by: Yuti Amonkar <yamonkar@cadence.com>
Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
---
include/linux/phy/phy.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index bcee8eba62b3..e435bdb0bab3 100644
--- a/include/linux/phy/phy.h
+++ b/include/linux/phy/phy.h
@@ -115,10 +115,12 @@ struct phy_ops {
/**
* struct phy_attrs - represents phy attributes
* @bus_width: Data path width implemented by PHY
+ * @max_link_rate: Maximum link rate supported by PHY (in Mbps)
* @mode: PHY mode
*/
struct phy_attrs {
u32 bus_width;
+ u32 max_link_rate;
enum phy_mode mode;
};
--
2.26.1
next prev parent reply other threads:[~2020-09-11 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 6:18 [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate Swapnil Jakhade
2020-09-11 6:18 ` Swapnil Jakhade [this message]
2020-09-15 23:00 ` [PATCH v6 1/2] phy: " Laurent Pinchart
2020-09-11 6:18 ` [PATCH v6 2/2] phy: cadence-torrent: Set Torrent PHY attributes Swapnil Jakhade
2020-09-15 23:01 ` Laurent Pinchart
2020-09-16 7:41 ` [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate Sekhar Nori
2020-09-16 12:09 ` Vinod Koul
2020-09-16 12:18 ` Laurent Pinchart
2020-09-16 12:43 ` Vinod Koul
2020-09-16 17:27 ` Sekhar Nori
2020-09-16 17:34 ` Laurent Pinchart
2020-09-16 12:08 ` Vinod Koul
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=1599805114-22063-2-git-send-email-sjakhade@cadence.com \
--to=sjakhade@cadence.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=jsarha@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mparab@cadence.com \
--cc=nsekhar@ti.com \
--cc=praneeth@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=vkoul@kernel.org \
--cc=yamonkar@cadence.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.