Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1284004 > unrolled thread

Re: [PATCH] regmap: Add a config option for making regmap debugfs writable

Started byPavel Machek <pavel@ucw.cz>
First post2015-12-04 17:40 +0100
Last post2015-12-05 17:50 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] regmap: Add a config option for making regmap debugfs  writable Pavel Machek <pavel@ucw.cz> - 2015-12-04 17:40 +0100
    Re: [PATCH] regmap: Add a config option for making regmap debugfs  writable Mark Brown <broonie@kernel.org> - 2015-12-05 17:50 +0100

#1284004 — Re: [PATCH] regmap: Add a config option for making regmap debugfs writable

FromPavel Machek <pavel@ucw.cz>
Date2015-12-04 17:40 +0100
SubjectRe: [PATCH] regmap: Add a config option for making regmap debugfs writable
Message-ID<qC1yP-57z-47@gated-at.bofh.it>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1284581

FromMark Brown <broonie@kernel.org>
Date2015-12-05 17:50 +0100
Message-ID<qCoc2-3ts-9@gated-at.bofh.it>
In reply to#1284004

[Multipart message — attachments visible in raw view] — view raw

On Fri, Dec 04, 2015 at 05:37:09PM +0100, Pavel Machek wrote:
> On Tue 2015-10-13 21:07:00, Mark Brown wrote:

> > 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.

It's not clear to me that those are especially good ideas that we want
to encourage people to use.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web