From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
"Sushma Venkatesh Reddy" <sushma.venkatesh.reddy@intel.com>
Subject: Re: [PATCH v4] drm/i915/slpc: Add sysfs for SLPC power profiles
Date: Tue, 21 Jan 2025 09:42:17 -0500 [thread overview]
Message-ID: <Z4-ySdQ7sCymXRMx@intel.com> (raw)
In-Reply-To: <4f62fe21-2641-40ba-ace4-1429389068f5@intel.com>
On Sat, Jan 18, 2025 at 06:47:27PM +0100, Michal Wajdeczko wrote:
>
>
> On 17.01.2025 22:57, Vinay Belgaumkar wrote:
> > Default SLPC power profile is Base(0). Power Saving mode(1)
> > has conservative up/down thresholds and is suitable for use with
> > apps that typically need to be power efficient.
> >
> > Selected power profile will be displayed in this format-
> >
> > $ cat slpc_power_profile
> >
> > [base] power_saving
> >
> > $ echo power_saving > slpc_power_profile
> > $ cat slpc_power_profile
> >
> > base [power_saving]
> >
>
> is that output aligned with the sysfs rules? from [1]
Please help me to understand why that is against the rule?
It is still ascii and it is one value per file.
How is this different from:
$ cat /sys/power/mem_sleep
[s2idle] shallow deep
?!
>
> "Attributes should be ASCII text files, preferably with only one value
> per file. It is noted that it may not be efficient to contain only one
> value per file, so it is socially acceptable to express an array of
> values of the same type.
>
> Mixing types, expressing multiple lines of data, and doing fancy
> formatting of data is heavily frowned upon. Doing these things may get
> you publicly humiliated and your code rewritten without not"
>
>
> [1] https://www.kernel.org/doc/html/latest/filesystems/sysfs.html#attributes
>
next prev parent reply other threads:[~2025-01-21 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 21:57 [PATCH v4] drm/i915/slpc: Add sysfs for SLPC power profiles Vinay Belgaumkar
2025-01-17 22:52 ` ✗ Fi.CI.SPARSE: warning for drm/i915/slpc: Add sysfs for SLPC power profiles (rev5) Patchwork
2025-01-17 23:03 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-18 17:47 ` [PATCH v4] drm/i915/slpc: Add sysfs for SLPC power profiles Michal Wajdeczko
2025-01-21 14:42 ` Rodrigo Vivi [this message]
2025-02-03 22:59 ` Rodrigo Vivi
2025-02-04 7:17 ` Michal Wajdeczko
2025-01-20 12:06 ` ✓ i915.CI.Full: success for drm/i915/slpc: Add sysfs for SLPC power profiles (rev5) Patchwork
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=Z4-ySdQ7sCymXRMx@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=sushma.venkatesh.reddy@intel.com \
--cc=vinay.belgaumkar@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