linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matteo Fortini <m.fortini@selcomgroup.com>
To: linuxppc-embedded@ozlabs.org
Subject: gpt frequency input/pwm driver for MPC512x
Date: Tue, 30 Sep 2008 13:12:54 +0200	[thread overview]
Message-ID: <48E209B6.7070203@selcomgroup.com> (raw)

We are developing a couple of gpt drivers (one for input capture and 
frequency measurement, one for pwm lcd backlight control) for an 
MPC512x, and we'd like to find the proper way of inserting it into the 
kernel.

Currently, the frequency input driver is reserving a character device 
and registering as a platform device driver with the 
of_register_platform_driver() calls.
The character device interface is given through the old-style cdev_t 
allocation and deallocation, but I see that maybe this kind of devices, 
which seems not to conform to any device type, should register as 
"miscdevice"s, is that correct? This would leave me with only 14 minor 
numbers free to be allocated. Moreover, there seems to be no way of 
getting to the device data when using miscdevice's file operations, so 
we would be on our own allocating more than one frequency input.

Same for the backlight driver: I'd like to have a pmw driver, which I 
can register a new platform driver, but how do I "glue" it with the 
backlight driver? I'd prefer not to have direct pwm  register calls in 
the backlight driver, but I'd rather have the backlight driver call a 
generic pwm driver in order to do its job.

Thanks,
Matteo

                 reply	other threads:[~2008-09-30 11:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48E209B6.7070203@selcomgroup.com \
    --to=m.fortini@selcomgroup.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).