mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kim, Milo" <milo.kim@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND 00/16] Support TI LMU devices
Date: Tue, 3 Nov 2015 18:08:14 +0900	[thread overview]
Message-ID: <5638797E.8020201@ti.com> (raw)
In-Reply-To: <20151103083344.GA3503@x1>


On 11/3/2015 5:33 PM, Lee Jones wrote:
> On Tue, 03 Nov 2015, Kim, Milo wrote:
>
>> Hi Lee,
>>
>> On 11/2/2015 5:59 PM, Lee Jones wrote:
>>>>   drivers/video/backlight/Kconfig                    |  62 ++
>>>>>   drivers/video/backlight/Makefile                   |   7 +
>>>>>   drivers/video/backlight/lm3532_bl.c                | 183 +++++
>>>>>   drivers/video/backlight/lm3631_bl.c                | 129 ++++
>>>>>   drivers/video/backlight/lm3632_bl.c                | 125 ++++
>>>>>   drivers/video/backlight/lm3633_bl.c                | 210 ++++++
>>>>>   drivers/video/backlight/lm3695_bl.c                |  91 +++
>>>>>   drivers/video/backlight/lm3697_bl.c                | 187 +++++
>>>>>   drivers/video/backlight/ti-lmu-backlight.c         | 429 ++++++++++++
>>>>>   drivers/video/backlight/ti-lmu-backlight.h         | 152 +++++
>>> How different are all of these drivers?
>>>
>>> Can you create one driver that supports them all instead?
>>>
>>
>> Thanks for your suggestion.
>>
>> 'ti-lmu-backlight' is the common part of lmxxxx_bl drivers. And each
>> lmxxx_bl has its own operation functions by using ti_lmu_bl_ops.
>> I've tried to make consolidated driver but it contained too much
>> device specific code in one file. So I prefer simple drivers
>> structure - 'common part' and 'device specific operations'.
>> It would be appreciated if you could introduce better idea.
>
> I wish to avoid having to apply the patches to conduct my own analysis
> of the files, as I am severely restricted on time.  Can you tell me how
> much duplicated code there is between the files?  How many lines would
> be saved by supporting all of the lm* drivers in a single file?
>

Understood. Let me try it again. I'll get back to you soon.
Thanks for your help.

Best regards,
Milo

  reply	other threads:[~2015-11-03  9:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  5:24 Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 01/16] Documentation: dt-bindings: mfd: add TI LMU device binding information Milo Kim
2015-11-06  2:00   ` Rob Herring
2015-11-11  9:49   ` Lee Jones
2015-11-12  0:05     ` Kim, Milo
2015-11-02  5:24 ` [PATCH RESEND 02/16] Documentation: dt-bindings: backlight: add TI LMU backlight " Milo Kim
2015-11-02 15:02   ` Rob Herring
2015-11-03  7:13     ` Kim, Milo
2015-11-03 15:32       ` Rob Herring
2015-11-02  5:24 ` [PATCH RESEND 03/16] Documentation: dt-bindings: hwmon: add TI LMU HWMON " Milo Kim
2015-11-06  1:57   ` Rob Herring
2015-11-06  3:48     ` Kim, Milo
2015-11-02  5:24 ` [PATCH RESEND 04/16] Documentation: dt-bindings: leds: add LM3633 LED " Milo Kim
2015-11-03 16:15   ` Jacek Anaszewski
2015-11-10  7:01     ` Kim, Milo
2015-11-02  5:24 ` [PATCH RESEND 05/16] Documentation: dt-bindings: regulator: add LM363x regulator " Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 06/16] mfd: add TI LMU driver Milo Kim
2015-11-23 10:30   ` Lee Jones
2015-11-24  2:35     ` Kim, Milo
2015-11-24  6:39       ` Kim, Milo
2015-11-24  8:18         ` Lee Jones
2015-11-25  8:10           ` Kim, Milo
2015-11-25  8:15             ` Lee Jones
2015-11-02  5:24 ` [PATCH RESEND 07/16] backlight: add TI LMU backlight common driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 08/16] backlight: ti-lmu-backlight: add LM3532 driver Milo Kim
2015-11-02  5:37   ` kbuild test robot
2015-11-02  7:33     ` Kim, Milo
2015-11-02  5:24 ` [PATCH RESEND 09/16] backlight: ti-lmu-backlight: add LM3631 driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 10/16] backlight: ti-lmu-backlight: add LM3632 driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 11/16] backlight: ti-lmu-backlight: add LM3633 driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 12/16] backlight: ti-lmu-backlight: add LM3695 driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 13/16] backlight: ti-lmu-backlight: add LM3697 driver Milo Kim
2015-11-02  5:24 ` [PATCH RESEND 14/16] hwmon: add TI LMU hardware fault monitoring driver Milo Kim
2015-11-02 14:27   ` Guenter Roeck
2015-11-03  7:01     ` Kim, Milo
2015-11-02  5:24 ` [PATCH RESEND 15/16] leds: add LM3633 driver Milo Kim
2015-11-03 16:15   ` Jacek Anaszewski
2015-11-10  7:38     ` Kim, Milo
2015-11-10 13:44       ` Jacek Anaszewski
2015-11-11  2:16         ` Kim, Milo
2015-11-12  9:04           ` Jacek Anaszewski
2015-11-20  9:22       ` Jacek Anaszewski
2015-11-22 23:40         ` Kim, Milo
2015-11-23 11:17           ` Jacek Anaszewski
2015-11-02  5:24 ` [PATCH RESEND 16/16] regulator: add LM363X driver Milo Kim
2015-11-02 12:26   ` Mark Brown
2015-11-03  6:59     ` Kim, Milo
2015-11-04 13:59   ` Mark Brown
2015-11-10  7:54     ` Kim, Milo
2015-11-02  8:59 ` [PATCH RESEND 00/16] Support TI LMU devices Lee Jones
2015-11-03  6:52   ` Kim, Milo
2015-11-03  8:33     ` Lee Jones
2015-11-03  9:08       ` Kim, Milo [this message]
2015-11-25  8:51       ` Kim, Milo
2015-11-25  9:05         ` Lee Jones
2015-11-02  9:00 ` Lee Jones
2015-11-03  6:56   ` Kim, Milo
2015-11-03  8:35     ` Lee Jones

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=5638797E.8020201@ti.com \
    --to=milo.kim@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --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

Powered by JetHome