From: Tony Lindgren <tony@atomide.com>
To: Hemanth V <hemanthv@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/2] OMAP4: Add support for PWM LED
Date: Thu, 1 Jul 2010 15:19:05 +0300 [thread overview]
Message-ID: <20100701121905.GN2822@atomide.com> (raw)
In-Reply-To: <028701cb1917$5313cd60$LocalHost@wipblrx0099946>
* Hemanth V <hemanthv@ti.com> [100701 15:11]:
> ----- Original Message ----- From: "Tony Lindgren"
> <tony@atomide.com>
> To: "Hemanth V" <hemanthv@ti.com>
> Cc: <linux-omap@vger.kernel.org>
> Sent: Thursday, July 01, 2010 4:07 PM
> Subject: Re: [PATCH 2/2] OMAP4: Add support for PWM LED
>
>
> >* Hemanth V <hemanthv@ti.com> [100630 17:12]:
> >>From 713727188b99465341767eedaa42004862261211 Mon Sep 17 00:00:00 2001
> >>From: Hemanth V <hemanthv@ti.com>
> >>Date: Wed, 30 Jun 2010 18:16:33 +0530
> >>Subject: [PATCH] OMAP4: Add support for PWM LED
> >>
> >>TWL6030 supports PWM (Pulse Width Modulator) which is used
> >>to control charging LED. This allows for controlling brightness
> >>This patch implements the APIs needed by leds-pwm driver.
> >
> ><snip>
> >
> >>--- /dev/null
> >>+++ b/arch/arm/mach-omap2/twl6030_pwm.c
> >>@@ -0,0 +1,168 @@
> >>+/*
> >>+ * twl6030_pwm.c
> >>+ * Driver for PHOENIX (TWL6030) Pulse Width Modulator
> >
> >This should go to somewhere under drivers instead of
> >arch/arm/mach-omap2.
>
> Tony, since PWM is specific to each platform, they are typically
> under platform folder. Some examples below
>
> arch/arm/plat-mxc/pwm.c
> arch/arm/plat-pxa/pwm.c
> arch/arm/plat-samsung/pwm.c
But this is related to an external PM chip that can be
potentially used for other chips than omaps.
Tony
prev parent reply other threads:[~2010-07-01 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 14:04 [PATCH 2/2] OMAP4: Add support for PWM LED Hemanth V
2010-07-01 10:37 ` Tony Lindgren
2010-07-01 12:17 ` Hemanth V
2010-07-01 12:19 ` Tony Lindgren [this message]
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=20100701121905.GN2822@atomide.com \
--to=tony@atomide.com \
--cc=hemanthv@ti.com \
--cc=linux-omap@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.