From: Pavel Machek <pavel@ucw.cz>
To: Dan Murphy <dmurphy@ti.com>
Cc: linux-leds@vger.kernel.org, jacek.anaszewski@gmail.com,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: [rfc] leds: add TI LMU backlight driver
Date: Thu, 30 Aug 2018 22:18:25 +0200 [thread overview]
Message-ID: <20180830201825.GA1936@amd> (raw)
In-Reply-To: <a0906253-44e3-5a01-73ca-67c7cb124eb0@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
Hi!
> > Here's preview of driver for TI LMU. It controls LEDs on Droid 4
> > smartphone, including keyboard and screen backlights.
> >
> > This adds backlight support for the following TI LMU
> > chips: LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
> >
> > Signed-off-by: Milo Kim <milo.kim@ti.com>
> > [add LED subsystem support for keyboard backlight and rework DT
> > binding according to Rob Herrings feedback]
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
> > [remove backlight subsystem support for now]
> > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> >
> > ---
> >
> > Does it looks mostly reasonable? I guess it will need some
> > s/BACKLIGHT/LEDS/ , and I'll need to remove my debugging hacks.
> >
> > I'd prefer this to be LED driver, first; I'll need to figure out what
> > to do with backlight. I guess something like existing "backlight"
> > trigger should do the trick.
> >
>
> I looked at this driver from Milo before submitting a specific LM3697 driver.
Aha. I did not realize that was for same hardware... I should have
cc-ed you, I guess.
> I do not like this driver.
> I don't like that it smashes numerous devices into some structure with varying register maps.
>
Can you elaborate? The chips are similar enough that single driver
makes sense, and we certainly want to maintain one driver, not 6
drivers differing only in .. what exactly?
> Not only that but it appears that you just pulled this driver from a repo and posted it without clean up.
>
a) No I did not, feel free to generate a diff.
b) Even if I did, why would that be a problem?
> If the devices share register maps and can be added to families I would prefer to do it that way.
>
> So if the LM3695 and LM3697 share the same features and register map they should be one driver
> The LM363x series may be able to be a different driver.
Well all 6 chips this driver supports seem to be similar enough, so
that single driver makes sense.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [rfc] leds: add TI LMU backlight driver
Date: Thu, 30 Aug 2018 22:18:25 +0200 [thread overview]
Message-ID: <20180830201825.GA1936@amd> (raw)
In-Reply-To: <a0906253-44e3-5a01-73ca-67c7cb124eb0@ti.com>
Hi!
> > Here's preview of driver for TI LMU. It controls LEDs on Droid 4
> > smartphone, including keyboard and screen backlights.
> >
> > This adds backlight support for the following TI LMU
> > chips: LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
> >
> > Signed-off-by: Milo Kim <milo.kim@ti.com>
> > [add LED subsystem support for keyboard backlight and rework DT
> > binding according to Rob Herrings feedback]
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
> > [remove backlight subsystem support for now]
> > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> >
> > ---
> >
> > Does it looks mostly reasonable? I guess it will need some
> > s/BACKLIGHT/LEDS/ , and I'll need to remove my debugging hacks.
> >
> > I'd prefer this to be LED driver, first; I'll need to figure out what
> > to do with backlight. I guess something like existing "backlight"
> > trigger should do the trick.
> >
>
> I looked at this driver from Milo before submitting a specific LM3697 driver.
Aha. I did not realize that was for same hardware... I should have
cc-ed you, I guess.
> I do not like this driver.
> I don't like that it smashes numerous devices into some structure with varying register maps.
>
Can you elaborate? The chips are similar enough that single driver
makes sense, and we certainly want to maintain one driver, not 6
drivers differing only in .. what exactly?
> Not only that but it appears that you just pulled this driver from a repo and posted it without clean up.
>
a) No I did not, feel free to generate a diff.
b) Even if I did, why would that be a problem?
> If the devices share register maps and can be added to families I would prefer to do it that way.
>
> So if the LM3695 and LM3697 share the same features and register map they should be one driver
> The LM363x series may be able to be a different driver.
Well all 6 chips this driver supports seem to be similar enough, so
that single driver makes sense.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180830/31f5014c/attachment.sig>
next prev parent reply other threads:[~2018-08-30 20:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 21:20 [rfc] leds: add TI LMU backlight driver Pavel Machek
2018-08-29 21:20 ` Pavel Machek
2018-08-30 8:22 ` [PATCH] " Pavel Machek
2018-08-30 8:22 ` Pavel Machek
2018-08-30 8:22 ` Pavel Machek
2018-08-30 16:40 ` Tony Lindgren
2018-08-30 16:40 ` Tony Lindgren
2018-08-30 19:20 ` Jacek Anaszewski
2018-08-30 19:20 ` Jacek Anaszewski
2018-08-30 19:41 ` [rfc] " Dan Murphy
2018-08-30 19:41 ` Dan Murphy
2018-08-30 19:41 ` Dan Murphy
2018-08-30 20:18 ` Pavel Machek [this message]
2018-08-30 20:18 ` Pavel Machek
2018-08-31 12:19 ` Dan Murphy
2018-08-31 12:19 ` Dan Murphy
2018-08-31 12:19 ` Dan Murphy
2018-08-31 21:30 ` Pavel Machek
2018-08-31 21:30 ` Pavel Machek
2018-09-04 14:34 ` Dan Murphy
2018-09-04 14:34 ` Dan Murphy
2018-09-04 14:34 ` Dan Murphy
2018-09-06 10:16 ` Pavel Machek
2018-09-06 10:16 ` Pavel Machek
2018-08-30 20:37 ` kbuild test robot
2018-08-30 20:37 ` kbuild test robot
2018-08-30 20:37 ` kbuild test robot
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=20180830201825.GA1936@amd \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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.