From: Wyes Karny <wyes.karny@amd.com>
To: <rafael@kernel.org>, <ray.huang@amd.com>,
<viresh.kumar@linaro.org>, <trenn@suse.com>, <shuah@kernel.org>
Cc: <gautham.shenoy@amd.com>, <Mario.Limonciello@amd.com>,
<Perry.Yuan@amd.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Wyes Karny <wyes.karny@amd.com>
Subject: [PATCH 3/6] cpupower: Add is_sysfs_present API
Date: Mon, 12 Jun 2023 11:36:12 +0000 [thread overview]
Message-ID: <20230612113615.205353-4-wyes.karny@amd.com> (raw)
In-Reply-To: <20230612113615.205353-1-wyes.karny@amd.com>
Add is_sysfs_present API to check whether the sysfs file is present or not.
Suggested-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Signed-off-by: Wyes Karny <wyes.karny@amd.com>
---
tools/power/cpupower/lib/cpupower.c | 7 +++++++
tools/power/cpupower/lib/cpupower_intern.h | 1 +
2 files changed, 8 insertions(+)
diff --git a/tools/power/cpupower/lib/cpupower.c b/tools/power/cpupower/lib/cpupower.c
index 3f7d0c0c5067..7a2ef691b20e 100644
--- a/tools/power/cpupower/lib/cpupower.c
+++ b/tools/power/cpupower/lib/cpupower.c
@@ -14,6 +14,13 @@
#include "cpupower.h"
#include "cpupower_intern.h"
+int is_valid_path(const char *path)
+{
+ if (access(path, F_OK) == -1)
+ return 0;
+ return 1;
+}
+
unsigned int cpupower_read_sysfs(const char *path, char *buf, size_t buflen)
{
ssize_t numread;
diff --git a/tools/power/cpupower/lib/cpupower_intern.h b/tools/power/cpupower/lib/cpupower_intern.h
index ac1112b956ec..5fdb8620d41b 100644
--- a/tools/power/cpupower/lib/cpupower_intern.h
+++ b/tools/power/cpupower/lib/cpupower_intern.h
@@ -7,5 +7,6 @@
#define SYSFS_PATH_MAX 255
+int is_valid_path(const char *path);
unsigned int cpupower_read_sysfs(const char *path, char *buf, size_t buflen);
unsigned int cpupower_write_sysfs(const char *path, char *buf, size_t buflen);
--
2.34.1
next prev parent reply other threads:[~2023-06-12 11:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:36 [PATCH 0/6] cpupower: Add various feature control support for amd_pstate Wyes Karny
2023-06-12 11:36 ` [PATCH 1/6] amd-pstate: Make amd-pstate epp driver name hyphenated Wyes Karny
2023-06-15 17:31 ` Rafael J. Wysocki
2023-06-15 17:55 ` Wyes Karny
2023-06-15 18:30 ` Rafael J. Wysocki
2023-06-15 19:04 ` Wyes Karny
2023-06-16 7:29 ` Yuan, Perry
2023-06-16 7:07 ` Huang Rui
2023-06-16 12:33 ` Rafael J. Wysocki
2023-06-20 12:47 ` Huang Rui
2023-06-12 11:36 ` [PATCH 2/6] cpupower: Recognise amd-pstate active mode driver Wyes Karny
2023-06-12 11:36 ` Wyes Karny [this message]
2023-06-12 13:17 ` [PATCH v1.1 3/6] cpupower: Add is_valid_path API Wyes Karny
2023-06-12 11:36 ` [PATCH 4/6] cpupower: Add EPP value change support Wyes Karny
2023-06-16 7:22 ` Huang Rui
2023-06-16 9:03 ` Wyes Karny
2023-06-20 12:58 ` Huang Rui
2023-06-20 13:20 ` Wyes Karny
2023-06-20 13:49 ` Huang Rui
2023-06-12 11:36 ` [PATCH 5/6] cpupower: Add support for amd_pstate mode change Wyes Karny
2023-06-16 7:28 ` Huang Rui
2023-06-12 11:36 ` [PATCH 6/6] cpupower: Add turbo-boost support in cpupower Wyes Karny
2023-06-16 7:29 ` Huang Rui
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=20230612113615.205353-4-wyes.karny@amd.com \
--to=wyes.karny@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®