From: Thierry Reding <thierry.reding@avionic-design.de>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Bryan Wu <bryan.wu@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] leds-lm3530: replace pwm platform functions with generic pwm functions
Date: Mon, 20 Aug 2012 09:50:39 +0200 [thread overview]
Message-ID: <20120820075038.GA20443@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F41EF096C@DQHE02.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Mon, Aug 20, 2012 at 07:41:31AM +0000, Kim, Milo wrote:
> > Maybe we should get this resolved somehow in the meantime. Resolving
> > the
> > other issues may take another cycle or two, so you may not want to wait
> > that long.
>
> Is that job also including HAVE_PWM configurations?
> Some SoCs still set HAVE_PWMs and codes exist under arch/ directory.
> As I far as understand, new PWM subsystem uses CONFIG_PWM not HAVE_PWM, right?
> And then will HAVE_PWM be cleaned-up?
Yes, the goal is to remove all implementations of the old framework
(HAVE_PWM) and replace it with PWM only implementations. I suppose we
could in the meantime add #ifdef CONFIG_HAVE_PWM around the legacy
functions and provide dummies in the !PWM case. That might work.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-20 7:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 4:02 [PATCH] leds-lm3530: replace pwm platform functions with generic pwm functions Kim, Milo
2012-08-20 5:04 ` Thierry Reding
2012-08-20 5:06 ` Thierry Reding
2012-08-20 5:37 ` Arnd Bergmann
2012-08-20 5:58 ` Thierry Reding
2012-08-20 6:16 ` Kim, Milo
2012-08-20 7:31 ` Thierry Reding
2012-08-20 7:41 ` Kim, Milo
2012-08-20 7:50 ` Thierry Reding [this message]
2012-08-20 7:56 ` Kim, Milo
2012-08-20 6:13 ` Kim, Milo
2012-08-20 6:45 ` Arnd Bergmann
2012-08-20 7:26 ` Kim, Milo
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=20120820075038.GA20443@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=Milo.Kim@ti.com \
--cc=arnd@arndb.de \
--cc=bryan.wu@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox