From: Sergey Temerkhanov <sergey.temerkhanov@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org
Subject: [PATCH iwl-next v5 1/6] ice: dpll: Add the MUX tables to the documentation
Date: Mon, 31 Aug 2026 14:50:00 +0000 [thread overview]
Message-ID: <20260831145005.191040-2-sergey.temerkhanov@intel.com> (raw)
In-Reply-To: <20260831145005.191040-1-sergey.temerkhanov@intel.com>
Add the tables documenting the DPLL pin MUX states and behavior
to the driver.
Signed-off-by: Sergey Temerkhanov <sergey.temerkhanov@intel.com>
---
drivers/net/ethernet/intel/ice/ice_dpll.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/drivers/net/ethernet/intel/ice/ice_dpll.c b/drivers/net/ethernet/intel/ice/ice_dpll.c
index 382fbe98f2b0..9b3584fa43a9 100644
--- a/drivers/net/ethernet/intel/ice/ice_dpll.c
+++ b/drivers/net/ethernet/intel/ice/ice_dpll.c
@@ -92,6 +92,29 @@ static const struct dpll_pin_frequency ice_esync_range[] = {
DPLL_PIN_FREQUENCY_RANGE(0, DPLL_PIN_FREQUENCY_1_HZ),
};
+/*
+ * SMA1/U.FL1 MUX table
+ *+----------------+-------------+------------+
+ *| | SMA1_DIR_EN | SMA1_TX_EN |
+ *+----------------+-------------+------------+
+ *|SMA1 RX Enable | 0 | x |
+ *|u.FL1 TX Enable | 0 | 0 |
+ *|SMA1 TX Enable | 1 | 0 |
+ *|All Disable | 1 | 1 |
+ *+----------------+-------------+------------+
+ *
+ * SMA2/U.FL2 MUX table
+ *+----------------+-------------+------------+------------+
+ *| | SMA2_DIR_EN | SMA2_TX_EN | UFL2_RX_EN |
+ *+----------------+-------------+------------+------------+
+ *|SMA2 RX Enable | 0 | x | x |
+ *|u.FL2 RX Enable | 1 | x | 0 |
+ *|SMA2 TX Enable | 1 | 0 | x |
+ *|SMA2 Disable | 1 | 1 | x |
+ *|All Disable | 1 | 1 | 1 |
+ *+----------------+-------------+------------+------------+
+ */
+
/**
* ice_dpll_is_sw_pin - check if given pin shall be controlled by SW
* @pf: private board structure
--
2.53.0
next prev parent reply other threads:[~2026-08-31 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:49 [PATCH iwl-next v5 0/6] Rework dpll pin control Sergey Temerkhanov
2026-08-31 14:50 ` Sergey Temerkhanov [this message]
2026-08-31 14:50 ` [PATCH iwl-next v5 2/6] ice: dpll: Rework multiplexed pin notifications Sergey Temerkhanov
2026-08-31 14:50 ` [PATCH iwl-next v5 3/6] ice: dpll: Use switch statements to handle pin states Sergey Temerkhanov
2026-08-31 14:50 ` [PATCH iwl-next v5 4/6] ice: dpll: Check for bounds when updating the " Sergey Temerkhanov
2026-08-31 14:50 ` [PATCH iwl-next v5 5/6] ice: dpll: Rework U.FL muxed pin (SMA) control Sergey Temerkhanov
2026-08-31 14:50 ` [PATCH iwl-next v5 6/6] ice: dpll: Rework the SMA control logic to match the requirements Sergey Temerkhanov
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=20260831145005.191040-2-sergey.temerkhanov@intel.com \
--to=sergey.temerkhanov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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