From: Andrew Lunn <andrew@lunn.ch>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-pwm@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-leds@vger.kernel.org,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Bryan Wu <cooloney@gmail.com>
Subject: Re: [RFC PATCH] pwm: TLC591xx PWM driver
Date: Wed, 19 Aug 2015 15:31:04 +0200 [thread overview]
Message-ID: <20150819133104.GA12002@lunn.ch> (raw)
In-Reply-To: <55D45FE4.2050805@ti.com>
> But in the end, it is still PWM in the HW level, and also, the
> brightness isn't linear, or even anything like it. At least on my
> backlight, the visible values range from ~230 to 255.
I suspect the narrow range for you is a property of your hardware. For
my WRT1900ac, 0-32 the LEDs look pretty much like off. Above that, i
get light. Should the LED class layer care about this? Probably
not. It seems like the generic backlight layer should have some method
to reduce the 0-255 down to a couple of dozen useful working points.
> That said, I feel that these frameworks, GPIO, PWM and LED are somewhat
> overlapping. Not really my area of expertise, but I imagine a single
> framework containing all those functionalities could be possible.
Humm, i don't think the frameworks overlap that much. I think it is
the hardware which overlaps. You have a device with an output which
you normally connect an LED to, but you could connect anything to. You
can control this pin using a very restricted PWM like scheme, or you
can have it plain off/on.
With hardware like this, you need to decide which it is most like, and
put that framework at the bottom. Then stack generic X->Y layers on
top to get the rest of the functionality.
Andrew
prev parent reply other threads:[~2015-08-19 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 13:52 [RFC PATCH] pwm: TLC591xx PWM driver Tomi Valkeinen
2015-08-18 13:52 ` [RFC PATCH] pwm: add TLC59108/TLC59116 " Tomi Valkeinen
2015-08-18 14:19 ` Andrew Lunn
2015-08-18 14:58 ` Tomi Valkeinen
2015-08-18 15:14 ` Andrew Lunn
2015-08-18 15:09 ` [RFC PATCH] pwm: TLC591xx " Andrew Lunn
2015-08-18 15:09 ` Andrew Lunn
2015-08-19 10:24 ` Thierry Reding
2015-08-19 10:52 ` Tomi Valkeinen
2015-08-19 13:31 ` Andrew Lunn [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=20150819133104.GA12002@lunn.ch \
--to=andrew@lunn.ch \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.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.