From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Raul Piper <raulpblooper@gmail.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: Developing Linux Kernel Driver for LED Driver
Date: Tue, 14 Jun 2016 10:37:40 +0200 [thread overview]
Message-ID: <575FC254.8040900@samsung.com> (raw)
In-Reply-To: <CAEwN+MA38ozhiZN-0XfeiZt9=Wr42yVU-HyzCzhMC1OzxxB=fg@mail.gmail.com>
Hi Raul,
On 06/14/2016 05:22 AM, Raul Piper wrote:
> 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.
Please get acquainted with the LED subsystem documentation:
Documentation/leds/leds-class.txt.
You should also refer to the existing LED class drivers in drivers/leds
to find out how LED class devices are being registered.
> 2.The architecture of the user space application to test this driver
LED class devices expose sysfs interface at /sys/class/leds, i.e.
the LEDs can be controlled from bash.
> 3.The requirement for the Device Tree configuration for this.
Please refer to Documentation/devicetree/bindings/leds/common.txt
and driver bindings in Documentation/devicetree/bindings/leds.
> 4.The name of the LED class driver maintainer in the kernel linux, to
> whom I have to send the patch?
./scripts/get_maintainer.pl -f drivers/leds/ will give you the answer.
> 5.Any other mandatory requirement to which I have to adhere to for
> pushing the device driver to the main line.
Please read the following documents:
- Documentation/SubmittingPatches
- Documentation/SubmittingDrivers
- Documentation/SubmitChecklist
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-06-14 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 3:22 Developing Linux Kernel Driver for LED Driver Raul Piper
2016-06-14 8:37 ` Jacek Anaszewski [this message]
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=575FC254.8040900@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=raulpblooper@gmail.com \
/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.