public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@avionic-design.de>
To: Borislav Petkov <bp@alien8.de>, Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: awful kconfig help texts.
Date: Thu, 16 Aug 2012 14:05:41 +0200	[thread overview]
Message-ID: <20120816120541.GA10154@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <20120816111044.GA12029@x1.osrc.amd.com>

[-- Attachment #1: Type: text/plain, Size: 3025 bytes --]

On Thu, Aug 16, 2012 at 01:10:44PM +0200, Borislav Petkov wrote:
> On Thu, Aug 16, 2012 at 11:54:39AM +0200, Thierry Reding wrote:
> > How does the attached patch look?
> > 
> > Thierry
> 
> > From cd3199b94e697cccd38766b4a60d2e91474d0539 Mon Sep 17 00:00:00 2001
> > From: Thierry Reding <thierry.reding@avionic-design.de>
> > Date: Thu, 16 Aug 2012 08:01:21 +0200
> > Subject: [PATCH] pwm: Improve Kconfig help text
> > 
> > The Kconfig help text should help the user understand what functionality
> > is provided by an option. This is especially true for new subsystems. An
> > improved help text is provided by this commit in the hopes of clarifying
> > the usefulness of the PWM framework.
> > 
> > Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
> > ---
> >  drivers/pwm/Kconfig | 24 ++++++++++++++++++------
> >  1 file changed, 18 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
> > index 8fc3808..88ddb9e 100644
> > --- a/drivers/pwm/Kconfig
> > +++ b/drivers/pwm/Kconfig
> > @@ -1,12 +1,24 @@
> >  menuconfig PWM
> > -	bool "PWM Support"
> > +	bool "Pulse-Width Modulation (PWM) Support"
> >  	depends on !MACH_JZ4740 && !PUV3_PWM
> >  	help
> > -	  This enables PWM support through the generic PWM framework.
> > -	  You only need to enable this, if you also want to enable
> > -	  one or more of the PWM drivers below.
> > -
> > -	  If unsure, say N.
> > +	  Generic Pulse-Width Modulation (PWM) support.
> > +
> > +	  This framework provides a generic interface to PWM devices
> > +	  within the Linux kernel. On the driver side it provides an API
> > +	  to register and unregister a PWM chip, an abstraction of a PWM
> > +	  controller, that supports one or more PWM devices. Client
> > +	  drivers can request PWM devices and use the generic framework
> > +	  to configure as well as enable and disable them.
> > +
> > +	  The new generic framework replaces the legacy PWM framework
> > +	  which allows only a single driver implementing the required
> > +	  API. Not all legacy implementations have been ported to the
> > +	  new framework yet. The new framework provides an API that is
> > +	  backward compatible with the legacy framework so that existing
> > +	  client drivers continue to work as expected.
> > +
> > +	  If unsure, say no.
> 
> Yes, this is much better than what we had before. I'd suggest though,
> that instead of describing the high-level software design of the PWM
> subsystem, the text should be more addressed to the simple user like me
> who would like to know what this thing is and why do I want to enable
> it. Basically summarize what PWN devices are and what they're used for.
> I.e., https://en.wikipedia.org/wiki/Pulse-width_modulation#Applications
> but in 4-5 lines of text.
> 
> IMHO, of course.

Okay, I'll add something along those lines in addition to the above.
That way everybody should find something useful in it.

Thanks,
Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-08-16 12:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 15:16 awful kconfig help texts Dave Jones
2012-07-31 17:07 ` Borislav Petkov
2012-07-31 17:26   ` Steven Rostedt
2012-07-31 17:42     ` Borislav Petkov
2012-08-01  7:47       ` Thierry Reding
2012-08-01  8:56         ` Borislav Petkov
2012-08-01  9:21           ` Lars-Peter Clausen
2012-08-01  9:26             ` Borislav Petkov
2012-08-01  9:38               ` Lars-Peter Clausen
2012-08-01 10:04                 ` Borislav Petkov
2012-08-01 10:56                   ` Lars-Peter Clausen
2012-08-01 12:46                     ` Steven Rostedt
2012-08-01 13:18                       ` Lars-Peter Clausen
2012-08-07 18:25               ` Mark Brown
2012-07-31 18:43   ` Dave Jones
2012-07-31 22:11     ` Borislav Petkov
2012-08-01  7:43   ` Thierry Reding
2012-08-01  9:28     ` Jan Engelhardt
2012-08-16  9:54   ` Thierry Reding
2012-08-16 11:10     ` Borislav Petkov
2012-08-16 12:05       ` Thierry Reding [this message]
2012-08-17  6:11         ` Thierry Reding
2012-08-17  7:00           ` Borislav Petkov
2012-08-17  7:19             ` Thierry Reding
2012-08-20  2:34           ` Cam Hutchison

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=20120816120541.GA10154@avionic-0098.adnet.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=bp@alien8.de \
    --cc=davej@redhat.com \
    --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