From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-phy@lists.infradead.org>,
Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, <linux-can@vger.kernel.org>,
<netdev@vger.kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>
Subject: [PATCH v2 1/6] phy: core: Reword the comment specifying the units of max_link_rate to be Mbps
Date: Wed, 14 Apr 2021 19:35:16 +0530 [thread overview]
Message-ID: <20210414140521.11463-2-a-govindraju@ti.com> (raw)
In-Reply-To: <20210414140521.11463-1-a-govindraju@ti.com>
In some subsystems (eg. CAN, SPI), the max link rate supported can be less
than 1 Mbps and if the unit for max_link_rate is Mbps then it can't be
used. Therefore, leave the decision of units to be used, to the producer
and consumer.
Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
---
include/linux/phy/phy.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index 0ed434d02196..f3286f4cd306 100644
--- a/include/linux/phy/phy.h
+++ b/include/linux/phy/phy.h
@@ -125,7 +125,7 @@ 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)
+ * @max_link_rate: Maximum link rate supported by PHY (units to be decided by producer and consumer)
* @mode: PHY mode
*/
struct phy_attrs {
--
2.17.1
next prev parent reply other threads:[~2021-04-14 14:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 14:05 [PATCH v2 0/6] CAN TRANSCEIVER: Add support for CAN transceivers Aswath Govindraju
2021-04-14 14:05 ` Aswath Govindraju [this message]
2021-04-14 14:05 ` [PATCH v2 2/6] phy: Add API for devm_of_phy_optional_get_by_index Aswath Govindraju
2021-04-14 14:05 ` [PATCH v2 3/6] dt-bindings: phy: Add binding for TI TCAN104x CAN transceivers Aswath Govindraju
2021-04-14 15:33 ` Marc Kleine-Budde
2021-04-15 6:27 ` Aswath Govindraju
2021-04-15 7:38 ` Marc Kleine-Budde
2021-04-15 9:11 ` Aswath Govindraju
2021-04-15 9:15 ` Marc Kleine-Budde
2021-04-14 14:05 ` [PATCH v2 4/6] phy: phy-can-transceiver: Add support for generic CAN transceiver driver Aswath Govindraju
2021-04-14 15:39 ` Marc Kleine-Budde
2021-04-14 15:40 ` Marc Kleine-Budde
2021-04-15 7:44 ` kernel test robot
2021-04-15 9:12 ` kernel test robot
2021-04-14 14:05 ` [PATCH v2 5/6] dt-bindings: net: can: Document transceiver implementation as phy Aswath Govindraju
2021-04-14 14:05 ` [PATCH v2 6/6] can: m_can: Add support for transceiver " Aswath Govindraju
2021-04-14 15:15 ` Marc Kleine-Budde
2021-04-14 15:43 ` [PATCH v2 0/6] CAN TRANSCEIVER: Add support for CAN transceivers Marc Kleine-Budde
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=20210414140521.11463-2-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rcsekar@samsung.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=wg@grandegger.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).