From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: cooloney@gmail.com, rpurdie@rpsys.net,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Matthew.Fatheree@belkin.com, "R, Vignesh" <vigneshr@ti.com>
Subject: Re: [PATCH RESEND v6 0/2] Driver for TI tlc591xx 8/16 Channel i2c LED driver
Date: Mon, 17 Aug 2015 19:40:54 +0300 [thread overview]
Message-ID: <55D20E96.3020504@ti.com> (raw)
In-Reply-To: <20150817142147.GG7537@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
On 17/08/15 17:21, Andrew Lunn wrote:
>>> If you think your PWM code is so much better, please submit a revert
>>> patch plus your PWM LED driver. We can find somebody to do a side by
>>> side review.
>>
>> It's not about the driver code. That can be cleaned up if needed. The
>> question is whether the driver should be a PWM driver or a LED driver.
>
> There i disagree. It is all about the code. Release early, release
> often. Show us the code. Get it discussed, reviewed, tested, and then
> ultimately merged.
>
> You keep saying PWM is the way to solve this problem, but where is
> your code showing your solution is superior to mine, yet still solves
> my use case?
No, I have not said PWM is the way to solve this problem. I have said it
sounds to me that a PWM driver better matches the HW and our use case. I
have asked you if PWM + pwd-leds would solve your use case as well as a
led driver.
If you don't have an answer, it's fine to say "I don't know". But you
have just ignored the question. And even worse, you dropped me (and
Vignesh) from the latest mail thread.
We have a pwm driver for the chip, but it only supports TLC59108. It
should be trivial to extend it to support TLC59116, but it's pointless
to spend time on that if a PWM driver doesn't handle your use cases.
> So please stop talking and show us the code.
TLC591xx is quite simple HW, and the code doing the HW programming
should be identical for a pwm and for a led driver. I don't see either a
pwm or a led driver being somehow superior. They are very similar simple
drivers, implementing a different interface. Whether the interface works
for you should be clear from the interface itself. The code is just details.
On the other hand, if you want something you can use to test, it's a
different case, but you haven't indicated any interest in that.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-17 16:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 22:08 [PATCH RESEND v6 0/2] Driver for TI tlc591xx 8/16 Channel i2c LED driver Andrew Lunn
2015-03-17 22:08 ` [PATCH RESEND v6 1/2] leds: tlc591xx: Document binding for the TI " Andrew Lunn
2015-04-20 13:09 ` Jacek Anaszewski
2015-04-20 17:46 ` Bryan Wu
2015-03-17 22:08 ` [PATCH RESEND v6 2/2] leds: tlc591xx: Driver " Andrew Lunn
2015-04-20 9:06 ` Jacek Anaszewski
2015-04-20 11:59 ` Andrew Lunn
2015-04-20 13:07 ` Jacek Anaszewski
[not found] ` <5534FA13.9090502-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-20 17:49 ` Bryan Wu
2015-03-29 19:28 ` [PATCH RESEND v6 0/2] Driver for TI tlc591xx " Andrew Lunn
2015-03-30 22:10 ` Bryan Wu
2015-08-17 12:11 ` Tomi Valkeinen
2015-08-17 13:27 ` Andrew Lunn
2015-08-17 14:11 ` Tomi Valkeinen
2015-08-17 14:21 ` Andrew Lunn
2015-08-17 16:40 ` Tomi Valkeinen [this message]
2015-08-17 16:48 ` Andrew Lunn
2015-08-17 17:08 ` Bryan Wu
2015-08-17 20:47 ` Tomi Valkeinen
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=55D20E96.3020504@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=Matthew.Fatheree@belkin.com \
--cc=andrew@lunn.ch \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=vigneshr@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.