All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Kuzminsky <seb@highlab.com>
To: linux-kernel@vger.kernel.org
Subject: getting configuration info into a driver at load-time
Date: Mon, 27 Oct 2008 17:07:08 -0600	[thread overview]
Message-ID: <4906499C.8090308@highlab.com> (raw)

Hi folks, i'm looking for a way to pass structured configuration 
information to a device driver at load-time.

I'm working on a device driver for a family of FPGA cards for motion 
control of industrial robots and computer-controlled machine tools.  The 
driver loads the FPGA firmware with request_firmware() and sends it to 
the FPGA.

Once the FPGA is up and running, the user needs to configure the 
firmware specifically for their machine, by telling the firmware things 
like "my machine has two stepper motors and three servo motors, and the 
second servo motor has an encoder with an index channel".  The details 
of the information being relayed isnt important, the key thing is that 
it's like a struct containing a couple of arrays of different kinds 
structs, something like this:

     struct config {

         struct {
             bool enabled;
             bool index_enabled;
             bool index_mask_enabled;
         } encoder_config[];

         struct {
             bool enabled;
         } pwmgen_config[];

         struct {
             bool enabled;
             uint width;
         } stepgen_config[];

         char *firmware;

         bool enable_raw;

     } board_config;


Each board that the driver finds should get its own "board_config".

I thought about exposing this config structure in /sys or /proc (in a 
per-board directory), and let the user poke in the config values after 
the driver has loaded, but I'd really prefer to make the information 
available at load-time.

Currently the driver has a module param array of char*, with each 
board's configuration encoded into an ascii string which gets decoded 
"by hand" in the driver.  Pretty grotty.

Is there some easier/cleaner way to do this?

-- 
Sebastian Kuzminsky
what i like best about 12648430 is the coffee

             reply	other threads:[~2008-10-27 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 23:07 Sebastian Kuzminsky [this message]
2008-10-28  9:21 ` getting configuration info into a driver at load-time Alan Cox
2008-10-28 22:14 ` Kay Sievers

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=4906499C.8090308@highlab.com \
    --to=seb@highlab.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.