From: Stephen Boyd <sboyd@kernel.org>
To: Li Chen <me@linux.beauty>, Michael Turquette <mturquette@baylibre.com>
Cc: Li Chen <lchen@ambarella.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: create write_enable file to control clk rate write and other dangerous ops permission
Date: Wed, 11 Jan 2023 10:37:29 -0800 [thread overview]
Message-ID: <57d1f58c4c6cca793d629d5776b477d0.sboyd@kernel.org> (raw)
In-Reply-To: <20230110114540.2975540-1-me@linux.beauty>
Quoting Li Chen (2023-01-10 03:45:39)
> From: Li Chen <lchen@ambarella.com>
>
> It's common requirement for bsp debug/test to change clk rate from userspace.
>
> Currently, we must define CLKOCK_ALLOW_WRITE_DEBUGFS then re-compile kernel
> to allow this feature. Let's replace it with a "write_enable" file to
> allow enable it at runtime.
Nak. This design is intentional.
next prev parent reply other threads:[~2023-01-11 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 11:45 [PATCH] clk: create write_enable file to control clk rate write and other dangerous ops permission Li Chen
2023-01-11 18:37 ` Stephen Boyd [this message]
2023-01-12 3:05 ` Li Chen
2023-01-12 19:18 ` Stephen Boyd
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=57d1f58c4c6cca793d629d5776b477d0.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=lchen@ambarella.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
--cc=mturquette@baylibre.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