From: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Bryan Wu <cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Linux LED Subsystem
<linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: Re: Re[6]: [PATCH] of: Add more stubs for non-OF builds
Date: Thu, 27 Jun 2013 10:50:45 +0100 [thread overview]
Message-ID: <20130627095045.2D4AC3E0A6F@localhost> (raw)
In-Reply-To: <CACxGe6uqng-s4KtSwQ-MEUQ3Ed9_moNw_KvZeaPoN2OaGZnNWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 21 Jun 2013 19:56:29 +0100, Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> On Fri, Jun 21, 2013 at 7:35 PM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
> >> >> On Fri, Jun 21, 2013 at 7:17 AM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
> >> >> >> On Thu, Jun 20, 2013 at 5:26 PM, Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> >> >> >> > On Thu, 20 Jun 2013 16:49:54 -0700, Bryan Wu <cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> >> >> >> Hi Rob,
> >> >> >> >>
> >> >> >> >> Is this patch good for merging?
> >> >> >> >>
> >> >> >> >> In Alex's one patch to add device tree supporting for a leds driver,
> >> >> >> >> we got building errors due to miss definitions of some of_xxx api
> >> >> >> >> functions.
> >> >> >> >>
> >> >> >> >> It looks obviously to me that we need to fix this in device tree core
> >> >> >> >> instead put #ifdef CONFIG_OF everywhere.
> >> >> >> >
> >> >> >> > Actually, the reason those things aren't universally defined is to catch
> >> >> >> > exactly what it caught. The "leds-mc13783: Add devicetree support" patch
> >> >> >> > interleaves DT and non-DT parsing which isn't generally a good idea. The
> >> >> >> > DT parsing code should be shuffled off into a separate function and/or
> >> >> >> > contained with "if (IS_ENABLED(CONFIG_OF)) {}".
> >> >> >> >
> >> >> >>
> >> >> >> Agree, reasonable! I will remove this patch from my tree firstly.
> >> >> >>
> >> >> >> Alex, could you please update your patch with Grant's feedback?
> >> >> >
> >> >> > As far I understand you mean only the last part of patch. Where DT support
> >> >> > is introduced. Is not it?
> >> >> >
> >> >>
> >> >> Yes, exactly. I still keep those 2 non-DT related patches in my tree
> >> >> and just removed that DT supporting patch.
> >> >>
> >> >> Please update that patch and posted again to linux-leds and DT
> >> >> maintainers as well.
> >> >
> >> > I am really dont like any #ifdef in the source, but will do if this is only
> >> > one way to put this patch into the main tree.
> >>
> >> You don't need any #ifdefs. Put all the DT-related calls into a
> >> separate function specifically for decoding the DT information and
> >> wrap the contents with:
> >>
> >> if (IS_ENABLED(CONFIG_OF)) { }
> >
> > This macro does not help for undefined reference, unfortunately.
> > So #ifdef and/or stubs for OF-functions is needed in this case anymore.
> >
> > if (IS_ENABLED(CONFIG_OF))
> > some = of_get_next_child(foo, bar);
> > will produce an error at compile time if OF is not enabled,
> > because we have not empty function (if !OF) for this.
>
> Check linux-next.
Oops, my apologies, of_get_next_child is still inside the CONFIG_OF
block. Arnd had written a patch to expose some of the OF prototypes, but
that was in of_platform.h, not of.h. Use a #ifdef block around the OF
parsing helper function for now until that is fixed in the header file.
g.
prev parent reply other threads:[~2013-06-27 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 17:24 [PATCH] of: Add more stubs for non-OF builds Alexander Shiyan
[not found] ` <1371489882-11143-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2013-06-18 16:25 ` Rob Herring
[not found] ` <51C089F6.2060902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-18 16:35 ` Alexander Shiyan
[not found] ` <1371573337.452797583-x9YND1UlJWJsdVUOrk1QfQ@public.gmane.org>
2013-06-20 23:49 ` Bryan Wu
[not found] ` <CAK5ve-+96fNSF0cV1gefzgJNFX-nefZ08HWupPirQYauecEQYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-21 0:26 ` Grant Likely
2013-06-21 0:36 ` Bryan Wu
[not found] ` <CAK5ve-JX1BC-jdpSzBx_en_o4FYjie-1GRL39B18NywUvXAHrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-21 10:21 ` Grant Likely
2013-06-21 14:17 ` Re[2]: " Alexander Shiyan
[not found] ` <1371824246.856851759-pyBXd9eNxi0edp2WBT/QOw@public.gmane.org>
2013-06-21 17:13 ` Bryan Wu
2013-06-21 17:21 ` Re[4]: " Alexander Shiyan
[not found] ` <1371835275.689989846-g6/BKhZsNKQedp2WBT/QOw@public.gmane.org>
2013-06-21 18:22 ` Grant Likely
2013-06-21 18:35 ` Re[6]: " Alexander Shiyan
[not found] ` <1371839716.602513920-Sq8Ym99z60Iedp2WBT/QOw@public.gmane.org>
2013-06-21 18:56 ` Grant Likely
[not found] ` <CACxGe6uqng-s4KtSwQ-MEUQ3Ed9_moNw_KvZeaPoN2OaGZnNWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 9:50 ` Grant Likely [this message]
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=20130627095045.2D4AC3E0A6F@localhost \
--to=grant.likely-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=shc_work-JGs/UdohzUI@public.gmane.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).