From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/of: Add devm_of_iomap()
Date: Fri, 15 Jun 2018 16:52:02 +1000 [thread overview]
Message-ID: <c564d222f0b566dc12b3e64baf93bc48702ad8da.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAMuHMdWPQPZxvG6JhGGqsqYpzp74PgABDjMKVCBetKSAnLqhkw@mail.gmail.com>
On Fri, 2018-06-15 at 08:16 +0200, Geert Uytterhoeven wrote:
> Hi Ben,
>
> On Fri, Jun 15, 2018 at 1:51 AM Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > On Thu, 2018-06-14 at 10:27 +0200, Geert Uytterhoeven wrote:
> > > > --- a/include/linux/of_address.h
> > > > +++ b/include/linux/of_address.h
> > > > @@ -40,6 +40,11 @@ extern void __iomem *of_iomap(struct device_node *device, int index);
> > > > void __iomem *of_io_request_and_map(struct device_node *device,
> > > > int index, const char *name);
> > > >
> > > > +/* Request and map, wrapper on devm_ioremap_resource */
> > > > +extern void __iomem *devm_of_iomap(struct device *dev,
> > > > + struct device_node *node, int index,
> > > > + resource_size_t *size);
> > > > +
> > > > /* Extract an address from a device, returns the region size and
> > > > * the address space flags too. The PCI version uses a BAR number
> > > > * instead of an absolute index
> > >
> > > Do you need a dummy for !CONFIG_OF_ADDRESS, to aid compile-testing?
> >
> > I didn't think so, as of_address_to_resource() already has a dummy, so
> > it should build fine.
>
> That dummy doesn't matter, as drivers/of/address won't be built if
> !CONFIG_OF_ADDRESS anyway.
Right but:
- I moved it to lib/devres.c in my respun patch (because otherwise
sparc won't get it)
- The dummy is in include/linux/of_address.h, so devm_of_ioremap will
compile fine either way.
> I mean for compile-testing users of devm_of_iomap().
>
> And according to kbuild test robot <lkp@intel.com>:
>
> > > (.text+0x1882): undefined reference to `devm_ioremap_resource'
>
> devm_ioremap_resource() has no dummy for !HAS_IOMEM and
> OF_ADDRESS depends on !SPARC && (HAS_IOMEM || UML),
> bypassing the HAS_IOMEM check on UML.
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2018-06-15 6:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 0:01 [PATCH] drivers/of: Add devm_of_iomap() Benjamin Herrenschmidt
2018-06-12 8:35 ` Andy Shevchenko
2018-06-12 10:28 ` Benjamin Herrenschmidt
2018-06-12 16:53 ` Andy Shevchenko
2018-06-12 22:58 ` Benjamin Herrenschmidt
2018-06-12 23:16 ` Andy Shevchenko
2018-06-13 0:18 ` Benjamin Herrenschmidt
2018-06-13 8:18 ` Andy Shevchenko
2018-06-12 17:42 ` Rob Herring
2018-06-12 22:53 ` Benjamin Herrenschmidt
2018-06-13 15:00 ` Rob Herring
2018-06-13 23:07 ` Benjamin Herrenschmidt
2018-06-14 8:27 ` Geert Uytterhoeven
2018-06-14 23:50 ` Benjamin Herrenschmidt
2018-06-15 6:16 ` Geert Uytterhoeven
2018-06-15 6:52 ` Benjamin Herrenschmidt [this message]
2018-06-14 13:30 ` kbuild test robot
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=c564d222f0b566dc12b3e64baf93bc48702ad8da.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).