linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>,
	linux-pwm@vger.kernel.org, Bryan Wu <cooloney@gmail.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] leds/pwm: don't call pwm_disable when setting brightness
Date: Wed, 25 Mar 2015 11:14:28 +0100	[thread overview]
Message-ID: <20150325101428.GB32677@pengutronix.de> (raw)
In-Reply-To: <1423734290-19750-1-git-send-email-u.kleine-koenig@pengutronix.de>

[Cc: += akpm]

On Thu, Feb 12, 2015 at 10:44:48AM +0100, Uwe Kleine-König wrote:
> on arm/i.MX28 the leds connected to a pwm are still broken and it's more
> than three years ago that I came up with these patches. I still consider
> them to do the right thing and they fix a real bug.
I'm really frustrated here. I want to fix a real bug, made several
suggestions (with patches) how to fix it and still have to include my
local patches in each project that uses leds on i.MX28's pwm output.

Thierry, how can we get this resolved?

Best regards
Uwe

> Old threads to this topic include:
> 
> 	http://thread.gmane.org/gmane.linux.kernel/1381289
> 	http://thread.gmane.org/gmane.linux.ports.arm.kernel/282593/focus=282596
> 	http://thread.gmane.org/gmane.linux.pwm/1749
> 
> Uwe Kleine-König (2):
>   pwm/doc: Clearify that the pin state after pwm_disable is undefined
>   leds/pwm: Don't disable pwm when setting brightness to 0
> 
>  Documentation/pwm.txt   |  5 +++++
>  drivers/leds/leds-pwm.c | 10 +++++-----
>  2 files changed, 10 insertions(+), 5 deletions(-)

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  parent reply	other threads:[~2015-03-25 10:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  9:44 [PATCH 0/2] leds/pwm: don't call pwm_disable when setting brightness Uwe Kleine-König
2015-02-12  9:44 ` [PATCH 1/2] pwm/doc: Clearify that the pin state after pwm_disable is undefined Uwe Kleine-König
2015-02-12  9:44 ` [PATCH 2/2] leds/pwm: Don't disable pwm when setting brightness to 0 Uwe Kleine-König
2015-02-12  9:47   ` Uwe Kleine-König
2015-02-24 18:56   ` Stefan Wahren
2015-02-24 19:06     ` Uwe Kleine-König
2015-02-25  8:13       ` Stefan Wahren
2015-02-25  8:42         ` Uwe Kleine-König
2015-03-25 10:14 ` Uwe Kleine-König [this message]
2015-03-25 12:00   ` [PATCH 0/2] leds/pwm: don't call pwm_disable when setting brightness Thierry Reding
2015-03-27  8:59     ` Uwe Kleine-König
2015-03-27 11:26       ` Thierry Reding
2015-03-27 14:35         ` Uwe Kleine-König
2015-03-27 15:43           ` Thierry Reding
2015-03-27 18:49             ` Sascha Hauer

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=20150325101428.GB32677@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=cooloney@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=s.hauer@pengutronix.de \
    --cc=thierry.reding@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 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).