From: Pavel Machek <pavel@ucw.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Anatol Pomozov <anatol.pomozov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regmap: Add a config option for making regmap debugfs writable
Date: Fri, 4 Dec 2015 17:37:09 +0100 [thread overview]
Message-ID: <20151204163709.GA822@amd> (raw)
In-Reply-To: <20151013200700.GM14956@sirena.org.uk>
On Tue 2015-10-13 21:07:00, Mark Brown wrote:
> On Tue, Oct 13, 2015 at 11:33:13AM -0700, Anatol Pomozov wrote:
> > On Tue, Oct 13, 2015 at 10:55 AM, Mark Brown <broonie@kernel.org> wrote:
>
> > > This is deliberately not a Kconfig option because it is a terrible idea
> > > to do this in production and making it either selectable or the default
> > > is an invitation to abuse.
>
> > What kind of abuse are you talking about?
>
> Using it as a standard interface to control systems in production rather
> than having appropriate support in the relevant driver.
>
> > Having an easy way of modifying chip registers is extremely useful
> > during bringup / driver development. And during device development
> > phase I regularly have situations when I need to change a register to
> > see if it fixes an issue. Sometimes I need to test it remotely when
> > users located at another end of the Earth.
>
> This is exactly the sort of use case this feature is intended for, and
> is the sort of situation where a custom kernel is not going to be any
> kind of practical problem.
Well.. we support iopl(0) and we have /dev/mem. I don't see how this
is different.
And yes, CONFIG_ option would be nice, so that this gets compile test
coverage....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-04 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 17:46 [PATCH] regmap: Add a config option for making regmap debugfs writable Anatol Pomozov
2015-10-13 17:55 ` Mark Brown
2015-10-13 18:33 ` Anatol Pomozov
2015-10-13 20:07 ` Mark Brown
2015-12-04 16:37 ` Pavel Machek [this message]
2015-12-05 16:49 ` Mark Brown
2015-10-13 20:00 ` kbuild test robot
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=20151204163709.GA822@amd \
--to=pavel@ucw.cz \
--cc=anatol.pomozov@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.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