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, 08 Sep 2015 07:10:07 +0000 [thread overview]
Message-ID: <55EE89CF.8060308@ti.com> (raw)
In-Reply-To: <55ED9B01.5030003@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]
On 07/09/15 17:11, Jacek Anaszewski wrote:
>>> Thanks for the patch. Generally, I'd prefer to add files
>>> drivers/leds/of.c and include/linux/of_leds.h and put related functions
>>> there. Those functions' names should begin with "of_". Please provide
>>
>> Ok, I'll do that. I do need to export something from led-class in that
>> case, so that the of.c gets hold of 'leds_class' pointer, either
>> directly or indirectly.
>
> What exactly do you need to export?
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.
>>> also no-op versions of the functions to address configurations when
>>> CONFIG_OF isn't enabled. I have also few comments below.
>>
>> Yep. No-ops for the purpose of making the kernel image smaller?
>
> No, for the case when support for LED subsystem is disabled in the
> kernel config. I'd rather backlight driver depended on LED subsystem
> than selected it.
Sorry, I didn't get that one. How does the backlight driver's
depend/select affect this?
>>> Please move it to include/linux/leds.h, make static inline and provide
>>> also no-op version for the case when CONFIG_LEDS_CLASS isn't enabled.
>>
>> Ok. Why do you want it as static inline in the leds.h?
>
> This function contains only one instruction, why should we waste
> a function call for it?
I like to keep code in .c files and leave .h files for declarations, and
only in special cases have inline code in .h files.
What do you mean with "waste"?
In this case there's no need to get more performance by inlining (which
anyway may not help and needs to be studied separately for every case),
with inlining the resulting kernel image is larger, and inlining forces
the users of led_put to include module.h to compile.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-08 7:10 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 [this message]
2015-09-08 9:21 ` Jacek Anaszewski
2015-09-08 10:41 ` Tomi Valkeinen
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=55EE89CF.8060308@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).