From: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Menachem Adin <menachem.adin@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [char-misc-next 3/7] mei: me: move trace into firmware status read
Date: Sun, 1 Feb 2026 11:43:54 +0200 [thread overview]
Message-ID: <20260201094358.1440593-4-alexander.usyskin@intel.com> (raw)
In-Reply-To: <20260201094358.1440593-1-alexander.usyskin@intel.com>
Move register trace near it actual read in the firmware status callback
and make it adhere to the actual read type.
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
---
drivers/misc/mei/gsc-me.c | 3 ++-
drivers/misc/mei/hw-me.c | 11 +++--------
drivers/misc/mei/hw-me.h | 2 +-
drivers/misc/mei/pci-me.c | 8 ++++++--
4 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/misc/mei/gsc-me.c b/drivers/misc/mei/gsc-me.c
index 93cba090ea08..73d5beeb9c34 100644
--- a/drivers/misc/mei/gsc-me.c
+++ b/drivers/misc/mei/gsc-me.c
@@ -23,11 +23,12 @@
#define MEI_GSC_RPM_TIMEOUT 500
-static int mei_gsc_read_hfs(const struct mei_device *dev, int where, u32 *val)
+static int mei_gsc_read_hfs(const struct mei_device *dev, int where, const char *name, u32 *val)
{
struct mei_me_hw *hw = to_me_hw(dev);
*val = ioread32(hw->mem_addr + where + 0xC00);
+ trace_mei_reg_read(&dev->dev, name, where, *val);
return 0;
}
diff --git a/drivers/misc/mei/hw-me.c b/drivers/misc/mei/hw-me.c
index d4612c659784..c0d4a02d9cae 100644
--- a/drivers/misc/mei/hw-me.c
+++ b/drivers/misc/mei/hw-me.c
@@ -215,11 +215,8 @@ static int mei_me_fw_status(struct mei_device *dev,
fw_status->count = fw_src->count;
for (i = 0; i < fw_src->count && i < MEI_FW_STATUS_MAX; i++) {
- ret = hw->read_fws(dev, fw_src->status[i],
+ ret = hw->read_fws(dev, fw_src->status[i], "PCI_CFG_HFS_X",
&fw_status->status[i]);
- trace_mei_pci_cfg_read(&dev->dev, "PCI_CFG_HFS_X",
- fw_src->status[i],
- fw_status->status[i]);
if (ret)
return ret;
}
@@ -250,8 +247,7 @@ static int mei_me_hw_config(struct mei_device *dev)
hw->hbuf_depth = (hcsr & H_CBD) >> 24;
reg = 0;
- hw->read_fws(dev, PCI_CFG_HFS_1, ®);
- trace_mei_pci_cfg_read(&dev->dev, "PCI_CFG_HFS_1", PCI_CFG_HFS_1, reg);
+ hw->read_fws(dev, PCI_CFG_HFS_1, "PCI_CFG_HFS_1", ®);
hw->d0i3_supported =
((reg & PCI_CFG_HFS_1_D0I3_MSK) == PCI_CFG_HFS_1_D0I3_MSK);
@@ -446,8 +442,7 @@ static void mei_gsc_pxp_check(struct mei_device *dev)
if (!kind_is_gsc(dev) && !kind_is_gscfi(dev))
return;
- hw->read_fws(dev, PCI_CFG_HFS_5, &fwsts5);
- trace_mei_pci_cfg_read(&dev->dev, "PCI_CFG_HFS_5", PCI_CFG_HFS_5, fwsts5);
+ hw->read_fws(dev, PCI_CFG_HFS_5, "PCI_CFG_HFS_5", &fwsts5);
if ((fwsts5 & GSC_CFG_HFS_5_BOOT_TYPE_MSK) == GSC_CFG_HFS_5_BOOT_TYPE_PXP) {
if (dev->gsc_reset_to_pxp == MEI_DEV_RESET_TO_PXP_DEFAULT)
diff --git a/drivers/misc/mei/hw-me.h b/drivers/misc/mei/hw-me.h
index 843ec2497b52..9df5899d2602 100644
--- a/drivers/misc/mei/hw-me.h
+++ b/drivers/misc/mei/hw-me.h
@@ -56,7 +56,7 @@ struct mei_me_hw {
enum mei_pg_state pg_state;
bool d0i3_supported;
u8 hbuf_depth;
- int (*read_fws)(const struct mei_device *dev, int where, u32 *val);
+ int (*read_fws)(const struct mei_device *dev, int where, const char *name, u32 *val);
/* polling */
struct task_struct *polling_thread;
wait_queue_head_t wait_active;
diff --git a/drivers/misc/mei/pci-me.c b/drivers/misc/mei/pci-me.c
index fe5d5aee074c..b4c9526857bb 100644
--- a/drivers/misc/mei/pci-me.c
+++ b/drivers/misc/mei/pci-me.c
@@ -23,6 +23,7 @@
#include "client.h"
#include "hw-me-regs.h"
#include "hw-me.h"
+#include "mei-trace.h"
/* mei_pci_tbl - PCI Device ID Table */
static const struct pci_device_id mei_me_pci_tbl[] = {
@@ -145,11 +146,14 @@ static inline void mei_me_set_pm_domain(struct mei_device *dev) {}
static inline void mei_me_unset_pm_domain(struct mei_device *dev) {}
#endif /* CONFIG_PM */
-static int mei_me_read_fws(const struct mei_device *dev, int where, u32 *val)
+static int mei_me_read_fws(const struct mei_device *dev, int where, const char *name, u32 *val)
{
struct pci_dev *pdev = to_pci_dev(dev->parent);
+ int ret;
- return pci_read_config_dword(pdev, where, val);
+ ret = pci_read_config_dword(pdev, where, val);
+ trace_mei_pci_cfg_read(&dev->dev, name, where, *val);
+ return ret;
}
/**
--
2.43.0
next prev parent reply other threads:[~2026-02-01 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 9:43 [char-misc-next 0/7] mei: csc: support controller with separate PCI device Alexander Usyskin
2026-02-01 9:43 ` [char-misc-next 1/7] mei: me: use PCI_DEVICE_DATA macro Alexander Usyskin
2026-02-01 9:43 ` [char-misc-next 2/7] mei: fix idle print specifiers Alexander Usyskin
2026-02-01 9:43 ` Alexander Usyskin [this message]
2026-02-01 9:43 ` [char-misc-next 4/7] mei: trace: print return value of pci_cfg_read Alexander Usyskin
2026-02-01 9:43 ` [char-misc-next 5/7] mei: convert PCI error to common errno Alexander Usyskin
2026-02-01 9:43 ` [char-misc-next 6/7] mei: csc: support controller with separate PCI device Alexander Usyskin
2026-02-01 9:43 ` [char-misc-next 7/7] mei: csc: wake device while reading firmware status Alexander Usyskin
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=20260201094358.1440593-4-alexander.usyskin@intel.com \
--to=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menachem.adin@intel.com \
--cc=mika.westerberg@linux.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
all inboxes | Powered by JetHome®