From: Mark Brown <broonie@kernel.org>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] regmap: Add Kconfig option for debugfs register writes
Date: Wed, 18 Jun 2014 01:11:27 +0100 [thread overview]
Message-ID: <20140618001127.GC5099@sirena.org.uk> (raw)
In-Reply-To: <1403033795-9122-1-git-send-email-mpa@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Tue, Jun 17, 2014 at 09:36:35PM +0200, Markus Pargmann wrote:
> To enable writing of registers through the regmap debugfs interface, it
> was necessary to alter the regmap-debugfs.c source code. This is not
> really practical.
> As this is a powerful tool for debugging, this patch creates an expert
> kconfig option for this function. This makes it easier to enable
> register writing in the kernel.
This is deliberately hard to enable in order to make it clear that it
should never, ever be used in production as a bodge around writing
drivers and generally in order to reduce the risk to the rest of the
system. Enabling this will typically give userspace full access to
components like PMICs which have the potential to cause physical damage
to the system if misused.
Anyone with a use for this is most likely building their own kernels
anyway and if a user modifies the code to enable it is clear that it is
their responsibility to deal with the fallout.
> This patch also fixes the file mode when the regmap debugfs write code is
> compiled.
Seperate changes in separate patches, especially don't put bugfixes in
the same patch as features.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-18 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 19:36 [PATCH] regmap: Add Kconfig option for debugfs register writes Markus Pargmann
2014-06-17 19:56 ` David Rientjes
2014-06-17 20:13 ` Markus Pargmann
2014-06-18 0:11 ` Mark Brown [this message]
2014-06-18 21:01 ` Markus Pargmann
2014-06-24 11:12 ` Mark Brown
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=20140618001127.GC5099@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpa@pengutronix.de \
/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