From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <patches@opensource.wolfsonmicro.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: core: Add debugfs for regulator always_on flag
Date: Fri, 22 Apr 2016 15:40:38 +0100 [thread overview]
Message-ID: <571A37E6.9070005@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20160422135709.GE3217@sirena.org.uk>
On 22/04/16 14:57, Mark Brown wrote:
> On Fri, Apr 22, 2016 at 02:33:02PM +0100, Richard Fitzgerald wrote:
>> This patch adds a debugfs file for the always_on flag in struct regulator.
>> It's useful for debugging to be able to view the state of this flag and
>> as it's set by logic inside the regulator core it doesn't necessarily have
>> the same value as the always_on flag in constraints.
> Why not include this in the same file as the rest of the constraints?
> Or why not have one file per constraint (which would be easier for
> scripts)?
Hmm, well the thing is there's two separate always_on flags, the one in
constraints (if you have any constraints) and the one in struct
regulator. I could munge the always_on status printed in the constraints
debugfs to be (regulator.always_on || constraints.always_on) though I'm
not sure if that's helpful (it shows actual state) or confusing (it
might not match what was fed in as constraints).
>> + ret = snprintf(buf, PAGE_SIZE, "always_on: %u\n", regulator->always_on);
>> + debugfs_create_file("always_on", 0444, regulator->debugfs,
> It seems to be formatted as though it's going to end up in the same file
> but it's a separate file so instead it's just repeating the name of the
> file inside the file.
Sorry, that was lazy copy-and-paste. I'll fix it.
prev parent reply other threads:[~2016-04-22 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:33 [PATCH] regulator: core: Add debugfs for regulator always_on flag Richard Fitzgerald
2016-04-22 13:57 ` Mark Brown
2016-04-22 14:40 ` Richard Fitzgerald [this message]
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=571A37E6.9070005@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.