From: Mike Tipton <quic_mdtipton@quicinc.com>
To: <djakov@kernel.org>, <gregkh@linuxfoundation.org>, <rafael@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<quic_okukatla@quicinc.com>, <quic_viveka@quicinc.com>,
Mike Tipton <quic_mdtipton@quicinc.com>
Subject: [PATCH 0/3] Add interconnect debugfs client
Date: Mon, 24 Jul 2023 18:28:56 -0700 [thread overview]
Message-ID: <20230725012859.18474-1-quic_mdtipton@quicinc.com> (raw)
This series introduces interconnect debugfs files that support voting
for any path the framework supports.
We've historically relied on an out-of-tree module for this, which used
the old icc_get() that was recently removed in [0]. The old icc_get()
took integer endpoint IDs, which made identifying paths in our old
implementation non-intuitive. The logical node names typically don't
change much chip-to-chip, but the raw integer IDs do. Take this
opportunity to introduce an icc_get() that uses string names instead,
which allows for a more intuitive and generic debugfs interface.
We rely on this support for debug, test, and verification. Hopefully
it'll be useful for other vendors as well.
[0] commit 7dcdad6f32c9 ("interconnect: drop unused icc_get() interface")
Mike Tipton (3):
debugfs: Add write support to debugfs_create_str()
interconnect: Reintroduce icc_get()
interconnect: Add debugfs test client
drivers/interconnect/Makefile | 2 +-
drivers/interconnect/core.c | 67 +++++++++++
drivers/interconnect/debugfs-client.c | 156 ++++++++++++++++++++++++++
drivers/interconnect/internal.h | 2 +
fs/debugfs/file.c | 48 +++++++-
include/linux/interconnect.h | 6 +
6 files changed, 278 insertions(+), 3 deletions(-)
create mode 100644 drivers/interconnect/debugfs-client.c
--
2.17.1
next reply other threads:[~2023-07-25 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 1:28 Mike Tipton [this message]
2023-07-25 1:28 ` [PATCH 1/3] debugfs: Add write support to debugfs_create_str() Mike Tipton
2023-07-25 1:28 ` [PATCH 2/3] interconnect: Reintroduce icc_get() Mike Tipton
2023-07-25 5:48 ` Pavan Kondeti
2023-07-26 1:24 ` Mike Tipton
2023-07-25 8:07 ` kernel test robot
2023-07-25 8:49 ` kernel test robot
2023-07-25 1:28 ` [PATCH 3/3] interconnect: Add debugfs test client Mike Tipton
2023-07-25 5:46 ` Pavan Kondeti
2023-07-25 15:59 ` Mike Tipton
2023-07-25 5:30 ` [PATCH 0/3] Add interconnect debugfs client Pavan Kondeti
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=20230725012859.18474-1-quic_mdtipton@quicinc.com \
--to=quic_mdtipton@quicinc.com \
--cc=djakov@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_okukatla@quicinc.com \
--cc=quic_viveka@quicinc.com \
--cc=rafael@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