From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
linux-leds@vger.kernel.org, linux-fbdev@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH 1/3] leds: Add of_led_get() and led_put()
Date: Tue, 8 Sep 2015 13:41:03 +0300 [thread overview]
Message-ID: <55EEBB3F.4040908@ti.com> (raw)
In-Reply-To: <55EEA8B2.3040808@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
On 08/09/15 12:21, Jacek Anaszewski wrote:
>> The "static struct class *leds_class" from led-class.c, in one way or
>> another. of_led_get() needs to go through the led devices from the class.
>>
>> For now I just removed the "static" from it, so that I can use it from
>> of.c.
>
> I think we can go in this direction. I've skimmed through existing
> class drivers and found similar examples (e.g. tty_class, rtc_class).
Yep.
>> Sorry, I didn't get that one. How does the backlight driver's
>> depend/select affect this?
>
> OK, I confused something here. Backlight driver should depend on
> LEDS_CLASS by defining "depends on LEDS_CLASS" in backlight Kconfig.
> It should also depend on OF. In case of this driver the no-ops would be
> only for the purpose of making the kernel image smaller, as the driver
> probe will fail without them anyway. Nevertheless, there might be added
> other drivers in the future, using of_led_get{put} API which would like
> to make some decisions basing on whether LEDS_CLASS or/and OF are
> turned on. No-ops would be of use then.
I agree.
>> What do you mean with "waste"?
>
> I used 'waste' because we would be wasting time here for the call which
> can be avoided at no cost. Of course if compiler will decide to inline
> it.
>
>> In this case there's no need to get more performance by inlining
>
> Why so?
Reserving and freeing resources are rarely hot paths. The functions in
question are usually called in a driver's probe and remove. Saving a few
CPU cycles there doesn't really matter, so I think readability is the
important part here.
>> and inlining forces the users of led_put to include module.h to compile.
>
> We could include module.h from leds.h.
Yes we can. And I can do that in my patch. I don't agree with the
solution but neither do I really have a problem with it =).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-08 10:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 11:33 [PATCH 0/3] backlight: led-backlight driver Tomi Valkeinen
2015-08-25 11:34 ` [PATCH 1/3] leds: Add of_led_get() and led_put() Tomi Valkeinen
2015-08-25 12:18 ` Andrew Lunn
2015-08-25 12:53 ` Tomi Valkeinen
2015-09-08 11:23 ` Tomi Valkeinen
2015-08-25 13:25 ` Jacek Anaszewski
2015-09-07 12:35 ` Tomi Valkeinen
2015-09-07 14:11 ` Jacek Anaszewski
2015-09-08 7:10 ` Tomi Valkeinen
2015-09-08 9:21 ` Jacek Anaszewski
2015-09-08 10:41 ` Tomi Valkeinen [this message]
2015-09-08 10:57 ` Jacek Anaszewski
2015-09-07 13:18 ` Tomi Valkeinen
2015-09-07 14:10 ` Jacek Anaszewski
2015-08-25 11:34 ` [PATCH 2/3] backlight: add led-backlight driver Tomi Valkeinen
2015-08-25 12:39 ` Andrew Lunn
2015-08-25 13:00 ` Tomi Valkeinen
2015-08-25 11:34 ` [PATCH 3/3] devicetree: Add led-backlight binding Tomi Valkeinen
2015-08-25 13:39 ` Jacek Anaszewski
2015-08-25 15:41 ` Tomi Valkeinen
2015-08-26 7:07 ` Jacek Anaszewski
2015-08-26 9:11 ` Tomi Valkeinen
2015-08-26 9:56 ` Jacek Anaszewski
2015-08-31 23:12 ` Rob Herring
2015-09-04 15:03 ` Jacek Anaszewski
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=55EEBB3F.4040908@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=andrew@lunn.ch \
--cc=j.anaszewski@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-leds@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;
as well as URLs for NNTP newsgroup(s).