All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raul Piper <raulpblooper@gmail.com>
To: linux-leds@vger.kernel.org
Subject: Developing Linux Kernel Driver for LED Driver
Date: Tue, 14 Jun 2016 08:52:44 +0530	[thread overview]
Message-ID: <CAEwN+MA38ozhiZN-0XfeiZt9=Wr42yVU-HyzCzhMC1OzxxB=fg@mail.gmail.com> (raw)

Hi,
I am developing a Linux kernel driver(software) for a 16 channel LED
driver(this driverhere refers to the hardware of LED ) .Below are few
of its characteristics

DC input voltage range : 10 V to 28 V
Integrated boost converter with adaptive output voltage
16 channels  and independent PWM brightness control
Up to 15 white LEDs per channel
On-board microcontroller for total device control through 4-wire
serial interface
LED short-circuit faults management

I have done some brute force work by creating a user space application
to do some portion of the LED glowing, I know its not a full fledged
work.

I want to know on the below points :
1. How can I convert it into a GPIO driver and the standard ramework
with which I can integrate it.
2.The architecture of the user space application to test this driver
3.The requirement for the Device Tree configuration for this.
4.The name of the LED class driver maintainer in the kernel linux, to
whom I have to send the patch?
5.Any other mandatory requirement to which I have to adhere to for
pushing the device driver to the main line.

PS : I am using TI's beagleboard for developing the driver on the kernel 4.1x.

Br,
Rp

             reply	other threads:[~2016-06-14  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  3:22 Raul Piper [this message]
2016-06-14  8:37 ` Developing Linux Kernel Driver for LED Driver Jacek Anaszewski
2016-06-14  4:29 Raul Piper

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='CAEwN+MA38ozhiZN-0XfeiZt9=Wr42yVU-HyzCzhMC1OzxxB=fg@mail.gmail.com' \
    --to=raulpblooper@gmail.com \
    --cc=linux-leds@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.