public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what means "module_param(channel_mask, channel_mask, 0644)"?
Date: Sat, 11 Jul 2009 14:41:37 +0200	[thread overview]
Message-ID: <1247316097.7262.11.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0907110658370.4257@localhost>

On Sat, 2009-07-11 at 07:01 -0400, Robert P. J. Day wrote:
> researching my next newbie column about module parameters and i ran
> across the following:
> 
> drivers/input/misc/ati_remote2.c:module_param(channel_mask, channel_mask, 0644);
> drivers/input/misc/ati_remote2.c:module_param(mode_mask, mode_mask, 0644);
> 
> i have no idea what it means to have the second (type) field of
> module_param() simply repeat the name of the parameter.  is this some
> strange magic?  those two names don't *appear* to be typedef'ed
> anywhere i can see.

See include/linux/moduleparam.h:
    /* Helper functions: type is byte, short, ushort, int, uint, long,
       ulong, charp, bool or invbool, or XXX if you define param_get_XXX,
       param_set_XXX and param_check_XXX. */
    #define module_param_named(name, value, type, perm)                        \
            param_check_##type(name, &(value));                                \
            module_param_call(name, param_set_##type, param_get_##type, &value, perm); \
            __MODULE_PARM_TYPE(name, #type)

    #define module_param(name, type, perm)                          \
            module_param_named(name, name, type, perm)

And in drivers/input/misc/ati_remote2.c we find:
    #define param_check_channel_mask(name, p) __param_check(name, p, unsigned in
    #define param_set_channel_mask ati_remote2_set_channel_mask
    #define param_get_channel_mask ati_remote2_get_channel_mask
    module_param(channel_mask, channel_mask, 0644);
    [...]
    #define param_check_mode_mask(name, p) __param_check(name, p, unsigned int)
    #define param_set_mode_mask ati_remote2_set_mode_mask
    #define param_get_mode_mask ati_remote2_get_mode_mask
    module_param(mode_mask, mode_mask, 0644);

To me that looks like two implementations of the three param_*_XXX
functions described in the comment quoted above.

Does that answer your question?

Regards,


Paul Bolle


  parent reply	other threads:[~2009-07-11 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 11:01 what means "module_param(channel_mask, channel_mask, 0644)"? Robert P. J. Day
2009-07-11 11:07 ` Robert P. J. Day
2009-07-11 12:41 ` Paul Bolle [this message]
2009-07-11 12:40   ` Robert P. J. Day

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=1247316097.7262.11.camel@localhost.localdomain \
    --to=pebolle@tiscali.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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