From: Thierry Reding <thierry.reding@avionic-design.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-fbdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backlight: Add of_find_backlight_by_node() function
Date: Fri, 16 Nov 2012 22:34:21 +0100 [thread overview]
Message-ID: <20121116213420.GA27563@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20121116131645.c979837c.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 3055 bytes --]
On Fri, Nov 16, 2012 at 01:16:45PM -0800, Andrew Morton wrote:
> On Fri, 9 Nov 2012 15:04:38 +0100
> Thierry Reding <thierry.reding@avionic-design.de> wrote:
>
> > This function finds the struct backlight_device for a given device tree
> > node. A dummy function is provided so that it safely compiles out if OF
> > support is disabled.
> >
> > Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
> > ---
> > drivers/video/backlight/backlight.c | 17 +++++++++++++++++
> > include/linux/backlight.h | 10 ++++++++++
> > 2 files changed, 27 insertions(+)
> >
> > diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
> > index 297db2f..0d1ed4f 100644
> > --- a/drivers/video/backlight/backlight.c
> > +++ b/drivers/video/backlight/backlight.c
> > @@ -370,6 +370,23 @@ void backlight_device_unregister(struct backlight_device *bd)
> > }
> > EXPORT_SYMBOL(backlight_device_unregister);
> >
> > +#if IS_ENABLED(CONFIG_OF)
>
> Using IS_ENABLED() was odd. We'll never support CONFIG_OF=m, so can't
> we use plain old "#ifdef CONFIG_OF" here?
>
> --- a/drivers/video/backlight/backlight.c~backlight-add-of_find_backlight_by_node-function-fix
> +++ a/drivers/video/backlight/backlight.c
> @@ -370,7 +370,7 @@ void backlight_device_unregister(struct
> }
> EXPORT_SYMBOL(backlight_device_unregister);
>
> -#if IS_ENABLED(CONFIG_OF)
> +#ifdef CONFIG_OF
> static int of_parent_match(struct device *dev, void *data)
> {
> return dev->parent && dev->parent->of_node == data;
> --- a/include/linux/backlight.h~backlight-add-of_find_backlight_by_node-function-fix
> +++ a/include/linux/backlight.h
> @@ -134,7 +134,7 @@ struct generic_bl_info {
> void (*kick_battery)(void);
> };
>
> -#if IS_ENABLED(CONFIG_OF)
> +#ifdef CONFIG_OF
> struct backlight_device *of_find_backlight_by_node(struct device_node *node);
> #else
> static inline struct backlight_device *
> _
Yes, that should work.
> > +static int of_parent_match(struct device *dev, void *data)
> > +{
> > + return dev->parent && dev->parent->of_node == data;
> > +}
> > +
> > +struct backlight_device *of_find_backlight_by_node(struct device_node *node)
> > +{
> > + struct device *dev;
> > +
> > + dev = class_find_device(backlight_class, NULL, node, of_parent_match);
> > +
> > + return dev ? to_backlight_device(dev) : NULL;
> > +}
> > +EXPORT_SYMBOL(of_find_backlight_by_node);
>
> It's a global, exported-to-modules function. We should document such
> major interfaces. Unless they are dead trivial, but I don't think this
> one is that simple. The semantics of the return value could be
> explained, and callers should be told that of_find_backlight_by_node()
> took a ref on the returned device, and that they need to run
> put_device(retval->dev), if retval was not NULL.
>
> And anything else which might be useful.
Yes, I should have thought about that. I'll add some proper kerneldoc
and repost.
Thanks for reviewing,
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-16 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 14:04 [PATCH] backlight: Add of_find_backlight_by_node() function Thierry Reding
2012-11-15 1:30 ` Jingoo Han
2012-11-15 6:51 ` Thierry Reding
2012-11-15 8:58 ` Jingoo Han
2012-11-16 20:56 ` Thierry Reding
2012-11-16 21:16 ` Andrew Morton
2012-11-16 21:34 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-07 22:08 Thierry Reding
2012-11-15 16:24 ` Grant Likely
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=20121116213420.GA27563@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=FlorianSchandinat@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).